> >> > I am handling the frmUpdateEvent to redraw my form after
> >> > returning from a dialog form. My problem is the form now blinks
> >> > when it is erased and then redrawn.
> >>
> >> if you don't erase and redraw the whole form in your frmUpdateEvent
> >> branch, it shouldn't happen - at least it doesn't with me. normally
> >> you only have to do that when responding to update code zero.
> >
> >I'm not sure what is going on but when I use FrmDrawForm in my
> >frmUpdate handler my fields blink. First the come back blank, then
> >they are drawn, then they are blank again, then redrawn again.
> >
> >If I use FldDrawForm and CtlDrawControl for each field and control
> >instead of FrmDrawForm, they do not blink. I have tried various
> >codes for FrmUpdateForm without any change.
> >
> >The question I have with this method is that I also have a bitmap
> >that also needs to be redrawn and I'm not sure how to force a bitmap
> >to be drawn. Currently I let the form take care of that but how
> >would I specify and force the redrawing of the bitmap?
> >
My bitmap is just added as part of my form when I create the form. I
don't currently use any functions to handle the bitmap.
> The only way I can think offhand of doing that is to save the
> bitmap and redraw it. If it were drawn in it's own separate window,
> it might be a little cleaner to refresh it. You can use BmpDelete and
> BmpCreate, calling BmpGetBits & BmpBitsSize first to get the data bits
> from it, and BmpGetColorTable & BmpColortableSize and BmpSize to get
> the colortable and sizes. (Or maybe use ColorTableEntries macro)
> Store that information, delete the bitmap, then recreate it with that
> information. (I don't know if this will work, I haven't really tried
> it...I usually just delete the bitmap object, then redraw it from a
> resource file, and not on the fly) -Rus
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/