resizing or maximizing xdialog

[djldc]

I am trying to maximize an xdialog to the current size of the Alpha5 window (whatever the current size happens to be)... but the maximize fills the entire screen and not just Alpha window size. The resize function does not seem to work (bug submitted). Here's my code:


ui_modeless_dlg_box("Visible Xdialog", <<%dlg%
<close> <resize> <maximize>
%dlg%,<<%code%

if a_dlg_button="resize" then 'resize does not seem to work -submitted bug report
ui_dlg_resize("Visible Xdialog",20,30)
end if

if a_dlg_button="maximize" then
ui_dlg_maximize("Visible Xdialog")
end if

if a_dlg_button="close" then
ui_modeless_dlg_close("Visible Xdialog")
end if
%code%)

[CALocklin]

Re: resizing or maximizing xdialog

Maybe this will give someone else a hint and they will get farther than I did. (In other words, I couldn't find a way either.)

I tried various things including using these functions to get current window sizes:

sys_id_enum()
sys_id_size_get()
sys_id_maximize()

The problem with the "size_get" function is that it returns "maximized" when maximized rather than the actual size. However, the size returned is in inches anyway so it isn't much use when everything else uses pixels.


A minor comment on the code in your %Code% section:

You used a series of IF statements and there is nothing wrong with that but in this case a series of ELSEIF statements would actually be clearer. The ELSEIF clarifies that only one of the statements will be true - or, if multiple statements might be true then only the first one will be acted on.

This isn't a big deal until you (a) have to edit the code after not seeing it for a few months and (b) have a situation where one of the actions (typically the last one) is required to be a separate IF. For example, I have occasionally had to build %Code% for a modal xdialog where the value of a_dlg_button might get changed based on some other action and then a_dlg_button MUST be checked at the end for that value. In that case it's not obvious what's happening if it is just a series of IF statements. However, something like this makes it clearer:

%code%
IF a=b
<do something>
ELSEIF a=c
<do something else>
ELSEIF a=d
<do something else>
ELSEIF a=e
<do something else>
ELSE
<do something else>
a_dlg_button = "OK"
END IF

IF a_dlg_button = "OK"
<run validation checks>
END IF
%code%

When I see something like the above with a separate IF, it's a pretty good hint that something special is going on somewhere in the above ELSEIF routines. Without that separate IF I might never think to look above for a change to a_dlg_button since that's not a typical think to do. In most cases the a_dlg_button would only be "OK" if the user clicked the OK button but, in this case, there is one situation where a_dlg_button gets changed to "OK" in the previous code even though the OK button was not clicked.

Of course, the above is only a suggestion. It isn't required and it doesn't make a lot of difference at the time you are writing the code. However, it is better coding technique and, although I personally never have to go back and edit code, I understand that many developers do and it can be a lot easier to decipher your original intent when you use ELSEIF when that's what you really intended anyway. (And, yes, those who prefer it can use SELECT .. CASE instead.)

FWIW, it should also run a few milliseconds faster because it doesn't have to evaluate every IF statement after finding the first match. (Which usually won't matter unless it's in a loop that runs many times.)

[MikeC]

Re: resizing or maximizing xdialog

Same results regarding the xdialog resize function.

If wanting the Alpha window size you can use the following to determine it even if maximized....

?a5.left
= -4
?a5.top
= -4
?a5.width
= 1032
?a5.height
= 742
which makes the size 1028 x 738

If ever needing to compare pixels and inches Alpha provides the following functions--not a direct conversion is all.

Inches_to_Twips()
Pixels_to_Twips()
Twips_to_Inches()
Twips_to_Pixels()

[djldc]

Re: resizing or maximizing xdialog

Thanks Mike! Now I just need to wait for the next update which, according to Selwyn, corrects the presently non-functioning ui_dlg_resize() function. :)

Don