Hi Jorge, could add an option to pass the dialogs position to the load'dialog() procedure, rather than them being hard coded into the XCALL AUI that creates the dialog?

Sure...

What do you think about add a checkbox ("use arguments") in the coordinates panel to define that, ALL the currently selected controls should receive in their corresponding function/procedure their coordinates in arguments?

This way we extend this to any control, and allow multi-selection.

Yeah, that sounds good.

Hi Jorge,

Just curious as to when you think there might be a LEO update w/ this feature?

Well reminded, this was already on my hands when something crossed the way and put me on another direction, let's see if I can solve it right now.

Hi Stephen,

It's published a rough version for handling control coordinates as arguments.
In the "coordinates" panel, below the row/col fields, there are a new checkbox "use arguments".
Besides you can check it for any control, by now, it only processes it for the Dialog so, when checked for the Dialog, on generating code the following happens:

Main program:

call dlg_1_load'dialog(dlg_1'dlgid, 0, 5000 , 5000 , 20000 , 55000 )

GEN file:

PROCEDURE dlg_1_load'dialog(dlg'id as b4,dlg'parent'id as b4,srow as b4, scol as b4, erow as b4, ecol as b4)
++pragma auto_extern

xcall AUI, AUI_CONTROL, CTLOP_ADD, "args.dlg_1", "dlg_1", 0, &
MBF_DIALOG+MBF_SYSMENU+MBF_DLGNOCREEP+MBF_ALTPOS, "", "", dlg'id, &
srow, scol, erow, ecol, -2, -2, 0, 0, "", "", dlg'parent'id

call dlg_1_screen'layout()
xputarg 1,dlg'id

ENDPROCEDURE


I think that, this completely solves the case where you want to define startup coordinates for the Dialog where you just need to substitute the absolute values for the coordinates by your variables, or other absolute values, on calling the load'dialog procedure.

This doesn't solve the case where you want to change the coordinates in the middle of your program.
Here was where I stopped to listen for suggestions before staring to waste time on unnecessary things.

As I suggested previously, in this version, is already possible to define any control with "use arguments", including when there are multiple controls selected but, this is useless if nothing is done on generating code.
Let me add that, there are no particular difficulty to add this to all controls, it's just a matter of being reasonable.

The "problem" of the arguments are the definition of external variables to be sent into the corresponding AUI control PROCEDURE.
Defining those variables also is not a problem, I just don't know if coordinate changes should be programmed inside the GEN file.
To change the coordinates of an AUI control, we just need to know the ID or ID$ of the control and execute:
xcall AUI, AUI_CONTROL, CTLOP_CHG, ID$, "", MBST_CHGALL, ... , new'srow, new'scol, new'erow, new'ecol

In my opinion, it would make sense to consider coordinate arguments for any control if, on startup, their coordinates can vary.

Opinions are welcome, even from those who don't use Leo, what I want to know is which cases do you have about changing control coordinates.

Thanks

First, I think that it would be really good to be able to do this for any control. You could add srow,scol,erow,ecol variables to the state'value$ and infld'state'values arrays. In this case rather than making the position arguments part of the function and procedure calls you'd just use the values currently in the arrays. You could also create a procedure to set the defaults defined in LEO that could be optionally called from load'dialog() based on a a new argument passed to load'dialog(), defaulting to call the defaults procedure.

The dlg'ordslt_state'control() procedure would probably be the best place to do the AUI_CONTROL changes.

I'm not exactly sure what would be the best way to handle SBXINP inputs. The best thing might be to delete the dialog and then recreate it w/ with the coordinate variables set in the array?

Secondly, here is the topic that brought this up

Resizing Dialog

I did accomplish resizing a dialog, here are snapshots of it.

Dialog before expansion


Dialog after expansion


So, here's how I acheived this (this procedure is called when the blue expand and contract buttons are clicked)

Also, my suggestion here would probably make the "use arguments" option be applied to the dialog and all of it's controls if turned on, rather than individual controls?

Jorge,

Just curious if you have an opinion about my suggestion here?

Your suggestion is also my opinion about how this should work, it's not forgotten, I just need some extra-time to implement it, but it will be soon.

Cool, no rush. I was just curious what you thought.