avid
July 15th, 2004, 02:11 AM
Ben,
Marcel found a problem with the drop-down button in my new utils driver. He placed it in a frame which used a STATE to toggle visibility of the whole frame and its contents. Everything in the frame became correctly hidden EXCEPT my drop down (which is registered to be painted by my driver).
Unfortunately there is no call to the driver when the the parent of the driver-painted button changes visibility. I just simply do not know it has happened.
After an experiment where I polled the parent on a timer (where Marcel did not like the slight lag), I now have a temporary "workaround" where it is necessary to specify the same STATE variable as a qualifier to the drop-down button. But I would like to think that this is temporary and should not really be needed.
So, is the problem clear? And is there any chance of a new call to let me handle this case?
Brian
Marcel found a problem with the drop-down button in my new utils driver. He placed it in a frame which used a STATE to toggle visibility of the whole frame and its contents. Everything in the frame became correctly hidden EXCEPT my drop down (which is registered to be painted by my driver).
Unfortunately there is no call to the driver when the the parent of the driver-painted button changes visibility. I just simply do not know it has happened.
After an experiment where I polled the parent on a timer (where Marcel did not like the slight lag), I now have a temporary "workaround" where it is necessary to specify the same STATE variable as a qualifier to the drop-down button. But I would like to think that this is temporary and should not really be needed.
So, is the problem clear? And is there any chance of a new call to let me handle this case?
Brian