All input and radio buttons reset when hiding a dialog to get point?

[Attila The Gel]

Hello,

Is it normal that when you have a dialog with several radio buttons and edit boxes, and have a button to do a getpoint the whole dialog is reset after you click to get point?

I know that hiding a dialog needs a "loop while", and that works properly but all input is gone whenever I want to getpoint.

Its as if a new dialog is started.

thx

[MSasu]

I'm afraid that this is the default behaviour - there is not a "true" hide of the form like in other languages. You will need to retain current user input into a temporary list and fill the dialog with those values when re-display it.

[Attila The Gel]

Do jou mean a list of "set_tiles" or something else. cause I got 5 groups of radio buttons and its going to be troublesome this way?

[MSasu]

That true, I was saying to use the SET_TILE function to load the values previously set by you user; that it, prior to "hide" the dialog. Don't need to be afraid about effect of those setting on dialog since ACTION_TILE is triggered only on user action.

[Attila The Gel]

Got it.

If in dcl code "rb1" has value = 1 and I chose "rb3" in form and when it reloads after hiding, it first sets "rb1" and then "rb3" with set_tile function right.
But its so fast you can't see it doing all that stuff?

But how do I set_tile a radio button and a toggle?

thx MSasu

[MSasu]

So, "rb1" is the default selection; that it, the option that appear selected when user call your command - I supposed that come from DCL definition. Next the user select the "rb3" option before "hide" the dialog to input a point on screen. When restore the dialog you just have to select from code the "rb3" option; the selection from "rb1" (that come, again, from DCL) is lost automatically - for sure, as long the said buttons are groupped in the same container.

To select programmatically a radio-button:

(set_tile "rb3" "1")

[Lee Mac]

Do jou mean a list of "set_tiles" or something else. cause I got 5 groups of radio buttons and its going to be troublesome this way?

MSasu is correct, you will need to store the current values of the various user input tiles and set these values when the dialog is displayed. To provide an example of how this may be accomplished, by program here has 6 buttons that will temporarily suppress the dialog whilst the user either picks an object or distance from the drawing, and the dialog must be reconfigured to the previously entered settings when displayed.

[Attila The Gel]

So, "rb1" is the default selection; that it, the option that appear selected when user call your command - I supposed that come from DCL definition. Next the user select the "rb3" option before "hide" the dialog to input a point on screen. When restore the dialog you just have to select from code the "rb3" option; the selection from "rb1" (that come, again, from DCL) is lost automatically - for sure, as long the said buttons are groupped in the same container.

To select programmatically a radio-button:

(set_tile "rb3" "1")

I was very close I forgot the double quotes thx again MSusu I think I can go forward for now.

MSasu is correct, you will need to store the current values of the various user input tiles and set these values when the dialog is displayed. To provide an example of how this may be accomplished, by program here has 6 buttons that will temporarily suppress the dialog whilst the user either picks an object or distance from the drawing, and the dialog must be reconfigured to the previously entered settings when displayed.

thx Lee MAC for the examples and for verifying what MSusu said!

[MSasu]

I was very close I forgot the double quotes

Please keep in mind that all functions that deal with DCL accept only strings as arguments.

[Lee Mac]

Please keep in mind that all functions that deal with DCL accept only strings as arguments.

Except mode_tile