[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
gEDA: Could not load question font char -- check font-directory keyword
- To: geda-dev@geda.seul.org
- Subject: gEDA: Could not load question font char -- check font-directory keyword
- From: sdb@cloud9.net (Stuart Brorson)
- Date: Wed, 4 Feb 2004 10:48:49 -0500 (EST)
- Delivered-to: archiver@seul.org
- Delivered-to: geda-dev-outgoing@seul.org
- Delivered-to: geda-dev@seul.org
- Delivery-date: Wed, 04 Feb 2004 10:49:20 -0500
- Reply-to: geda-dev@seul.org
- Sender: owner-geda-dev@seul.org
Hi guys,
I've been beavering away on gattrib -- my attribute editor -- for a
while. I am putting it together by stealing tons of code from gschem,
gnetlist, and gtkextra. Now I am trying to get the dialog boxes to
work properly, and I have encountered the following run-time error:
"Could not load question font char -- check font-directory keyword"
This apparently occurs inside "o_text_load_font" which lives in
libgeda-20040111/src/o_text_basic.c. The code snippet is here:
------------------------------------------------------------
if (access(temp_string, R_OK) != 0) {
s_log_message("Could not find character %c definition\n",
needed_char,
temp_string);
free(temp_string);
temp_string =
g_strdup_printf("%s%cquest.sym", w_current->font_directory,
PATH_SEPARATER_CHAR);
if (access(temp_string, R_OK) != 0) {
fprintf(stderr,
"Could not load question font char -- check
font-directory keyword\n");
exit(-1);
}
not_found = TRUE;
}
------------------------------------------------------------
THis is executed after looking for various chars in the font
directory, as far as I can tell.
My question: What is o_text_load_font looking for, and where? What
do I have to tell it to make it find the proper fonts? This works
fine in gschem, but I am not sure where gschem configures the fonts,
or if I can somehow just bypass this stage. . . .
Thanks,
Stuart
p.s. Thanks for the replies to my question about u_basic_strdup. It
doens't eat strings. I just had my head wedged. . . . .