I just found that the new version causes flickering with... VISTA
Argh! those "small" differences between Microsoft's OS, have always been a pain for us, low level SDK programmers :'(
This new version works well, with both XP and VISTA, and it is flicker free on both OS.
So far I didn't check with 2000, I hope it should work well with it too ;)
Patrice Terrier
www.zapsolution.com
Checked under WinXP and Vista (VMWare emulated). All fine.
Under Win2K application doesn't start at all, no error, no messages. I have GDI+ installed because other applications using GDI+ works.
Under Taskmanager seems the process starts and immediatelly ends but no user interface is visible.
Ciao
Eros
I still have a computer running native Windows 2000, I shall make a try on it and see if I can diagnostic the problem ...
I don't know if the WS_EX_COMPOSITED extended style is supported on 2000, must check that first.
patrice
All perfect under Win2K just commenting out:
dwExStyle = %WS_EX_COMPOSITED
Thanks a lot
Eros
In this case just replace the current
dwExStyle = %WS_EX_COMPOSITED
by this
dwExStyle = 0
IF zOsVersion > 500 THEN dwExStyle = %WS_EX_COMPOSITED '// XP and above
Then, no built-in double buffer in Windows 2000.
patrice
"GdipCreateFontFamilyFromName" (zFontName AS ASCIIZ, BYVAL fontCollection&, fontFamily&) AS LONG
how about byval FontName AS string ?
Sorry did not finish posting... does this debug ok for you
Mike
Quotehow about byval FontName AS string ?
Indeed it is a UNICODE ASCIIZ string (wide):
With PB9 you can use GdipCreateFontFamilyFromName((UCODE$(UseFont$)), 0, Fam&).
With PB10 better to use the new native WSTRINGZ.
...
The first post of this thread has been updated, to fix the ZIP file corruption caused by the "Server Collapse".
...