> > Because the underlying toolkit uses its own "picture" object that is not
> > automatically reassigned to the control automatically. In other words,
> > assume that the Picture property returns a copy of the underlying
> > picture.
>
> I hope this doesn't create extra unneeded picture objects i
2009/11/28 David Dell :
>> the underlying toolkit
> I hope this doesn't create extra unneeded picture objects in memory,
> for any number of times without memory penalties.
>
> Please confirm this.
He said "the underlying toolkit". that means it is out of Benoit's control.
> Because the underlying toolkit uses its own "picture" object that is not
> automatically reassigned to the control automatically. In other words, assume
> that the Picture property returns a copy of the underlying picture.
I hope this doesn't create extra unneeded picture objects in memory,
so I
> Let's say first I assign a picture to a menu:
>
> DIM Pic AS Picture
> Pic = NEW Picture(18, 18)
> Pic.Fill(Color.Black)
> MenuCustomColor.Picture = Pic
>
> When I try to modify a picture assigned to a menu, if I use
>
> MenuCustomColor.Picture.Fill(Dialog.Color)
>
> it does not do
Let's say first I assign a picture to a menu:
DIM Pic AS Picture
Pic = NEW Picture(18, 18)
Pic.Fill(Color.Black)
MenuCustomColor.Picture = Pic
When I try to modify a picture assigned to a menu, if I use
MenuCustomColor.Picture.Fill(Dialog.Color)
it does not do anything.
Instead I hav
