Announcement

**Michael Mattias** · 7 Jul 2009, 08:44 AM

If you think the problem is occuring in WM_SIZE...

Code:

%WM_SIZE
          LOCAL HwndMainRect AS RECT
          LOCAL x AS LONG
          LOCAL y AS LONG
          LOCAL xx AS LONG
          LOCAL yy AS LONG
'*** Get Toolbar and statusbar height
          GetWindowRect HwndMain, HwndMainRect
MSGBOX STR$(HwndMainRect.nLeft) + "," + STR$(HwndMainRect.nBottom)
          DIALOG PIXELS HwndMain, HwndMainRect.nLeft, HwndMainRect.nBottom TO UNITS HwndMainRect.nLeft, HwndMainRect.nBottom
MSGBOX STR$(HwndMainRect.nLeft) + "," + STR$(HwndMainRect.nBottom)
'MSGBOX STR$(xx) + "," + STR$(yy)

... first thing get the MSGBOXs out of there. Those run more-or-less asyncronously and you can be creating re-entrancy problems. Use TRACE PRINT or STDOUT or write to a log file or something else.

I'd go for the TRACE PRINT for the simple reason I'd like to see how far the program gets before it faults out. TRACE is great for that.

The PBNOTE2 example is moot, since that window is already created in Pixels and I don't know why you'd want dialog units... and although I doubt this would be a problem, DIALOG PIXELS TO UNITS is a DDT command being used against a non-DDT window.

Lastly, you have enough experience by now to know that when you get a protection fault termination in a "wicked huge program", the 'real' error could have occurred many many instructions ago; that is, whatever is really happening on WM_SIZE (code shown does nothing except calculate some dimensions) is just the first place some earlier untrapped error exhibits itself.

First thing I'd do is enable a TRACE in "wicked huge program" and see if that can get me to a place where the real problem can be isolated.

**Cliff Nichols** · 7 Jul 2009, 03:04 PM

It appears you are partially right. However I did discover if trying to go from Units to Pixels then no problems.

SDK Tests

Code:

'¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤
' Declares
'¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤
#COMPILE EXE
#INCLUDE "WIN32API.INC"
'----------------------------------------------------------------------
GLOBAL g_hInst        AS DWORD
GLOBAL g_hWndMain     AS DWORD
GLOBAL g_hMenu        AS DWORD

'----------------------------------------------------------------------
DECLARE FUNCTION WndProc (BYVAL hWnd AS LONG, BYVAL wMsg AS LONG, _
                          BYVAL wParam AS LONG, BYVAL lParam AS LONG) AS LONG

'¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤
' Program entrance
'¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤
FUNCTION WINMAIN (BYVAL hInst AS LONG, BYVAL hPrevInstance AS LONG, _
                  BYVAL lpszCmdLine AS ASCIIZ PTR, BYVAL nCmdShow AS LONG) AS LONG
TRACE NEW "ErrorLog.txt"
TRACE ON
  LOCAL hDlg AS LONG, hCtl AS LONG, hFont AS LONG, _
        wce AS WndClassEx, szClassName AS ASCIIZ * 80

  hFont = GetStockObject(%ANSI_VAR_FONT)

  ' Register Main Window Class
  szClassName       = "TestSdk"
  wce.cbSize        = SIZEOF(wce)
  wce.STYLE         = %CS_HREDRAW OR %CS_VREDRAW
  wce.lpfnWndProc   = CODEPTR(WndProc)
  wce.cbClsExtra    = 0
  wce.cbWndExtra    = 0
  wce.hInstance     = g_hInst
  wce.hIcon         = LoadIcon(g_hInst, "APPICON")
  IF wce.hIcon = 0 THEN 'if no resource icon, give it a system icon..
     wce.hIcon = LoadIcon(0, BYVAL %IDI_APPLICATION)
  END IF
  wce.hCursor       = LoadCursor(%NULL, BYVAL %IDC_ARROW)
  wce.hbrBackground = %NULL
  wce.lpszMenuName  = %NULL
  wce.lpszClassName = VARPTR(szClassName)
  wce.hIconSm       = LoadIcon(g_hInst, BYVAL %IDI_APPLICATION)

  IF RegisterClassEx(wce) = 0 THEN
      RegisterClass BYVAL (VARPTR(wce) + 4)
  END IF
  g_hWndMain = CreateWindow("TestSdk", _      ' Main window's class name
                            "TestSdk", _      ' Main window's initial caption
                            %WS_OVERLAPPEDWINDOW, _   ' window style
                            (GetSystemMetrics(%SM_CXSCREEN) - 640) / 2, _  ' initial x position
                            (GetSystemMetrics(%SM_CYSCREEN) - 480) / 2, _  ' initial y position
                            640, _                    ' initial x size
                            480, _                    ' initial y size
                            %NULL, _                  ' parent window handle
                            g_hMenu, _                ' window menu handle
                            g_hInst, _                ' program instance handle
                            BYVAL %NULL)              ' creation parameters

  ShowWindow g_hWndMain, nCmdShow
  UpdateWindow g_hWndMain

  LOCAL Msg AS tagMsg
  WHILE GetMessage(Msg, %NULL, 0, 0)<>0
     TranslateMessage Msg
     DispatchMessage Msg
  WEND

  FUNCTION = msg.wParam
END FUNCTION

'¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤
' Main Window procedure
'¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤
FUNCTION WndProc (BYVAL hWnd AS LONG, BYVAL wMsg AS LONG, _
                  BYVAL wParam AS LONG, BYVAL lParam AS LONG) AS LONG
TRACE ON
  SELECT CASE wMsg
     CASE %WM_CREATE
     CASE %WM_COMMAND
     CASE %WM_DESTROY
        PostQuitMessage 0
        FUNCTION = 0 : EXIT FUNCTION
     CASE %WM_SIZE
        IF wParam <> %SIZE_MINIMIZED THEN
          LOCAL HwndMainRect AS RECT
          LOCAL x AS LONG
          LOCAL y AS LONG
          LOCAL xx AS LONG
          LOCAL yy AS LONG
'*** Get Toolbar and statusbar height
          GetWindowRect g_hWndMain, HwndMainRect
#DEBUG PRINT STR$(HwndMainRect.nLeft) + "," + STR$(HwndMainRect.nBottom)
'*** None of the below work PIXELS ---> UNITS
'          DIALOG PIXELS g_hWndMain, HwndMainRect.nLeft, HwndMainRect.nBottom TO UNITS HwndMainRect.nLeft, HwndMainRect.nBottom
'          DIALOG PIXELS g_hWndMain, HwndMainRect.nLeft, HwndMainRect.nBottom TO UNITS xx, yy
'          DIALOG PIXELS g_hWndMain, 480, 840 TO UNITS xx, yy
'          DIALOG PIXELS g_hWndMain, x, y TO UNITS xx, yy
'*** Reverse the order though and no crash UNITS ---> PIXELS
          DIALOG UNITS g_hWndMain, x, y TO PIXELS xx, yy
'          DIALOG PIXELS g_hWndMain, x, y TO UNITS xx, yy
#DEBUG PRINT STR$(HwndMainRect.nLeft) + "," + STR$(HwndMainRect.nBottom)
        END IF
  END SELECT
  FUNCTION = DefWindowProc(hWnd, wMsg, wParam, lParam)
END FUNCTION

DDT Tests ---> Code not shown due to no problems using PB commands on DDT windows, so works as advertised.

Maybe I should submit this to PB??? (But the back of my mind I could swear this affect is already documented????

**Michael Mattias** · 7 Jul 2009, 06:58 PM

Let me re-guess...

DIALOG UNITS to PIXELS and PIXELS TO UNITS may in Fact be "DDT windows only" if PB saves the dimensions internally and converts on the fly (as you can do yourself).... then when it tries to find the "UNITS" in a screen it is not managing it finds NOTHING.

Does your x00005 exception report the failing address as 0x0000000 (Null pointer)? If so, that would kind of tend to support this theory.

Let's see, converting units to Pixels... start with the GetDlgBaseUnits() function. I think the two-step formula is on the SDK reference page for that. I think MapWindowPoints() might work, too.

But why you'd be working with UNITS on a non-DDT window is a mystery.. all SDK operations on non-dialog windows return or use nothing but pixels; and even with SDK-Created dialogs, I think dialog units are used ONLY in the CreateDialog[Indirect] or DialogBox[Indirect] calls.. after that everything is done in pixels.

MCM

**Cliff Nichols** · 7 Jul 2009, 08:25 PM

DIALOG UNITS to PIXELS and PIXELS TO UNITS may in Fact be "DDT windows only" if PB saves the dimensions internally and converts on the fly (as you can do yourself).... then when it tries to find the "UNITS" in a screen it is not managing it finds NOTHING.

if PB saves the dimensions internally and converts on the fly (as you can do yourself)

OK so how do I do that??? to my knowledge I can only get pixels....and it may be my fatal flaw (as in math...the moment you forget units, the math is flawed)

Does your x00005 exception report the failing address as 0x0000000 (Null pointer)? If so, that would kind of tend to support this theory.

I will have to check under XP in the morning, cause Vista (at least in my case) either wants me to report, or debug.....and nothing to debug with outside trace, pb, pbdebug, anything short of somehow hooking my own program.
Although the memory addresses are REALLY familiar (like I have not seen them before

)

But why you'd be working with UNITS on a non-DDT window is a mystery.. all SDK operations on non-dialog windows return or use nothing but pixels;

Well I did say I was trying to clean up mistakes of the past, (mix and match SDK with DDT) so reading docs I thought converting values in DDT (Dialog Units) to SDK (Pixels) would be one to try to look at.....(I knever knew though why (fully) why it involved a Dialog (sort of like Pixels vs Twips vs Dialog Units vs (Heyheaaa I got a new unit)))))

I should go about the whole problem in another way (Convert values (in units) to Values (in Units) and NOTTTT care what the dialog(or Window) is, and match units for units.

Only problem is...how do yu convert Dialog Units to pixels? Or Pixels to Dialog Units???

In the world of "Mr. Owl....the world may never know"

**Michael Mattias** · 8 Jul 2009, 07:15 AM

Well, bad memory. It's not "GetDlgBaseUnits", it's "GetDialogBaseUnits"

And the formula is ..

Each horizontal base unit is equal to 4 horizontal dialog template units; each vertical base unit is equal to 8 vertical dialog template units. Therefore, to convert dialog template units to pixels, use the following formulas:

Code:

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

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

Code:

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

However, in the comments for GetDialogBaseUnits() Ye Olde SDK doc says...

For either type of dialog box, it is easier to use the MapDialogRect function to perform the conversion. MapDialogRect takes the font into account and correctly converts a rectangle from dialog template units into pixels.

MCM

Announcement

Invalid Memory Address

Invalid Memory Address

Comment

Comment

Comment

Comment

Comment