Well, right now the WinUXTheme works well for other themes. BTW, I dearly wish you hadn't named your theme "Windows Classic" when people also use the same term to refer to the classic theme under Windows. It makes it very difficult to refer to them separately. :)
Nevertheless the only step forward for the WinUXTheme right now is to fix this bug in the way I suggested. Yes, there are bugs, but this is by far the most prominent one. GC On Sun, Jun 26, 2011 at 2:13 PM, Riccardo Mottola <[email protected]> wrote: > Gregory, > > I believe getting them to work separately well enough so that they can be > released is much more important. I don't consider either of them > presentable. > > I want the windows classic theme to work alone: it enables to use it on > windows 2000 or ReactOS for example or even other Unix distributions as a > CUA-compliant theme. If you use fvwm with a windows style, the theme would > be your best bet probably > > Once they will work, we can think if merging them makes sense. It needs some > tinkering when both versions of the theme have a bitmap. > > In Italy we say: don't make a stride longer than your leg. > > Riccardo > > Gregory Casamento wrote: >> >> Riccardo, >> >> I believe the best course of action here is to expand the WinUXTheme >> to support the classic theme on Windows properly by using bitmaps when >> that particular theme is chosen. Switching manually between the >> WinUXTheme and the "Windows Classic Theme" which resides in GAP is >> somewhat clunky. >> >> GC >> >> >> > > -- Gregory Casamento - GNUstep Lead/Principal Consultant, OLC, Inc. yahoo/skype: greg_casamento, aol: gjcasa (240)274-9630 (Cell) _______________________________________________ Discuss-gnustep mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnustep
