|
From: Daniel J S. <dan...@ie...> - 2012-12-21 03:15:31
|
Related to the dashed lines issue, someone noticed that {solid|dashed}
is not listed in the documentation for the Qt terminal even though these
terms are accepted and appear to do something relevant. The user
appears to not be able to get the proper dashed setting with a
combination of "termoption" and "term", even though inside gnuplot the
test page seems to function in a sensible way. I'd say hold off on that
other than perhaps adding {solid|dashed} to the Qt terminal
documentation. Fixing the x11 term is higher priority.
Dan
|
|
From: sfeam (E. Merritt) <eam...@gm...> - 2012-12-21 04:24:44
|
On Thursday, 20 December 2012, Daniel J Sebald wrote:
> Related to the dashed lines issue, someone noticed that {solid|dashed}
> is not listed in the documentation for the Qt terminal even though these
> terms are accepted and appear to do something relevant.
True. The {dashed|solid} options seem to be missing from the terminal's
help output. Perhaps the idea was to hold off advertising it until
dashlength could be implemented?
> The user
> appears to not be able to get the proper dashed setting with a
> combination of "termoption" and "term", even though inside gnuplot the
> test page seems to function in a sensible way.
That's not much of a description to work from.
Have any more information?
Is it just that the terminal doesn't offer the "dashlength" option?
> I'd say hold off on that
> other than perhaps adding {solid|dashed} to the Qt terminal
> documentation. Fixing the x11 term is higher priority.
See other message. I don't think there's anything wrong with the x11
terminal. You could make a case that the way x11 itself works is a
problem, but X has been that way for 25 years now.
echo " gnuplot*dashed: on
gnuplot*borderDashes: 0
gnuplot*axisDashes: 16
gnuplot*line1Dashes: 0
gnuplot*line2Dashes: 42
gnuplot*line3Dashes: 13
gnuplot*line4Dashes: 44
gnuplot*line5Dashes: 15
gnuplot*line6Dashes: 4441
gnuplot*line7Dashes: 42
gnuplot*line8Dashes: 13" > xrdb -merge
gnuplot
set term x11 dash
test
Ethan
> Dan
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
>
|
|
From: sfeam (E. Merritt) <eam...@gm...> - 2012-12-21 04:36:42
|
On Thursday, 20 December 2012, sfeam (Ethan Merritt) wrote:
> On Thursday, 20 December 2012, Daniel J Sebald wrote:
> > Related to the dashed lines issue, someone noticed that {solid|dashed}
> > is not listed in the documentation for the Qt terminal even though these
> > terms are accepted and appear to do something relevant.
>
> True. The {dashed|solid} options seem to be missing from the terminal's
> help output. Perhaps the idea was to hold off advertising it until
> dashlength could be implemented?
>
> > The user
> > appears to not be able to get the proper dashed setting with a
> > combination of "termoption" and "term", even though inside gnuplot the
> > test page seems to function in a sensible way.
>
> That's not much of a description to work from.
> Have any more information?
> Is it just that the terminal doesn't offer the "dashlength" option?
>
> > I'd say hold off on that
> > other than perhaps adding {solid|dashed} to the Qt terminal
> > documentation. Fixing the x11 term is higher priority.
>
> See other message. I don't think there's anything wrong with the x11
> terminal. You could make a case that the way x11 itself works is a
> problem, but X has been that way for 25 years now.
>
> echo " gnuplot*dashed: on
> gnuplot*borderDashes: 0
> gnuplot*axisDashes: 16
> gnuplot*line1Dashes: 0
> gnuplot*line2Dashes: 42
> gnuplot*line3Dashes: 13
> gnuplot*line4Dashes: 44
> gnuplot*line5Dashes: 15
> gnuplot*line6Dashes: 4441
> gnuplot*line7Dashes: 42
> gnuplot*line8Dashes: 13" > xrdb -merge
Darn those fingers! That should be a pipe of course.
echo "..." | xrdb -merge
|
|
From: Daniel J S. <dan...@ie...> - 2012-12-21 04:44:20
|
On 12/20/2012 10:24 PM, sfeam (Ethan Merritt) wrote:
> On Thursday, 20 December 2012, Daniel J Sebald wrote:
>> Related to the dashed lines issue, someone noticed that {solid|dashed}
>> is not listed in the documentation for the Qt terminal even though these
>> terms are accepted and appear to do something relevant.
>
> True. The {dashed|solid} options seem to be missing from the terminal's
> help output. Perhaps the idea was to hold off advertising it until
> dashlength could be implemented?
Is dashlength working now? I see it in the ChangeLog.
>> The user
>> appears to not be able to get the proper dashed setting with a
>> combination of "termoption" and "term", even though inside gnuplot the
>> test page seems to function in a sensible way.
>
> That's not much of a description to work from.
> Have any more information?
> Is it just that the terminal doesn't offer the "dashlength" option?
Perhaps, something like that. I agree it isn't much to go on, though.
I'll get X11 color dashes working in Octave first and see if I can
reproduce the problem.
>> I'd say hold off on that
>> other than perhaps adding {solid|dashed} to the Qt terminal
>> documentation. Fixing the x11 term is higher priority.
>
> See other message. I don't think there's anything wrong with the x11
> terminal. You could make a case that the way x11 itself works is a
> problem, but X has been that way for 25 years now.
>
> echo " gnuplot*dashed: on
> gnuplot*borderDashes: 0
> gnuplot*axisDashes: 16
> gnuplot*line1Dashes: 0
> gnuplot*line2Dashes: 42
> gnuplot*line3Dashes: 13
> gnuplot*line4Dashes: 44
> gnuplot*line5Dashes: 15
> gnuplot*line6Dashes: 4441
> gnuplot*line7Dashes: 42
> gnuplot*line8Dashes: 13"> xrdb -merge
>
> gnuplot
> set term x11 dash
> test
Working on it. I need to figure out where .Xresources or .Xdefaults
should reside.
Thanks,
Dan
|