On 1/24/17 11:50 AM, Ralph DiMola via use-livecode wrote:
I have been poking around in the IDE stacks and found this. I think it's a bug
but wanted to run it up the ol' flag pole with the list first before I submit a
bug report.
Recipe:
1) Open a stack.
2) Make a small change.
3) Build a standalone.
4) When presented with the "Save/Cancel/Don’t save" dialog, click on the "Don't
save" option.
5) Exit the IDE and you will not get the options to save your stack because the "Don’t
save" option clears the "Dirty" flag.
6) Re-open the stack in the IDE and observe that your change(s) are not there.
Expected result: User should be present with the option to save the stack when
exiting the IDE.
Observed result: The user is not asked to save the stack when exiting the IDE.
When the "Cancel" option is selected the "dirty flag is not cleared as I would expect but
"Don't save" clears it. I think this is wrong. Even if you don't choose to save at that moment The IDE
should leave the stack marked as "dirty". I could see someone inadvertently losing a lot of work.
This is documented briefly in the dictionary under "savingStandalone".
When a standalone is made, the stack is closed and removed from memory.
After it's built, it is re-opened. If you don't save beforehand, changes
are lost. I think that's just how it has to be.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
