[Octave-bug-tracker] [bug #52150] all plot functions throw errors when built with --without-fontconfig

[Dan Sebald]

Follow-up Comment #12, bug #52150 (project octave):

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.  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").  So although gnuplot
should work still, in theory, program flow was stopped before reaching the
toolkit code.  There would need to be a change in the code that allows the
toolkit to continue, rather than error in the core.  In other words, the
error/warning should be in the toolkit, not the core code.

As noted in the posts, the main question is what to do.  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".

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?52150>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/