1. testing win32lib font 'bug'
Haven't run into this problem with ver.0.45o yet, but here's the way to test
for the bug.
1.)Minimal system, preferably with next to nothing in Startup group.
2.)Start and minimize a number of 'text based' applications' which use
different selectable fonts.
...this obviously creates a number of different of 'font handles' on the
system.
3.)Run some win32lib programs, then:
4.)Check each minimized application to see if it's been corrupted yet.
...( Explorer and Taskbar are obvious 'hits' since they're usually running...
)
Wolf
