nanogui: Thread: FLTK 2.0 Fonts

The application is blowing up due to the handling of the fonts in X11 vs eCos.  Within eCos, the fonts are compiled and are not referred to along a file system path.

XListFonts returns a sorted list of fonts found in the system that match a specific pattern.

What do I need to do to use the built in fonts provided by fltk?

Graham Henderson ####@####.#### wrote: Michael:

I have gotted eCos to run the non-fltk part of my application in client/server mode.  As you may recall, my application linked directly to the server before.

I have added the button test application to my code and it will execute to a point.  I am currently throwing a Data Abort exception in SVR_GrPeekEvent.  In addition, the following unsupported (nxlib 0.45) routines are being called:

XSetErrorHandler
XSetLocaleModifier
XOpenIM

More as it develops.

Graham
 

"McCune, Michael"  wrote: Graham,

Sounds like you are very close to testing it out, please keep us posted I would love to hear how things go.

Mike McCune
Navigation Solutions
248 282 5407


-----Original Message-----
From: Graham Henderson ####@####.####
Sent: Mon 7/23/2007 3:44 PM
To: McCune, Michael; ####@####.####
Subject: Re: [nanogui] FLTK 2.0 followup
 
Michael:

Thank you for your replies.  Yes....that is where I  am at  right now.  I have added the missing functions to the stub.c file to get eCos/nxlib/fltk2 and my application code to compile.

Within eCos, both the client and the server reside in the same space with the application.  I also needed to add some SVC_[fuinctionname] definitions to serv.h to make nano-x happy.

I just need to resolve two more undefined references and it will be time for a smoke test.

Graham...



       
---------------------------------
Yahoo! oneSearch: Finally,  mobile search that gives answers, not web links. 

       
---------------------------------
Got a little couch potato? 
Check out fun summer activities for kids.

: The application is blowing up due to the handling of the fonts in X11 vs
eCos.  Within eCos, the fonts are compiled and are not referred to along a
file system path.

In that case, XListFonts will require a rewrite likely.  And you may have to
hack FLTK, which uses numbers to identify fonts except for when
they're finally pulled out of some internal table and get converted
to a filename, to be matched with XListFonts.

Regards,

Greg



:
: XListFonts returns a sorted list of fonts found in the system that match a
specific pattern.
:
: What do I need to do to use the built in fonts provided by fltk?

Greg:

The good people over at the fltk forum provided some insight.  Within the font_xlfd  fileI simply commented out the call to XListFonts.

I had stack related problems due to a buffer of MAXREQUESTSZ ( 30000) being allocated on the stack.

GsHandleClient(int fd)
{
    nxReq *    req;
    long    len;
    char    buf[MAXREQUESTSZ];

.
.
.
Increasing the stack for the server task solved the problem.  Would it be better to allocate that memory from the heap or statically define it globally?

Graham....


Greg Haerr ####@####.#### wrote: : The application is blowing up due to the handling of the fonts in X11 vs
eCos.  Within eCos, the fonts are compiled and are not referred to along a
file system path.

In that case, XListFonts will require a rewrite likely.  And you may have to
hack FLTK, which uses numbers to identify fonts except for when
they're finally pulled out of some internal table and get converted
to a filename, to be matched with XListFonts.

Regards,

Greg



:
: XListFonts returns a sorted list of fonts found in the system that match a
specific pattern.
:
: What do I need to do to use the built in fonts provided by fltk?


---------------------------------------------------------------------
To unsubscribe, e-mail: ####@####.####
For additional commands, e-mail: ####@####.####




Graham W. Henderson
241 Sauk Drive
Batavia, IL 60510-8660

630 406 1724 (home)
630 862 6474 (cell)
801 406 6008 (fax )
       
---------------------------------
Need a vacation? Get great deals to amazing places on Yahoo! Travel. 

: The good people over at the fltk forum provided some insight.  Within the 
font_xlfd  fileI simply commented out the call to XListFonts.

Amazing that eliminating a call solves the problem and it still works!
Makes you wonder why its in there in the first place.


: Increasing the stack for the server task solved the problem.  Would it be 
better to allocate that memory from the heap or statically define it 
globally?

This was increased to 30000 to handle larger images.  Its allocated
from the heap since its normally cheap and fast to do so, any
nxproto routine with a data buffer may require it.  If you have
space, a static global define would work, but you've essentially
done that with the increased stack spec already...

Regards,

Greg