Several questions about importing previous LC projects

Ask for help
1

Hello,

I am currently testing LiveCode Create and exploring the possibilities for migrating projects from LiveCode 9 and 10. While doing so, I’ve encountered several challenges and questions:

  1. Accessing the Dictionary In LiveCode Classic, I could access the dictionary by right-clicking in the script editor. How can I access it directly in LiveCode Create?
  2. Unsupported Properties Some properties seem to be unsupported in LiveCode Create. For example, the command put the filename of this stack does not work. Are there alternatives or workarounds for these properties?
  3. Visibility of UI Elements After importing a project, all UI elements that were set to invisible in LiveCode Classic are now visible in LiveCode Create. Is there a way to preserve their original visibility settings during migration?
  4. Visibility Property in the IDE The “visible” property is not available in the LiveCode Create IDE for imported elements—only for new widgets and groups. However, commands like set the visible of fld id 1111 still work in the message box. Why is this property missing from the IDE for imported elements?
  5. Handling .livecodescript Files Many of my projects use .livecodescript files, which are stored in the stack folder and loaded using start using stack... and specialFolderPath("resources"). Where should I place or integrate these .livecodescript files in the new LiveCode Create IDE?
  6. DataGrid Is it possible to migrate DataGrids to the new IDE? If so, what is the recommended approach?

Overall, migrating from LiveCode Classic to LiveCode Create seems quite challenging. In cases where compatibility issues arise, is “Switch to Classic” the only viable solution for now? Additionally, what are the long-term plans for backward compatibility and support for legacy projects?

Thank you for your guidance and support. I look forward to your insights.

Best regards,

2

Hi @smunos

  1. The dictionary isn’t accessible through the IDE as of right now but that will be implemented soon. For now you can find documentation here: Introduction to LiveCode Create | LiveCode Documentation
  2. The filename of a stack is unsupported because stacks are by default stored in the cloud, not locally. If you wish to continue to work locally, create a single project (in the cloud) using Create, then create a single button with:
on mouseUp
  answer file “Select a stack:”
  go stack it
end mouseUp

You will be able to work with the stack locally and fileName will work. You will not be able to save your cloud project or the local project using the save menu, you must run “save stack [stackName]” in the message box to save to disk. Full support for creation of a local project is coming shortly which will give you a choice on whether or not to use the cloud.

  1. This is a bug, thank you for bringing this to our attention. I’ve filed it and we’ll have a fix coming soon.
  2. This is also a bug. A fix is coming shortly.
  3. Same answer to question 2 applies here.
  4. I’ll check with the team and will update this post once I have some answers.

Thank you for the feedback, We’re working hard to improve the Classic > Create pathway. Keep the questions coming!

1 Like
3

Thanks for your helpful responses and clarifications. I’m continuing to explore LiveCode Create