Warning: ft_text_renderer: unable to load appropriate fontĮrror: ft_text_renderer: invalid bounding box, cannot renderĮrror: _goaxes_: unable to create graphics handle configure -without-fontconfig -without-opengl -without-osmesa -without-qt -disable-docs Do you believe that the gnuplot toolkit should be able to function normally without fontconfig? Because it doesn't. Instead of changing configure, I would change the code, so that if HAVE_FONTCONFIG is undefined, the OpenGL toolkits are not built. We had these tests all bundled together before in configure and we have successfully unbundled them. I think this is a corner case, so I would find option #2 acceptable. I looked again at adding "octave::config::font_dir ()" in toplev.h as is done for info_dir but got lost again.
Oct2py gnu octave how to#
> No problem, I'll look at the missing pieces here for how to distribute and install the font files and what the default should be when OCTAVE_FONT_DIR is not set.
Oct2py gnu octave Patch#
What is the proper way to export a patch with binary data and should we include those binary files in version control? I tried to add the "-a" switch and the files where somewhat added but probably messed up because they are then treated as text (as the doc says). only the following:ĭiff -r e250aeab3c85 -r 8aa94b7dda80 etc/fonts/FreeSans.ttfīinary file etc/fonts/FreeSans.ttf has changedĭiff -r e250aeab3c85 -r 8aa94b7dda80 etc/fonts/FreeSansBold.ttfīinary file etc/fonts/FreeSansBold.ttf has changedĭiff -r e250aeab3c85 -r 8aa94b7dda80 etc/fonts/FreeSansBoldOblique.ttfīinary file etc/fonts/FreeSansBoldOblique.ttf has changedĭiff -r e250aeab3c85 -r 8aa94b7dda80 etc/fonts/FreeSansOblique.ttfīinary file etc/fonts/FreeSansOblique.ttf has changedĭiff -r e250aeab3c85 -r 8aa94b7dda80 libinterp/corefcn/ Sorry, the simple "hg add fontfiles" followed by "hg export -o patchname" did not include the files in the patch. If there is no font-config, Qt font's don't work? (Oh, I suppose the plotting never actually uses the Qt resource, but OpenGL.and it's only the GUI where we know Qt resources are available.) Behavior option #1, i.e., simply issue a warning and leave text objects blank on the plot, seems OK if the warning included some phrase like, "Try a different toolkit".
In other words, the error/warning should be in the toolkit, not the core code.Īs noted in the posts, the main question is what to do.
Oct2py gnu octave code#
There would need to be a change in the code that allows the toolkit to continue, rather than error in the core. So although gnuplot should work still, in theory, program flow was stopped before reaching the toolkit code. For that reason, it was the core code making the decision that a text object should not be valid (the bounding box description failing because it doesn't return "4"). I started looking at this a few days ago, but the actual source of the error seemed so hard to trace-mainly because program flow is back into the C source and there was some type of macro GO_BODY. Other than that this patch looks perfect to me.
I also see a stray space on line 208 of and the indentation on line 217 isn't right. I just want to make sure we get the right files in there. The fonts in the release look like this on my system What is your source for the FreeSans files? I used the 20120503 release tarball from gnu.org. Your latest patch gives me valid font files, but they are not exactly the same as what I have.
0 kommentar(er)
