At 10:20 AM 20/05/2001 -0700, you wrote:
gerard patel gerard.patel@asi.fr writes:
(patch using NC_HandleNCCalcSize instead of SetWindowPos)
IMO it's better and it solves my problem as well.
I think the SetWindowPos one was better. If the app handles WM_NCCALCSIZE we shouldn't try to bypass it.
But does Windows send this message in this case ? From what I can see in the traces, I don't think so. Maybe Maciek could look at the behaviour of his app under Windows. Or I could download it and try to solve the problem myself (I'd better not :-/)
Gerard
On Sun, May 20, 2001 at 11:33:45PM +0200, gerard patel wrote:
At 10:20 AM 20/05/2001 -0700, you wrote:
gerard patel gerard.patel@asi.fr writes:
(patch using NC_HandleNCCalcSize instead of SetWindowPos)
IMO it's better and it solves my problem as well.
I think the SetWindowPos one was better. If the app handles WM_NCCALCSIZE we shouldn't try to bypass it.
But does Windows send this message in this case ? From what I can see in the traces, I don't think so. Maybe Maciek could look at the behaviour of his app under Windows. Or I could download it and try to solve the problem myself (I'd better not :-/)
I have small experience in debugging apps under windows ,so any hints are welcomed.
In attachement WIN.3_11 you can see listing generated under windows 3.11. ( Borland WinSight ) (If you want get a listing generated under win98/95 - no problem , but I'll have to format&reinstall ,because this copy of windows stopped functioning about 6 months ago ) WINE_SETWINPOS ,WINE_NCALC- under wine with first and second version of patch. I think WINE_NCALC is more similar to WIN.3_11 .
I'm wondering why menu->Height == 0. I'll investigate it.
Maciek