hi,

respect to Alaska, v331 "Patch" is much more than a Bugfix
it seem me faster, except activeX which is a little bit slower
than v350 BUT much more stable !!!

it seem me that it does better syncronsize Xbase++ "Output"
with activeX "Output" so Xbase++ sometime have to wait
a little for activeX grafic "Output", but it is a MUST.

now i can begin to remove my SLEEP(1) from v350 Code
while Xbase++ seem to take care of activeX "Output", GREAT !!!

a BUG on Win7rc1/FX5600 128MB with "lates" Nvidea Driver

every time i start a Xbase++ Application 1st Time a got
at XbpDialog only a Frame and "transparent" :drawingArea

this happend with Splashscreen and Login (Xbase++ GUI Sample)

i did not got it with v350 or v331+"hotfix" on Win7rc1 so it is "new"

Question : now while both Version have v1.9.355 how to report Error
if all DLL have same Version No. ?

greetings by OHR
Jimmy

hi,

in File C:\ALASKA\XPPW32\Source\SYS\xbparts.prg
XbpCombobox:HandleEvent Workaround is missing in v335 ("without visual 
Style")

greetings by OHR
Jimmy

hi,

still have "visual Style" in XbpBrowse() with Version v335 ("without visual 
Style")
must use ::Browser:useVisualStyle := .F. to get back Color in Header

::browser:getColumn(i):heading:setColorFG(GRA_CLR_YELLOW)
::browser:getColumn(i):heading:setColorBG(GRA_CLR_RED)

i "wish" Windows Manifest "Style" at Scrollbar, but

::Browser:hScrollObject:useVisualStyle := .T.
::Browser:vScrollObject:useVisualStyle := .T.

does not work with Version v335 ("without visual Style")

a Scrollbar is a Windows Part, it should follow Windows Style.
XbpBrowse is from Tbrowse, not a Windows Part no Style need
and we can use :setColorFG() / :setColorBG() as we like.

 greetings by OHR
Jimmy