OpenEuphoria

RE: win32 and win98

• Posted by Al Getz <Xaxo at aol.com> Aug 02, 2003
• 450 views

Derek Parnell wrote:
> 
> 
> ----- Original Message ----- 
> From: "Al Getz" <Xaxo at aol.com>
> To: "EUforum" <EUforum at topica.com>
> Subject: RE: win32 and win98
> 
> 
> [snip]
> > 
> > The best way to get around this is to track down the functions
> > that use shared resources and find out if they are using the
> > correct flags.  This will probably clear up most of the problems.
> > 
> 
> Sounds fine to me. Two questions though...
> 
> ** What, specifically, are the shared resources (or how can I recoginize 
> a shared resource from a non-shared one)?
> 
> ** Which flags are you referring to? There are SO MANY flags about, I'm 
> not sure which ones are relevant to this specific issue.
> 
> -- 
> Derek
> 
Hello again Derek,

The actual problem i was referring to occurs when a listview control
is destroyed.  If the control uses system images and doesnt have
the "LVS_SHAREIMAGELISTS" flag set it will take out various
objects like folders that normally appear in Windows Explorer,
icons on the taskbar, and icons and folders on the desktop.

This condition is always recognizable by the fact that it happens
right after the listview control is destroyed, which usually
occurs when the application is closed, and that after a reboot
all the objects reappear normally.

The problem is of course solved by making sure that the
listview style flags includes LVS_SHAREIMAGELISTS.

If this isnt the problem, or if this is only part of the problem,
then i would have to see the actual code in its entirety in order
to tell what else might wrong.  I do have win 98 so it would 
appear on my system as well.  At this time, i dont have access to
a win XP machine that often, so i wouldnt be able to test it
on XP normally.

Let me know where i can find the code and the library version
and i'd be glad to take a look if this doesnt help.

Take care for now,
Al