[Cuis-dev] A few tweaks to preferences

[Gerald Klix]

On 8/20/21 5:53 PM, Juan Vuletich via Cuis-dev wrote:
> Hi Folks,
> 
> After some off-list discussion, and the risk of newcomers, especially 
> students, get scared after accidentally doing World / Quit and quitting 
> without any warning, I did a few tweaks. Now the menu option reads 'Quit 
> without saving' and by default asks for confirmation. The confirmation 
> can be disabled by doing `Preferences disable: 
> #checkLostChangesOnStartUp`, although it will still be given if there 
> are unsaved ChangeSets.
After I adopted my SystemDictionary>>#saveAsNewHaverVersion:
to the changed behavior, sigh ...
> 
> I also made the "Save new Release" option also quit.
Which I also did from the very beginning with my
"Save New Haver Release" option.
After all you don't want to taint your new automatically generated 
release image with incidental last second changes that are not reproducible.

I also use this (ballon|hover) help text:

-- snip --
'Save as a new release of Haver.
Use an updated version-stamped name
and save it under that name on disk.

', 'Clear' bold, ' all user preferences and user state (class vars).
Then ', 'quit' bold, ' running the image.

','This action is for the maintainer of Haver!' red bold, '
Use at your own risk.' red
-- snap --

I suggest to use something similar for Cuis.
Furthermore I would like to see this option,
together with my "Save New Haver Release",
in a Menu of its own withe something like
"Release Management". I am aware that this
single option menu will look a bit ridiculous
for Cuis, but it should make clear, that its
options are not intended for the casual Cuis/Haver
user.

> 
> I also flipped preference #checkLostChangesOnStartUp to false, as I 
> expect most people (like me) will prefer manually going over the 
> .user.???.changes files to recover stuff.
Thanks a lot!
This menu was most annoying, because it was displayed
before the display loop was started.
If you resized your VM window, which I did automatically,
you ended up with a white screen and you had to click smoewhere
on your VM window to get rid of that menu.
> 
> And as usual, tweaks to VectorGraphics.
New VMs needed?
> 
> Thanks,
> 


Just my 0.20€,

Gerald