I found out that you added a new "CONFIG" clause to DCBROWSE, which defaults to the result of the function "DC_XbpBrowseDefault" and needs a "DC_XbpBrowseConfig"-object otherwise. Since DCBROWSE doesn't show the transparent browse markers (Vista/7) anymore (this worked until build 252), I tried to find the reason for this and digged out the CONFIG-clause. But this has no effect:
I'm not sure what you mean by transparent browse markers.
I recall making a change to the DC_XbpBrowse() class because of complaints that it did not work correctly with Vista and SL1, but now I will need to compare source code of 252 with 251 to see what I changed.
I think that I started writing a DC_XbpBrowseConfig() when I had the idea to experiment with ownerdraw of the XbpBrowse() class but then realized that it was too difficult and Alaska gave no samples.
Can you take a picture of what you are expecting to see?
The eXpress train is coming - and it has more cars.
Can you take a picture of what you are expecting to see?
I'm currently trying to do so. Maybe Alaska changed something there with the latest hotfixes? I remember their "QBROWSE2" sample came up with a rounded, gradient filled, transparent cell marker on my Windows 7 system, but it does not do this anymore.
Best regards,
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Just for the records: This problem is fixed with the new hotfix rollups (# 25 to 28), which were provided by Alaska yesterday. Vista and Windows 7 now show transparent browse markers again.
Best regards,
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."