Hi all, hi Eugene.
You said "flood us with bug reports", so I'm trying to do my best But you should be a bit more responsive... most of the issues I posted in these forums have not been replied to. A reply just to say "I have seen your message, we are investigating" would be appreciated.
I have almost all of your (EcoSoft) software registered and installed!

Let's go to the point: bug reports.

- eSchemes v1.40 doesn't play well with PianoPad (see other thread by Gabriele Gamba), even with the latest PianoPad and latest eCO-runtimes.

- eSchemes v1.40 doesn't replace correctly all title-bar controls: the control-box (the control in the upper-left part of any window) is not updated for windows that do not have an own icon (e.g. dialog windows or the window-list). See

- System Setup -> Appearence -> eStyler Preferences doesn't work anymore. IIRC it worked when I installed eSchemes v1.40, but it broke after another package (eCO-RT?) was installed afterwards. In POPUPLOG.OS2 I have the following:

- When applying a scheme, if immediately after I open the desktop proerties notebook and go to the "Background" tab, the WPS resets itself. After this reset the WPS restarts with the "lockup" page (as if you had chosen "Lockup Now" from the context menu). At this point I have to restart the whole system by pressing C-A-D repeatedly. If instead I try to unlock it by typing the password, the "lockup" screen goes away, but the system is locked up so hard that I have to cycle the power.

These are the first bugs that come to mind... others may follow.
Hope this helps!
Bye

Another problem: with at least two of the schemes (Winter and eCOToys) there are windows that are not readable because of the fact that the foreground and the background colors are the same.
For example, this is a screenshot of the "File Open" dialog of QDVDAuthor (an app ported from Linux, using the QT3 port):
I don't know if the problem is in eSchemes or in the port. It seems (but I can't be completely sure) that apps using plain PM don't have the problem, while those using custom controls are more easily broken by the application of a scheme.

Eugene,
I am finding more and more apps that show this weird behavior when an eScheme is applied. And they are native apps too. One example is PMView 2000, which does not show some controls in the preferences notebook.
I also find that when this happens (i.e. when controls are hidden) the CPU will jump to 100% and stay there until I close the buggy window.