preview dialog ...

ggaliens · (This post was last modified: 09-25-2015, 01:02 AM by ggaliens.)

preview dialog ... (under wxWidgest and 2.0.x)

I don't think it should always compute with the default values ... before hitting OK. If it does ... then the dialog is NO-GOOD for slower operations ... because they all would execute TWICE.

The value I used to employ to avoid was called ...

manual_preview.

micheus · 09-25-2015, 02:25 AM

Dan has informed about this here . Maybe you can help to put it to work again.(?!)

ggaliens · (This post was last modified: 09-25-2015, 02:25 PM by ggaliens.)

I would be willing to look at it and try to make it more usable ... or more similar to what Optigon had.

dgud · 09-25-2015, 02:48 PM

I do not want what we had before, don't like it so I removed it.

ggaliens · (This post was last modified: 09-25-2015, 03:16 PM by ggaliens.)

I think at the very least ... the user should somehow know that behavior is different.
What is the "tip off" ?

Suppose the dialog is large and covering the thing being generated ... how does the end user even get an "hint" that something behind is being updated ?

I understand sometimes things go two steps forward and two step back. Just wanting to have a conversation here. How does the user know that he/she has been presented with a modeless dialog ?

ggaliens · 09-26-2015, 12:30 AM

Lets say a user BACKSPACES in a field that has a value like

0.001

which might be controlling say volume ... of some foam or whatever that fill another shape. If the system tries to make the foams of size 0.00 ... then there will be an infinite number of them ... because the system triggered a preview on a single backspace. That being said ... because I know about the issue ... I can SWEEP a few chars in the field (pre-select the char) and when I hit say 2 then I get 0.002 w/o ever getting a 0.00 event tiggered.

I hope it is worth consideration.