You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current EXPORTS we have, display a popup with the TEXT to copy and paste.
Wouldn't this be better if we had a File Save popup instead, then save the export to the file name and location specified. Then we could make the Screens and Objects export to a selected folder and include all the associated files with it?
OK, I now understand why you did it this way, as a File Save Dialog will only save it to the server and no to the client. So I am looking in to dynamically creating a "ZIP" file that would contain all the information for a particular screen. This would include, the Screen object itself, along with all the screen controls on the particular screen, and any images used on that screen.
Once we have a stable export function, we can then look at adding an IMPORT function that would use the ZIP file to Import or install the screen. (Boy this is such fun!!)
A nested export that would export the Screen, Controls and related objects and their object types.
Properties are not linked to anything, so the graphics would have to exported that match those properties.
Graphics are not currently exported at all, so this would used in object exports too.
The text was updated successfully, but these errors were encountered: