This code is part of a much larger code. I'll put together a smaller piece of 
compilable code and send it to you.

But to add on -
I used FLTK 1.1.7 with the same Nano-X and Nxlib and found that there is no 
delay.
Now replacing the FLTK 1.1.7 with 1.3.0, am seeing the delay.
I have made no changes in my application code.
So is there some change in FLTK 1.3.0 which i probably am not handling in my 
application.

- Arun






> It seems to me like your event management is somehow messed up. This is eit=
> her in your code, or somewhere in the x11 server that you are using. It wou=
> ld help tremendously if you could sen us some minimal code which exhibits t=
> he bad behavior which we can compile and test.
>
> If the problem can be fixed=
>  by adding Fl::flush() calls after changes in th UI, then one of the reason=
> s above os to blame.
>
>
>
> Jayaram <[email protected]> schrieb:
>
> >> On 07=
> /18/12 04:39, Jayaram wrote:
> >> >>
> >DQo+IEnigJltIHJ1bm5pbmcgdGhlc2Ugb24gYW4=
> gYXJtIHRhcmdldC4gVGhlIGRlbGF5IGFtIHNl
> >> >>
> >ZWluZyBpcyBpbiBnZW5lcmFsIHdpdG=
> gNCj4gcmVuZGVyaW5nIHdpbmRvd3MgYW5kIHRleHQuDQo+
> >> >>
> >IEkgdXNlZCBGTFRLIDEuM=
> S43IHdpdGggdGhlIGxhdGVzdCBOYW5vLVggYW5kIE54bGliIGFuZCBm
> >> >> [..]
> >> >
> >> =
> > Hi Ian ,
> >> >         This message is not readable. Can you post this mes=
> sage
> >again
> >>
> >>     I can read Ian's message via the NNTP interface to th=
> e group,
> >>     so I'm posting a copy as clear text below.
> >>
> >>     Indeed=
> , his message looks entirely like encrypted text if I hit
> >>     'View Sour=
> ce'; it appears that message is in Microsoft's TNEF
> >format,
> >>     which m=
> any interfaces to the group probably can't decode
> >properly.
> >>
> >>     Anot=
> her message he wrote 10 minutes earlier was clear text, so it
> >>     appear=
> s to be something his MS mail reader is doing specific with
> >>     that one=
>  message.
> >>
> >>     Anyway, here's what he wrote in reply to your msg:
> >>
> >=
> >                             * * *
> >>
> >> > I=EF=BF=BD=EF=BF=BD=EF=BF=BDm running these on an arm t=
> arget. The delay am seeing is in
> >general with
> >> > rendering windows and t=
> ext.
> >> > I used FLTK 1.1.7 with the latest Nano-X and Nxlib and found the
> =
> >> > performance to be the same as when I was using FLTK1.1.7 +
> >Nano-X0.92=
>  +
> >> > Nxlib 0.45.
> >> > This would eliminate Nano-X and Nxlib as being the=
>  problem area
> >wouldn=EF=BF=BD=EF=BF=BD=EF=BF=BDt
> >> > it ?
> >>
> >> I'm not s=
> ure it does - though also see Micha's post (and my response)
> >about
> >> the =
> behaviour of the IM system, and fltk's interaction with it, in
> >the
> >> 1.3.=
> x series.
> >>
> >> WHat he proposes may be a credible workaround for you, if t=
> hat is the
> >problem.
> >> I'm assuming that in your embedded target the IM pr=
> obably is not
> >useful to you?
> >> But then, you may be entering complex scri=
> pted languages, so maybe
> >you do need
> >> the IM to work?
> >>
> >> > But with F=
> LTK 1.3.0 and latest Nano-X, Nxlib delay seems to be
> >> > considerable espe=
> cially in windows where a sizeable amount of utf-8
> >text
> >> > need to be re=
> ndered.
> >>
> >> If it depends on the amount of text to be rendered, it maybe =
> NOT the
> >IM problem then...
> >> This really sounds more like a rendering iss=
> ue perhaps? Do you have
> >any metrics for
> >> how "fast" your Nano-x system i=
> s rendering text?
> >> Can you run a kdrive-style X server on your target for=
>  comparison and
> >see how
> >> that compares to Nano-x for performance?
> >>
> >> =
> > I have disabled xft and don=EF=BF=BD=EF=BF=BD=EF=BF=BDt have any problem =
> displaying utf-8
> >characters
> >> > except the delay issue am seeing.
> >> > Wo=
> uld enabling Xft and using a ttf font make any difference ?
> >>
> >> I doubt t=
> hat XFT with a TTF font would render faster than a simple
> >Xlib
> >> bitmap f=
> ont, though I may well be wrong.
> >>
> >> I much prefer XFT, but because it lo=
> oks better, not because it is
> >faster!
> >>
> >> There is a fair bit of logic i=
> n fltk to try and cope with unicode
> >text in
> >> a "simple" Xlib context so =
> there shouldn't be any need to use XFT to
> >get
> >> unicode fonts rendered.
> >=
> >
> >
> >With respect to performance am seeing this behavior (not quite sure ho=
> w
> >i can explain this behavior).
> >So am using FLTK+Nano-X+Nxlib on an Arm t=
> arget with a touch screen
> >dislay.
> >On the press of a button on the touch s=
> creen i populate some random
> >text in a FL_Box. 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 k=
> eep 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 !!
> >
> >=
>
> >
> >-----------------------------------------------------------------------=
> -
> >
> >_______________________________________________
> >fltk mailing list
> >fl=
> [email protected]
> >http://lists.easysw.com/mailman/listinfo/fltk

_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to