Sure, go ahead.

Best,
Marcel
Am 28.04.2018 21:26:27 schrieb Chris Muller <asqueaker at gmail.com>:
Cool!  I hope you won't object to this tweak to cancel one level, merely the Confirm question, back to the original question (the ListChooser), because what gets the user to that Confirm is their intent to move forward with the action, but simply needing to correct the previous entry first.

I'll move this to trunk in a few days if you didn't already, thanks!

 - Chris



On Fri, Apr 27, 2018 at 3:47 AM, Marcel Taeumel <marcel.taeumel at hpi.de [mailto:marcel.taeumel at hpi.de]> wrote:

Hi Chris,

here is a change set for this. Yet, I am not sure whether "cancelability" in trueChoice/falseChoice dialogs break much old code? Anyway, you cannot use UIManager yet because it does not support the position of the trueChoice/falseChoice dialog yet. Let's keep it this way for now. ListChooser is Morphic-specific anyway.


Best,
Marcel

Best,
Marcel
Am 27.04.2018 10:34:17 schrieb Marcel Taeumel <marcel.taeumel at hpi.de [mailto:marcel.taeumel at hpi.de]>:
1) ListChooser is Morphic-specific at the moment. What means "it" here?

2) If you allow addition in the ListChooser, then that is a two-step dialog. The first step is already cancelable. Yes, it makes sense to also make the second step cancelable.

Best,
Marcel
Am 27.04.2018 03:27:46 schrieb Chris Muller <asqueaker at gmail.com [mailto:asqueaker at gmail.com]>:
1) Should it be making use of "UIManager default" instead of
Morphic-specific dialog?

2) When I added a method category, I mis-typed it and simply wanted to
cancel, but I was forced to add one or the other and the remove it.
This being on ListChooser, however, means this is useful for more than
just categories, so this dialog needs a cancelability, does it not?





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20180429/7a1ed8ce/attachment-0001.html>