Dialog Coordinates

[Bayron]

Hi all,
Is there any difference between Window Coordinates and Dialog Coordinates????

I built a separate .prg file using a window, I obtained the size of it by using WndHeight( GetDesktopWindow() ), WndWidth( GetDesktopWindow() ) I calculated the coordinates using oWnd:nHeight and oWnd:nWidth, all the controls were placed and sized logically using percentages of this coordinates…
Now I am adding this .prg to my main program and for that reason, I am changing the Window to a Dialog, but now all controls appear to be double the size of what they were supposed to be….

This is a pretty big .prg file, with thousands of logical calculations for size and position, and I just want to know if there is something special about Dialogs that I need to know to make my calculations???

EDITED1:
I tested msginfo( oDialog:nwidth )
and It returned the right coordinates in pixels...
It seems that the size of the dialog is right, but the size and position of the controls are not... How is this possible, I just change from DEFINE WINDOW to DEFINE DIALOG??

EDITED2:
Dividing oDlg:nHeight and oDlg:nWidth by 2, it shows the controls in the right place... (This can't be Right) I think I am going to wait for FiveTech on this one, I don't want to change 1,000 lines and find out I only needed:

One line of code to get it done...

I only changed the calculations for the splitters!!!

[nageswaragunupudi]

Dividing oDlg:nHeight and oDlg:nWidth by 2, it shows the controls in the right place.

That is right.
This is the difference between windows and dialogs.
Fivewin has nothing to do with it. It is Microsoft Windows behavior.

We need to do all our calculations to position the controls keeping this in mind.

[Bayron]

Thanks Mr. Rao, I did not knew that...

[Bayron]

I Wonder why GradientFill, did not needed the divided by 2 calculation???

[nageswaragunupudi]

In the ON INIT clause, we do not have to do 1/2

[Bayron]

Now I fully undestand it's behavior because of your good explanation...

Thanks a lot Mr. Rao...

[Bayron]

In the ON INIT clause, we do not have to do 1/2

Next time I am going to read my own Forum Signature and believe in it:

FiveWin, One line of code and it's done...

I am almost done... after not sleeping last night..., and I just realized that I only needed to change a few lines of code:

Create a function to be called from the ON INIT clause to build the controls, Copy and Paste and Done...

Some times we do dumb things because: who does not know is like who does not see...

[nageswaragunupudi]

Clever

[Antonio Linares]

http://msdn.microsoft.com/en-us/library/ms645475(VS.85).aspx

baseunitX = nLoWord( GetDlgBaseUnits() )
baseunitY = nHiWord( GetDlgBaseUnits() )

Therefore, to convert dialog template units to pixels, use the following formulas:

pixelX = MulDiv(templateunitX, baseunitX, 4);
pixelY = MulDiv(templateunitY, baseunitY, 8 );

Similarly, to convert from pixels to dialog template units, use the following formulas:

templateunitX = MulDiv(pixelX, 4, baseunitX);
templateunitY = MulDiv(pixelY, 8, baseunitY);

[Antonio Linares]

An example:

testdlgu.prg // Testing dialog base units

Code: Select all  Expand view

#include "FiveWin.ch"

function Main()

   local oWnd, cTest := Space( 20 )

   DEFINE WINDOW oWnd TITLE "A window"
   
   @ 20, 20 SAY "Hello" SIZE 80, 20 PIXEL
   
   @ 20, 60 GET cTest SIZE 80, 20 PIXEL

   @ 80, 60 BUTTON "Ok" SIZE 80, 20 PIXEL

   @ 80, 180 BUTTON "Cancel" SIZE 80, 20 PIXEL

   Dialog( oWnd )

   ACTIVATE WINDOW oWnd ;
      ON CLICK MsgInfo( oWnd:nWidth )

return nil

#define SM_CXDLGFRAME 7

function Dialog( oWnd )

   local oDlg, cTest := Space( 20 )
   local factorX := 4 / nLoWord( GetDlgBaseUnits() )
   local factorY := 8 / nHiWord( GetDlgBaseUnits() )

   DEFINE DIALOG oDlg TITLE "A dialog" ;
      SIZE oWnd:GetCliRect():nWidth - 2, oWnd:GetCliRect():nHeight - 2

   @ 20 * factorX, 20 * factorY SAY "Hello" SIZE 80 * factorY, 20 * factorX PIXEL

   @ 20 * factorX, 60 * factorY GET cTest SIZE 80 * factorY, 20 * factorX PIXEL
   
   @ 80 * factorX, 60 * factorY BUTTON "Ok" SIZE 80 * factorY, 20 * factorX PIXEL

   @ 80 * factorX, 180 * factorY BUTTON "Cancel" SIZE 80 * factorY, 20 * factorX PIXEL

   ACTIVATE DIALOG oDlg CENTERED NOWAIT ;
      ON CLICK MsgInfo( oDlg:GetCliRect():nWidth - oWnd:GetCliRect():nWidth )

return nil

[Bayron]

Thanks for the excelent example Mr. Linares...
That should be the right way to doit, but I worked out fine for me dividing everything by 2 as well...

All the controls are calculated automatically and sized to the screen resolution... even the fonts

[Antonio Linares]

Bayron,

You are welcome

Still there is a little difference between the width and height of the window and the dialog, not sure exactly why...

[James Bott]

I found that using 2.05 for the divisor worked better for me.

Regards,
James

[Antonio Linares]

James,

It depends on the used font, thats why its better to call GetDlgBaseUnits() provided by Windows API as I used in my example above

[James Bott]

Antonio,

>It depends on the used font, thats why its better to call GetDlgBaseUnits() provided by Windows API as I used in my example above

I totally agree. My 2.05 value I came up with many, many years ago--probably with Win98. It worked OK then, but your system is better.

James