quit message on windows builds

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

quit message on windows builds

EstebanLM

Hi,

Although my direct responsibility with the community is building mac vm's, for my day work necessities I'm also building windows vm's (one of my clients want a multi-platform desktop app).
When doing this... I found one difference in vm behavior between mac, linux and windows: when you press "close button" in main window, both linux and mac fires a callback to image, who can decide if quit, quit saving or denial of quit for some reason. Windows, in the other hand, pops up a dialog "Quit Croquet without save" and then quits or not. We can't handle this from image.

Changing this is as easy as removing the dialog part... without it, windows behaves just as the other two...

So, my question: Why??????? Why is that code there? Is there a reason? or just remnants of older vm's?

best,
Esteban
Reply | Threaded
Open this post in threaded view
|

Re: quit message on windows builds

Andreas.Raab
 
Please read the documentation.

http://squeakvm.org/win32/settings.html
  • EnableF2Menu: This entry allows you to determine whether the preference menu should be shown when pressing F2. The default is 1 (true).
  • EnableAltF4Quit: This entry allows you to specify whether Alt-F4 (and the windows close button) should be honored or not. The default is 1 (true).
    New for 3.10.8:When this setting is disabled (0), the VM generates a window close event instead which can be handled by the image.
There are many other interesting settings documented at the site that you should check out if you're trying to set up production environments with the Squeak VM on Windows.

Cheers,
  - Andreas

On 12/19/2011 13:53, Esteban Lorenzano wrote:
 
Hi,

Although my direct responsibility with the community is building mac vm's, for my day work necessities I'm also building windows vm's (one of my clients want a multi-platform desktop app). 
When doing this... I found one difference in vm behavior between mac, linux and windows: when you press "close button" in main window, both linux and mac fires a callback to image, who can decide if quit, quit saving or denial of quit for some reason. Windows, in the other hand, pops up a dialog "Quit Croquet without save" and then quits or not. We can't handle this from image.

Changing this is as easy as removing the dialog part... without it, windows behaves just as the other two... 

So, my question: Why??????? Why is that code there? Is there a reason? or just remnants of older vm's? 

best,
Esteban
Reply | Threaded
Open this post in threaded view
|

Re: quit message on windows builds

EstebanLM
 
ok, fair enough :)
anyway... I would like the vm's to behave as near as possible between each other... (I know that is not possible always... but at least when it is...)

thanks,
Esteban 

El 19/12/2011, a las 10:50a.m., Andreas Raab escribió:

Please read the documentation.

http://squeakvm.org/win32/settings.html
  • EnableF2Menu: This entry allows you to determine whether the preference menu should be shown when pressing F2. The default is 1 (true).
  • EnableAltF4Quit: This entry allows you to specify whether Alt-F4 (and the windows close button) should be honored or not. The default is 1 (true).
    New for 3.10.8:When this setting is disabled (0), the VM generates a window close event instead which can be handled by the image.
There are many other interesting settings documented at the site that you should check out if you're trying to set up production environments with the Squeak VM on Windows.

Cheers,
  - Andreas

On 12/19/2011 13:53, Esteban Lorenzano wrote:
 
Hi,

Although my direct responsibility with the community is building mac vm's, for my day work necessities I'm also building windows vm's (one of my clients want a multi-platform desktop app). 
When doing this... I found one difference in vm behavior between mac, linux and windows: when you press "close button" in main window, both linux and mac fires a callback to image, who can decide if quit, quit saving or denial of quit for some reason. Windows, in the other hand, pops up a dialog "Quit Croquet without save" and then quits or not. We can't handle this from image.

Changing this is as easy as removing the dialog part... without it, windows behaves just as the other two... 

So, my question: Why??????? Why is that code there? Is there a reason? or just remnants of older vm's? 

best,
Esteban