nanogui: Thread: Performance : FLTK+Nxlib+Nano-X

Hello,

Am using FLTK 1.3 , Nxlib (development head) , Nano-X (development
head) for an ARM touch screen target.

I upgraded it from FLTK 1.1.7+Nxlib 0.45 + Nano-X .91 to add UTF-8 support.

On a button press, am displaying text in an information box. I see a
long delay for the text to be rendered. But if i keep the touch screen
pressed after the button press, the rendering is extremely quickly.

I tried this with FLTK1.1.7 + the latest of nxlib+nano-x and this
delay was not seen.

Unable to understand why this could be happening. Any ideas ?

Thanks,
Arun

Arun,

I have the same setup FLTK-1.3, NXLIB (development head),
Nano-X (development head) with FreeType2 enabled.

If you are using Truetype fonts it may take a long time
to load the font for the first time, but after that it
is cached (if enabled). If TrueType, what version of
FreeType are you using. I am using FreeType 2.3.9

Pete

On 7/31/2012 12:37 PM, Arun Ram M wrote:
> Hello,
>
> Am using FLTK 1.3 , Nxlib (development head) , Nano-X (development
> head) for an ARM touch screen target.
>
> I upgraded it from FLTK 1.1.7+Nxlib 0.45 + Nano-X .91 to add UTF-8 support.
>
> On a button press, am displaying text in an information box. I see a
> long delay for the text to be rendered. But if i keep the touch screen
> pressed after the button press, the rendering is extremely quickly.
>
> I tried this with FLTK1.1.7 + the latest of nxlib+nano-x and this
> delay was not seen.
>
> Unable to understand why this could be happening. Any ideas ?
>
> Thanks,
> Arun
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>
>
>

Pete ,

No, i haven't added freetype support. Am currently using pcf fonts only.
Have been trying to debug it and it looks like it has something to do
with timers from the mouse event handling for the touchscreen. Haven't
yet figured out exactly ! Any ideas ?
Do you have this setup for an ARM target ?

Now that you mention True Type fonts, i have been trying to add
support for true type fonts. I cross compiled freetype 2 for the arm
target and modified nano-x appropriately. that worked fine.
Now while i try to enable xft in FLTK, i understand i needed to build
XFT. Trying to build that, i realized XFT needs FontConfig.
So seems like am getting into a chain of dependencies here and trying
to build all those libraries for the ARM target !
Is there a simpler way to do this ?

Thanks,
Arun

On Wed, Aug 1, 2012 at 9:48 PM, Pete Klemm ####@####.#### wrote:
> Arun,
>
> I have the same setup FLTK-1.3, NXLIB (development head),
> Nano-X (development head) with FreeType2 enabled.
>
> If you are using Truetype fonts it may take a long time
> to load the font for the first time, but after that it
> is cached (if enabled). If TrueType, what version of
> FreeType are you using. I am using FreeType 2.3.9
>
> Pete
>
>
> On 7/31/2012 12:37 PM, Arun Ram M wrote:
>>
>> Hello,
>>
>> Am using FLTK 1.3 , Nxlib (development head) , Nano-X (development
>> head) for an ARM touch screen target.
>>
>> I upgraded it from FLTK 1.1.7+Nxlib 0.45 + Nano-X .91 to add UTF-8
>> support.
>>
>> On a button press, am displaying text in an information box. I see a
>> long delay for the text to be rendered. But if i keep the touch screen
>> pressed after the button press, the rendering is extremely quickly.
>>
>> I tried this with FLTK1.1.7 + the latest of nxlib+nano-x and this
>> delay was not seen.
>>
>> Unable to understand why this could be happening. Any ideas ?
>>
>> Thanks,
>> Arun
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ####@####.####
>> For additional commands, e-mail: ####@####.####
>>
>>
>>
>

Pete ,

I managed to add support for true type fonts.
As i mentioned i cross compiled freetype 2 and made the changes in Nano-X.
But using a ttf font, am unable to display Cyrillic characters, even
though the ttf font file contains cyrillic characters.
Earlier i was using pcf fonts and i was able to display cyrillic and
all utf-8 characters. The only change i made is to add freetype 2.
I seem to be missing something.

Also, would you know where i can find good quality unicode ttf fonts ?
the free ones i have come across till now dont give clear text .

- Arun

On Thu, Aug 2, 2012 at 9:52 AM, Arun Ram M ####@####.#### wrote:
> Pete ,
>
> No, i haven't added freetype support. Am currently using pcf fonts only.
> Have been trying to debug it and it looks like it has something to do
> with timers from the mouse event handling for the touchscreen. Haven't
> yet figured out exactly ! Any ideas ?
> Do you have this setup for an ARM target ?
>
> Now that you mention True Type fonts, i have been trying to add
> support for true type fonts. I cross compiled freetype 2 for the arm
> target and modified nano-x appropriately. that worked fine.
> Now while i try to enable xft in FLTK, i understand i needed to build
> XFT. Trying to build that, i realized XFT needs FontConfig.
> So seems like am getting into a chain of dependencies here and trying
> to build all those libraries for the ARM target !
> Is there a simpler way to do this ?
>
> Thanks,
> Arun
>
> On Wed, Aug 1, 2012 at 9:48 PM, Pete Klemm ####@####.#### wrote:
>> Arun,
>>
>> I have the same setup FLTK-1.3, NXLIB (development head),
>> Nano-X (development head) with FreeType2 enabled.
>>
>> If you are using Truetype fonts it may take a long time
>> to load the font for the first time, but after that it
>> is cached (if enabled). If TrueType, what version of
>> FreeType are you using. I am using FreeType 2.3.9
>>
>> Pete
>>
>>
>> On 7/31/2012 12:37 PM, Arun Ram M wrote:
>>>
>>> Hello,
>>>
>>> Am using FLTK 1.3 , Nxlib (development head) , Nano-X (development
>>> head) for an ARM touch screen target.
>>>
>>> I upgraded it from FLTK 1.1.7+Nxlib 0.45 + Nano-X .91 to add UTF-8
>>> support.
>>>
>>> On a button press, am displaying text in an information box. I see a
>>> long delay for the text to be rendered. But if i keep the touch screen
>>> pressed after the button press, the rendering is extremely quickly.
>>>
>>> I tried this with FLTK1.1.7 + the latest of nxlib+nano-x and this
>>> delay was not seen.
>>>
>>> Unable to understand why this could be happening. Any ideas ?
>>>
>>> Thanks,
>>> Arun
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: ####@####.####
>>> For additional commands, e-mail: ####@####.####
>>>
>>>
>>>
>>

Arun,

My main use for FreeType and UTF-8 support was for Chinese. I use the
fireflysung.ttf font for that. It can found at

http://www.study-area.org/apt/firefly-font/fireflysung-1.3.0.tar.gz

Did you try the DejaVu fonts http://dejavu-fonts.org/wiki/Main_Page
I believe it has Cyrillic support.

I ended up modifying my application code to handle all text internally 
in wide
characters (wchar_t). This way I can support all unicode code points.

For example,

     GrText( window, _gc, x, y, wcString,  wcslen(wcString), GR_TFUC32 );

Hope some of this helps.

Pete

On 8/2/2012 8:20 PM, Arun Ram M wrote:
> Pete ,
>
> I managed to add support for true type fonts.
> As i mentioned i cross compiled freetype 2 and made the changes in Nano-X.
> But using a ttf font, am unable to display Cyrillic characters, even
> though the ttf font file contains cyrillic characters.
> Earlier i was using pcf fonts and i was able to display cyrillic and
> all utf-8 characters. The only change i made is to add freetype 2.
> I seem to be missing something.
>
> Also, would you know where i can find good quality unicode ttf fonts ?
> the free ones i have come across till now dont give clear text .
>
> - Arun
>
> On Thu, Aug 2, 2012 at 9:52 AM, Arun Ram M ####@####.#### wrote:
>> Pete ,
>>
>> No, i haven't added freetype support. Am currently using pcf fonts only.
>> Have been trying to debug it and it looks like it has something to do
>> with timers from the mouse event handling for the touchscreen. Haven't
>> yet figured out exactly ! Any ideas ?
>> Do you have this setup for an ARM target ?
>>
>> Now that you mention True Type fonts, i have been trying to add
>> support for true type fonts. I cross compiled freetype 2 for the arm
>> target and modified nano-x appropriately. that worked fine.
>> Now while i try to enable xft in FLTK, i understand i needed to build
>> XFT. Trying to build that, i realized XFT needs FontConfig.
>> So seems like am getting into a chain of dependencies here and trying
>> to build all those libraries for the ARM target !
>> Is there a simpler way to do this ?
>>
>> Thanks,
>> Arun
>>
>> On Wed, Aug 1, 2012 at 9:48 PM, Pete Klemm ####@####.#### wrote:
>>> Arun,
>>>
>>> I have the same setup FLTK-1.3, NXLIB (development head),
>>> Nano-X (development head) with FreeType2 enabled.
>>>
>>> If you are using Truetype fonts it may take a long time
>>> to load the font for the first time, but after that it
>>> is cached (if enabled). If TrueType, what version of
>>> FreeType are you using. I am using FreeType 2.3.9
>>>
>>> Pete
>>>
>>>
>>> On 7/31/2012 12:37 PM, Arun Ram M wrote:
>>>> Hello,
>>>>
>>>> Am using FLTK 1.3 , Nxlib (development head) , Nano-X (development
>>>> head) for an ARM touch screen target.
>>>>
>>>> I upgraded it from FLTK 1.1.7+Nxlib 0.45 + Nano-X .91 to add UTF-8
>>>> support.
>>>>
>>>> On a button press, am displaying text in an information box. I see a
>>>> long delay for the text to be rendered. But if i keep the touch screen
>>>> pressed after the button press, the rendering is extremely quickly.
>>>>
>>>> I tried this with FLTK1.1.7 + the latest of nxlib+nano-x and this
>>>> delay was not seen.
>>>>
>>>> Unable to understand why this could be happening. Any ideas ?
>>>>
>>>> Thanks,
>>>> Arun
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: ####@####.####
>>>> For additional commands, e-mail: ####@####.####
>>>>
>>>>
>>>>
>

Re posting because the earlier post was sidetracked with freetype
support related discussion.

Hello,

Am using FLTK 1.3 , Nxlib (development head) , Nano-X (development
head) for an ARM touch screen target.

I upgraded it from FLTK 1.1.7+Nxlib 0.45 + Nano-X .91 to add UTF-8 support.

On a button press, am displaying text in an information box. I see a
long delay for the text to be rendered. But if i keep the touch screen
pressed after the button press, the rendering is quick.

I tried this with FLTK1.1.7 + the latest of nxlib+nano-x and this
delay was not seen.

Am using a touch screen device. So i reduced touch screen reads by
half. This improved performance but reduced the touchscreen response
itself.
I was using the same touch screen drivers with the earlier versions
without any sort of performance delay.

It seems like some sort of threading issue with the newer versions of
the code, but am unable to figure out. Any ideas ?

Thanks,
Arun

Hi Arun,

I had a similar problem. Rendering did work faster when I put a sleep() 
statement into my mouse driver:

static int AM_Poll(void)
{
_sleep(0.05);
return 1;
}

My assumption is that the mouse is polled very (too) often and the sleep() 
frees some time slices to the processor allowing it to spend this time on 
rendering. Greg suggested that I rather put the sleep() into the GsSelect() 
routine which is probably better.

Georg


----- Original Message ----- 
From: "Arun Ram M" ####@####.####
To: ####@####.####
Sent: Monday, August 20, 2012 5:05 AM
Subject: [nanogui] Performance : FLTK + Nxlib + Nano-X


> Re posting because the earlier post was sidetracked with freetype
> support related discussion.
>
> Hello,
>
> Am using FLTK 1.3 , Nxlib (development head) , Nano-X (development
> head) for an ARM touch screen target.
>
> I upgraded it from FLTK 1.1.7+Nxlib 0.45 + Nano-X .91 to add UTF-8 
> support.
>
> On a button press, am displaying text in an information box. I see a
> long delay for the text to be rendered. But if i keep the touch screen
> pressed after the button press, the rendering is quick.
>
> I tried this with FLTK1.1.7 + the latest of nxlib+nano-x and this
> delay was not seen.
>
> Am using a touch screen device. So i reduced touch screen reads by
> half. This improved performance but reduced the touchscreen response
> itself.
> I was using the same touch screen drivers with the earlier versions
> without any sort of performance delay.
>
> It seems like some sort of threading issue with the newer versions of
> the code, but am unable to figure out. Any ideas ?
>
> Thanks,
> Arun
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>