[squeak-dev] Closing modal dialogs...

Thiede, Christoph Christoph.Thiede at student.hpi.uni-potsdam.de
Mon Jan 13 12:09:48 UTC 2020


Hi Eliot,


> Would you?  Why wouldn't you discard the entire compilation continuation?  That is what I would expect t.  So killing the dialog effectively kills the process up to the point of invoking the Unused Variable dialog.


I don't think that toggling the "be modally exclusive" box should be meant as killing the process. Otherwise, we should really rename it ... I would rather think of this feature as a fork.


(Moreover, I never was really happy with the way to pause the UI process ... In particular, MC modal dialogs, which are not exclusive, don't need to decorate the whole UI process. Why can't these things work with the observer pattern instead?)


> That doesn't work for me because the modal dialog emerges from a subcomponent (the FilePlugin) not from the VM level itself.  It is from a plugin in the VM, and making that dialog able to reach out and smite the entire VM feels like working out-of-bounds.

I may have expressed myself inaccurately: Why is your plugin not able to do something like

UIManager default chooseFrom: #('Yes' 'No' 'Quit this operations')

?


However, in my humble opinion, adding an extra button for closing the parent window of a modal dialog sounds kind of insular solution to me. In most scenarios, modal dialogs come without any window. In other scenarios, a window might control multiple processes. What if the "parent window" is detected to be a debugger debugging a process that spawns a modal dialog? Would you then close the debugger?

Other opinions? :-)


Best,

Christoph

________________________________
Von: Squeak-dev <squeak-dev-bounces at lists.squeakfoundation.org> im Auftrag von Eliot Miranda <eliot.miranda at gmail.com>
Gesendet: Freitag, 10. Januar 2020 19:02:45
An: The general-purpose Squeak developers list
Betreff: Re: [squeak-dev] Closing modal dialogs...

Hi Christoph,

On Fri, Jan 10, 2020 at 4:35 AM Thiede, Christoph <Christoph.Thiede at student.hpi.uni-potsdam.de<mailto:Christoph.Thiede at student.hpi.uni-potsdam.de>> wrote:

Hi Eliot,

I did not ever work with the VM simulator, but from what you say, I guess that your modal dialog might simply lack a third button labeled "Quit"?

That doesn't work for me because the modal dialog emerges from a subcomponent (the FilePlugin) not from the VM level itself.  It is from a plugin in the VM, and making that dialog able to reach out and smite the entire VM feels like working out-of-bounds.


In general, to me, the idea of modal windows appears to require an immediate user response that precedes any different user interactions with the notifying view. If this assumption is violated, many models might show bad behavior.* I would rather prefer not to change this behavior. :)

* For an example, do-it |x| (sic, just three characters) in a workspace. Disable modal exclusivity of the appearing Unused Variable dialog, clear the Workspace and then answer the dialog. Of course, you will get an internal compiler error ...

Would you?  Why wouldn't you discard the entire compilation continuation?  That is what I would expect t.  So killing the dialog effectively kills the process up to the point of invoking the Unused Variable dialog.  It would not allow computation to continue.  What should happen is the current process is terminated, a new UI process created, and the user be free to interact with the UI afresh.

Best,

Christoph

________________________________
Von: Squeak-dev <squeak-dev-bounces at lists.squeakfoundation.org<mailto:squeak-dev-bounces at lists.squeakfoundation.org>> im Auftrag von Eliot Miranda <eliot.miranda at gmail.com<mailto:eliot.miranda at gmail.com>>
Gesendet: Freitag, 10. Januar 2020 00:58:18
An: The general-purpose Squeak developers list
Betreff: [squeak-dev] Closing modal dialogs...

Hi All,

    would it be easy to modify modal dialog box interaction to allow closing the "parent window" of a dialog while in the modal dialog?  In the VMSimulator I use a modal dialog to prompt the user for input to evaluate, to test the sim.  Often I simply want to stop after the first expression and so wish to diss,iss the entire simulation omg the second modal dialog.  Bit I'm always forced to select "don't be modal" before I can close the thing.  It;'s a little annoying.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20200113/4590d49e/attachment.html>


More information about the Squeak-dev mailing list