1. Repeatable Win32Lib 'Resource' Problem
Hello,
Ive mananged to stumble upon a way to get the Win32Lib problem to
reoccur. I was testing something else resource related when this
happened.
Ive taken example5 (two buttons) and changed the position of the
window to something like 10,10,200,200 so that when you open
several exw's of that example at the same time, the windows
pile on top of each other neatly. That's the only change.
Here's when the problem occurs:
Open at least one instance of Explorer (i'll explain this later)
and have it visible in a part of the window (all panes and cb's).
Open 20 to 30 of the .exw seeing two buttons in each window.
Once all are open, move the windows around by moving them
one by one to a different part of the screen, again stacking them
one on top of the other (makes later work easier).
While doing this, note that NO font has been set for BOLD in
either of the two buttons, nor in Explorer. In other words,
verify that nothing is wrong with the screen fonts, Explorer fonts,
nor in the (possibly 60) buttons created with the exw files.
Now begin closing out the exw examples (that are stacked) by clicking
on the upper right 'x' and keeping an eye on the font of the buttons.
Eventually, one exw example will be closed out and the window
underneath it will have what looks like 'bold' font, when it didnt
have that before any windows were closed out.
After all windows are closed, check the fonts in all the child
windows of Explorer to see if any have changed to 'bold'.
Also check the screen icons to see if any of their fonts have
changed to bold (text like 'Shortcut to...').
In all cases tested so far, there has been at least one button
font changed to 'bold' upon closing an example exw window,
but usually two or three change.
In some cases tested, one window of Explorer changes it's font to
bold also (Listview, Combo box, status bar).
In cases where it affects a window, that window can be closed
and the problem seems to disappear when reopened (for that app).
When the problem occurs such that the desktop icons text changes,
the only way to correct the problem is to reboot.
The GDI resource meter is at 80% or greater at the time this
occurs.
The only guesses i have so far is that maybe there is something
wrong with the way a DC is destroyed, a font is selected into
a DC, or a font is destroyed, or the order of destruction is
not correct between fonts and DC's, or something else like that.
If i remember right, this also occurs if you keep selecting
a font into a DC without destroying the old one?
I'd have to look at this again though.
Also, it's not that the font is really getting it's attrib set
to 'bold', what is actually happening is the default system font
is being selected into the device contexts somehow, which looks
bold. How it gets to device contexts that arent gotten from
the exw program i dont know yet.
It doesnt seem to be a resource depletion problem because
it only happens AFTER a control is destroyed.
Of course if you open many more instances of the exw
this isnt true however, and strange errors really begin to
crop up, like missing icons, an error that reads
"the compiler has run out of memory".
(I've never seen that error before, but it's probably a resource
depletion error and not Win32Lib).
At least this is one way to reproduce the problem.
Take care for now,
Al
2. Re: Repeatable Win32Lib 'Resource' Problem
----- Original Message -----
From: "Al Getz" <Xaxo at aol.com>
To: "EUforum" <EUforum at topica.com>
Subject: Repeatable Win32Lib 'Resource' Problem
>
>
> Hello,
>
> Ive mananged to stumble upon a way to get the Win32Lib problem to
> reoccur.
Thanks, Al. All help is welcomed. I continue this trek... 
--
Derek
3. Re: Repeatable Win32Lib 'Resource' Problem
This may or may not be related.
I am running Mike's editor (the EU one) and close my XP laptop so it will
now go to suspend mode.
When I open it back up to continue to work I get a looping error message as
follows
error code 454
getDC:SelectObject(pixmap) failed.
the looping goes on forever until I click cancel or ignore.
I'm using an exe version of the editor that was using win32 55.5
george
----- Original Message -----
From: "Derek Parnell" <ddparnell at bigpond.com>
To: "EUforum" <EUforum at topica.com>
Sent: Sunday, August 03, 2003 5:43 PM
Subject: Re: Repeatable Win32Lib 'Resource' Problem
>
>
> ----- Original Message -----
> From: "Al Getz" <Xaxo at aol.com>
> To: "EUforum" <EUforum at topica.com>
> Sent: Monday, August 04, 2003 1:16 AM
> Subject: Repeatable Win32Lib 'Resource' Problem
>
>
> > Hello,
> >
> > Ive mananged to stumble upon a way to get the Win32Lib problem to
> > reoccur.
>
> Thanks, Al. All help is welcomed. I continue this trek...
>
> --
> Derek
>
>
>
> TOPICA - Start your own email discussion group. FREE!
>
>
4. Re: Repeatable Win32Lib 'Resource' Problem
On Mon, 4 Aug 2003 08:21:30 -0400, George Walters <gwalters at sc.rr.com>
wrote:
>This may or may not be related.
>
>I am running Mike's editor (the EU one) and close my XP laptop so it =
will
>now go to suspend mode.
>
>When I open it back up to continue to work I get a looping error message=
as
>follows
>
>error code 454
>getDC:SelectObject(pixmap) failed.
>
>the looping goes on forever until I click cancel or ignore.
To be honest, george, I've seen similar many times, but I don't think
it is especially related to suspend mode. Sometimes, it does happen
right off from running MEditor, but actually, when another program
gives up the ghost, it is *rare* when I can shut down MEditor (or
carry on for long) without one of those (or similar) popping up.
The bad news is your display is knacked, until reboot. (The really bad
news, of course is we have no real idea what causes it so I have no
strategy to help any, sorry). The good news is MEditor will honour Alt
=464 if you click ignore, even though you can't see that happening,
possibly a few returns may be needed to the save changes to XXX
prompts, before you reboot. (But clicking cancel will kill the app &
all unsaved edits, though).
Personally, I run the editor with auto-save on, which some hate, but
since I make regular backups (albeit to the same hard disk, tsk!), and
can undo over an auto save, I don't see what the problem is.
>I'm using an exe version of the editor that was using win32 55.5
I'm still working on migrating to a more recent version, don't hold
your breath, though.
Pete
