Re: [fltk.general] X11 coordinate clipping [was: Re: Fl_Tree - performance and scrollbehavior issue]

2011-12-24 Thread Albrecht Schlosser
On 22.12.2011 21:27, David FLEURY wrote: >> Question: why do you use "USHRT_MAX = 65536" instead of SHRT_MAX (32767), >> as it is in fl_rect.cxx, as you mentioned above? X coordinates can be >> negative, so they are signed shorts AFAICT. Am I missing something? > > > I only USHORT_MAX because this

Re: [fltk.general] X11 coordinate clipping [was: Re: Fl_Tree - performance and scrollbehavior issue]

2011-12-23 Thread Greg Ercolano
On 12/22/11 12:27, David FLEURY wrote: > You are right, I will see for a Tree Item solution, to avoid regression > somewhere else. > I do not know well enough fltk to have any opinion on this subject. > Just try to make my tests work for my own configuration. I was noodling with creating

Re: [fltk.general] X11 coordinate clipping [was: Re: Fl_Tree - performance and scrollbehavior issue]

2011-12-22 Thread David FLEURY
> On 22.12.2011 09:56, David FLEURY wrote: > > > On this issue, is this possible to replicate (somehting like) the > > clip_to_short method used in fl_rect.cxx into fl_font_x.cxx ? > > and use it each XUtf8Draw or draw string methods ? > > > > Something like: > > namespace { > >const int USHRT