I get this response in attempting to create a new project:
'cp' is not recognized as internal or external command, operable program, or batch file.
I have not run into this before nor have I had any trouble creating projects before. I reinstalled the manager. Still give me the same error. It installs the canela folder, and creates its parent folder with the name of the project, but there is nothing in the canela folder nor is there the traditional login stack.
Quick question - several methods that update the cloud database have an option to defer the update until a cdb_flushCache is sent. Great and very useful for batching multiple updates to the cloud.
However just wanted to check - if i do an update or batchMerge and defer the cloud update by putting true into tInternalA["delaySend"], does this update the local database?
Or do I have to update the local database separately? (needless to say i'd prefer the former!)
We fixed three bugs and provide one improvement with this update.
Bug fix: We had a rare but possible issue with one of our internal indices that tracks the tableName references to the tableID. It was possible for the cdbCache Table to have two references in the index. This issue could cause an app to fail to sign in when the credentials were correct.
Bug fix: We now insure that the config file is updated on disk when an appropriate change has been made to the database configuration.
Bug fix: There was a bug that would not allow you to sign out of LCM from the Accounts screen.
Improvement: We added a new API - cdb_autoSetupAuthKey(). This API will allow you to place your initializeCanelaDB handler (from your exported sdk) to be placed anywhere in your app. Before, you had to place that handler in your mainstack script or the script of card 1 of your mainstack. Please see the online docs for details on how to use this API (https://docs.livecloud.io/AutoSetupAuthKey/).
Hi all,
I'm probably missing something basic here, so grateful for any help.
I've recently modified a table with the addition of 3 new keys and would like to set a default value for all records for these 3 keys.
I know i can read the entire table into an array, loop through this in liveCode, make the changes and then do an update back to liveCloud.
However this is cumbersome; i had envisaged that i may be able to use batchMerge, or batchUpdate to do this and simply pass "*" as the cdbRecordID, but this does not work - cdb_result shows me the error is The specified cdbRecordID is invalid: *
Is there a way to do this directly? If not will just process in LiveCode and update all records, but am hoping i've missed something more straightforward...
I was having problems loading the cdbUsers table using the cdb_load("cdbUsers") name. I found that the actual name had some information in parenthesis and I can't remember that information. I actually changed the name of the table and now I cannot access that table.
I thought that renaming the user table was supposed to be disabled, is this true?
I need some help with this.
Hello to everyone. We pushed LCM version 2.8. The notable changes are listed below. Enjoy!
Added: Mac engine is code-signed, notarized, and stapled
Improved: Account deletion and paid subscription cancellations will take effect on the first of the following month and refunds will no longer occur
Improved: Engine updater works with modern OS expectations
Improved: Updated Mac and Win engines to LC 9.6.2 rc 3
Improved: Hovering over a table's name will generate a tooltip for tableName and tableID
Improved: Handle importing CSV files that contain quote delimited values and values containing multiple lines
Improved: Added region details to exported invoices
Bugfix: Keys may not show correctly in the header when they are removed or added
Bugfix: Adding keys during a CSV or JSON import can lose notion of the current project
Bugfix: Error occurred when entering non-ASCII characters into the credit card form
Bugfix: UI bugs displaying the list of credit cards in the billing tab
Posted by: stamatis - 03-30-2021, 09:31 AM - Forum: Bug Reports
- No Replies
Hi liveCloud team & all...
Last night i was experimenting with syncing 800+ records repeatedly from local -> cloud. On LiveCode side was fine, but when i tried to view in LCM, i just kept getting the 'we appear to be offline' message.
This morning i get a bizarre error that happens immediately on startup. I downloaded the (new?) notarised version of LCM and tried again, after deleting all preferences etc.
It now launches fixed to the San Francisco server with Mark's username on -- but i'm unable to change any details without triggering an error message making this unusable (screenshot:
LCM error.jpg (Size: 140.63 KB / Downloads: 6)
)
I want to reach out to everyone and update you on the things we are doing. The Canela team continues to work from home, thanks to Covid. The reality is that we have been extremely productive during this time. Our team collaborates on development as if we were in the same room. It has been a great experience.
Our team remains very focused on Appli. Appli is our front-end design tool for making database apps. Our progress has been tremendous. In the last few months, our new IDE has become very clean and robust.
What kind of progress have we made? We have added the ability to create and test apps on a simulator and a mobile device. This feature alone will cut down the development cycle because you can forgo the need to compile and transfer your apps. You save your work and press a refresh button on your phone to see your updates in real-time. You are updating your actual app on a mobile device without having a developer account and app store experience.
Appli comes with a completely responsive design system that is easy to use. You can build your app for any size phone, and it will look pixel-perfect on all phones, no matter the size and aspect ratio.
We have also been working on our Appli elements (complex controls) by improving their functionality and performance. Each element solves anywhere from hundreds to thousands of lines of code automatically. Once you draw your element on the playground, the element is ready for action.
Appli takes full advantage of LiveCloud. Drag a CSV file onto the playground and have Appli automatically store the data in the cloud, build a table for you, and bind your data in seconds. Save your work and test on your phone. You will notice that the table automatically manages key features like editing your data, sort columns, rearrange columns, and rearrange rows. You can decide which columns to make visible. Buttery smooth scrolling on mobile is managed automatically for you. Pull down on the table to refresh your data. Your table can display gigantic amounts of data with its cache system that streams data as you scroll. It looks amazing!
Appli solves so many problems elegantly. It is fantastic that we will have another option for developing apps. All of this work intimately applies to LiveCloud and CanelaDB. Our database and cloud architecture is the meat of the Appli framework. Your apps are indeed databases in the truest sense. You no longer need to think about your app's file and folder architecture. Instead, you get to focus on the UI/UX in a way never before possible.
What types of apps can one create with Appli? We plan to rewrite LCM and NurseNotes in Appli. I can see our productivity increased by not having to manage the UI/UX in code. It also will allow us to release a version of LCM that can run on a tablet and phone.
When will Appli be released? That is the age-old question every software team wishes they could answer accurately. We are planning to go into closed beta this April. We have been demoing our progress and eliciting feedback with a unique group of people over the last few months. We will know more after these champions have had time to kick the tires.
What does all this mean for LiveCloud and CanelaDB? We have been improving LCM behind the scenes during Appli's development. We will soon release new under the hood improvements. We have a few new features and enhancements that we think you will enjoy as well. Mac developers will soon be able to run LCM as a notarized app. We did a lot of work on our app update system. This intense refactor will allow our software to work with modern OS requirements in the future.
We have some big plans for LiveCloud that will allow more collaborative work. Imagine being able to invite another person to access a project on your account for collaboration. Soon you will be able to link your blobs externally to other apps. Our recent refactor of our internal ordering system added a new level of robustness.
Appli would not exist without LiveCloud. Thus, LiveCloud is more important to us than ever before. I hope this information is informative and helpful to you. Please comment below if you have any thoughts or questions.
I've had this recurring issue in developing an app based on LiveCloud -- every now and again, without any clear triggers, the SDK becomes 'unusable'. I'm guessing there is a possible corruption issue?
I just get the message 'the CanelaDB SDK is missing' -- when it's clearly there and has been in use for weeks with no issues...
The SDK folder is stored in a folder containing the LiveCode mainstack; it uses a local DB that syncs with the cloud DB with a custom handler called SyncDB pSource, where the pSource is either local or cloud and will overwrite destination at cloud or local respectively...
This type of issue seems to crop up every 3-4 weeks, I'm unable to explain why... If i download the SDK again, it works but of course my concern is if this will keep happening with the deployed app...
ran into problems importing a CSV file into LiveCloud. This is a large file (122 Mb) with 127K + records
Issues:
1. only 103,000 of the 127,000 records were imported
2. the text was exported from an SQL query system that encloses text components in double quotes; there are leading or trailing double quotes (or both) in all fields. However it seems random if these are leading, trailing or both...
3. several fields also have a leading comma in their text (ie. the field starts with ,"field text"
Any advice? (i mean other than programmatically importing the data file to LiveCode and writing a handler to do this)
