the name shall not easily changes for my app code somewhere else use those, here changed, then I need chang the place that used it…
and, in 1.4.2 version, I checked the box of “do not export” of some screens, in 1.5.0 version re-open the proj find that the “do not export” checkBox not checked…I need modify all these related places…
AFAIK that’s one of the reasons for jumping the minor version to 1.5, because some minor changes might be needed for previous project-files, like those you mention above.
For the component child-index names it’s generally not a good idea to use them directly in a code in many places, because they can change easily anytime (even in older versions) if the design layout/hierarchy/component-naming changes. What I usually do is creating objects (bindings) to them and using those in the program, so if the SquareLine Studio project changes these names, it’s only needed to rename it in the binding. But now SquareLine Studio 1.5 has this ‘custom variable alias’ field (described in the documents) which makes this component-child name-creation seamless for you from now on. I’d advise to use this feature and the names exported by it from now on, but if you simply want to change the child-index names in your existing project you’ll need to resort to a refactoring function of your IDE.
For screens that were not exported in your project, you still have the checkbox but now it’s in a new place at the top of the inspector panel. The reason for this is to make it consistent with the new useful feature: the ‘don’t export’ is now available for widgets too, so for example the designer can create a list from widgets to visualize how it will look, but if the list is to be generated later dinamically from the code, its unnecessary exporting can be disabled.
Essentially these changes are the results of some useful new features of SquareLine Studio.
about the second point, I checked the “don’t export” checkBox in 1.4.2 verson squareLine, and re-open the proj in 1.5.0 squareLine the “don’t export” checkbox at the top of the inspector panel does not checked, i mean this
about the first point, we will consider it. Please don’t make too many changes easily, we are doing a large-scale project with a heavy historical burden
Yes. I forgot to say that the ‘don’t export’ checkboxes are not only moved to the general don’t export place in the inspector panel, but also got a new placement in the projectfile, and as far as I know it was intentional and reasonable not to bother with importing it from the old project-versions. Again, that’s why the prominent version-change, it signifies that these kind of changes to old projects can be expected. Nevertheless, the development staff will see that it was a problem for your historical project.