Win2K Issues .. was Black Background for new Toolbar icons

Bill,

> > It seems unlikely to help, as non-client elements (scroll bars) are
> > not being drawn.  It goes beyond appearance and gets to
> > functionality.

Erm, as I far as I was aware the only Win2K issues were the debugger
list pane (which is now solved-although I'm not quite sure why) and the
rather odd look of the TabViewXP backgrounds which don't respect their
background colours.

The only other report (I think) is this one from you:

> but basic inspectors (which I use in preference to the
> flipper for most things) do not draw their iv pane properly.
> Some elements are blank, the scroll bars and border (probably
> all nc elements) do not draw on first display.
> Nudge the splitter and all is well

Running under VMWare Win2K I don't see this myself, although it does
sound reminiscent of a general X6 bug (i.e. not specific to Win2K)
where some views occasionally don't draw correctly on first appearence
.. which we are trying to address.

The situation we are trying to get to is one where we can say that
running the IDE under Windows 2000 is "unofficially supported" (a) but
running deployed applications is (b), providing they don't make use of
Windows XP specific features (such as theming etc). We's also like to
be able to say the latter about Windows 98 if possible. Now this sounds
like it would fulfill most people's requirements in this area.

At the end of the day we want to ship this stuff ASAP. If people can
provide us with examples of problems with (b) then we will spend some
time trying to fix them or provide workaraounds. If you have examples
of problems with (a) that can be addressed by a "10 minute fix" then we
will look at these too. If you can supply fixes for either then that's
all the better.

However, if it turns out that some problems look too daunting to
address within the limited time left, then I'm afraid we will probably
have to just remove 2K from the supported list altogether. At the
moment, I'm rather confused as to what does and doesn't work in these
areas.

Best regards,

--
Andy Bower
Dolphin Support
www.object-arts.com

Andy,

> Erm, as I far as I was aware the only Win2K issues were the debugger
> list pane (which is now solved-although I'm not quite sure why)

I believe that that's because the list is now virtual.  Win2K won't do
#hasFlatScrollbars and #'isVirtual at the same time.

I suggest that it'd be better to fix that one by turning off the
#hasFlatScrollbars aspect, and leaving #isVirtual false.  The code evaluation
needed for the debugger's display causes problems sometimes as it is, and
making the list virtual can only make that worse.  OTOH, the #hasFlatScrollbars
is presumably an error ?  At least on Win2K and on WinXP "classic" the
scrollbars /are/ rendered flat and therefore don't match the other scrollbars.
On WinXP "emulated classic" the #hasFlatScrollbars is ignored (they work fine,
but the're still in 3d).  I guess that the setting is ignored on WinXP's
"normal" look too, or you would have noticed the mismatch.

    -- chris