> On 07/20/12 03:42, Jayaram wrote: > >> PiBJIHByZXMgdGhlIGJ1dHRvbiBhbmQgdGFrZSBteSBoYW5kcyBhd2F5IGZyb20gdGhlIHNjcmVl > >> bg0KPiB0aGVyZSBpcyBhIGRlbGF5IGZvciB0aGUgaW5mb3JtYXRpb24gYm94IHRvIGFwcGVhciBh > >> bmQgdGhlIHRleHQgdG8gYmUNCj4gZGlzcGxheWVkLiBCdXQgYWZ0ZXIgcHJlc3NpbmcgdGhlIGJ1 > >> dHRvbiwgaWYgaSBrZWVwIGl0IHByZXNzZWQgb24gdGhlDQo+IHRvdWNoIHNjcmVlbiwgdGhlIGJv > > > > Hello Ian , > > Sorry, your message is unreadable again. > > He wrote: > * * * > > > I pres the button and take my hands away from the screen > > there is a delay for the information box to appear and the text to be > > displayed. But after pressing the button, if i keep it pressed on the > > touch screen, the box appears a lot quicker and text is displayed. > > Am unable to understand the reason for this behavior !! > > This is just another vote to say thios sounds very much like > delayed redraw() behaviour, so adding an explicit call to redraw > the widget (or perhaps its parent widget) may well bring improved behaviour. > > * * *
Sorry i haven't yet posted the code yet. But i see that a redraw is being called on the widget. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
