R
Rik Hemsley
Hi,
I'm using a ListView in Details mode and have assigned an ImageList to
it via its SmallImageList property.
If I make a trivial change to the code of my application, and then run
it, the images show up within the ListViewItems as expected.
The next time, and each subsequent time, that I run my application
(through the VS.NET 2003 debugger or compiled and outside VS.NET), the
images do not appear. It appears that display space is reserved for
them, but they show as blank.
If I make another trivial change (such as clearing a list which has just
been created), the images will be displayed in the next run of the
application.
This behaviour is quite consistent, though on a few occasions I have
managed to run the application twice before the icons start disappearing.
The images are loaded from embedded resources and I have checked with
the debugger that they are always loaded correctly and added to the
ImageList.
I cannot fathom how it is possible for this problem to occur only on the
second and subsequent runs after a compile.
A trivial test application does not have the same problem.
Rik
I'm using a ListView in Details mode and have assigned an ImageList to
it via its SmallImageList property.
If I make a trivial change to the code of my application, and then run
it, the images show up within the ListViewItems as expected.
The next time, and each subsequent time, that I run my application
(through the VS.NET 2003 debugger or compiled and outside VS.NET), the
images do not appear. It appears that display space is reserved for
them, but they show as blank.
If I make another trivial change (such as clearing a list which has just
been created), the images will be displayed in the next run of the
application.
This behaviour is quite consistent, though on a few occasions I have
managed to run the application twice before the icons start disappearing.
The images are loaded from embedded resources and I have checked with
the debugger that they are always loaded correctly and added to the
ImageList.
I cannot fathom how it is possible for this problem to occur only on the
second and subsequent runs after a compile.
A trivial test application does not have the same problem.
Rik