Here is what I want you to do:

Create a new window.

Add a list box and name it "LB".

Bring up the Properties window and

- make the list box hierarchical

- set the Bitmap Entity to "OR_TIME", and Number of Images=4

- set Items to the two lines

  1-1:One

  1-1:Two

Then make a user Create event for the window, where the bitmap is changed to OR_SAVE:

  call Set_Property( @Window : ".LB", "BITMAP", "BMPS/OR_SAVE.BMP" )

  call Set_Property( @Window : ".LB", "IMAGECOUNT", 4 )

Now test run the window. With me the two lines appear in the list box, each with an image taken from the programmatically set bitmap OR_SAVE (a diskette). When I click on a line the image changes to an image taken from the design time bitmap OR_TIME (a clock).

If I try the same without a design time bitmap I get no images at all.

Is this the same with you?

I run 3.3. Is this fixed in 3.5? Or have I perhaps done something wrong?

- Oystein -

Tested in 3.5r3, same errant behaviour as you are getting.

Barry Stevens

Thanks a lot, Barry!! Now I don't feel so lonely any more.

Can anybody out there help me with this? RevSoft guys - is there a workaround? Are there perhaps other properties that I can set? Or am I doing something that's not meant to be done?

- Oystein -

Oystein,

I believe this is not a "bug" per se but rather Set_Property is an inadequate way of modifying the bitmap of a hierarchical listbox.

I don't have independent confirmation yet but I'm pretty sure this is one of those times where the control has to be destroyed and re-created in order for this type of alteration to work. Using your example, I used the following code instead:

Declare function Utility

Struct=Get_Property(@Window:".LB", "ORIG_STRUCT")

Struct=BMPS\OR_SAVE.BMP"

rv=Utility("DESTROY", @Window:".LB")

rv=Utility("CREATE", Struct)

This seems to work pretty well and without much of a noticeable "flicker" either.

Hope this helps,

dbakke@srpcs.com

SRP Computer Solutions

View this thread on the forum...