|
From: Petr M. <mi...@ph...> - 2006-05-16 20:10:00
|
>> I have implemented it as you've proposed, see SF patch >> 1488448 User-available GPVAL_ variables > > It looks basically reasonable to me. > There are some rough edges though: > > %%%%%%% How to handle time data on axes? %%%%%%%%%%%%%%%%%% > > set xdata time > set xrange [ "01/06/93\t0000" : "01/11/93\t0000" ] noreverse nowriteback > > gnuplot> print GPVAL_X_MIN > -207792000.0 > gnuplot> print GPVAL_X_MAX > -194572800.0 Sorry, I have no idea about time values, I have never dealt with them. > %%%%%%% Something wrong in save/load code %%%%%%%%%%%%%%%%% > > Terminal type set to 'wxt' > gnuplot> save 'yyy' > gnuplot> load 'yyy' > Segmentation fault > > I think these special variables should not be user-writable. > That is, I think we want to return an error message like > > But this means it makes no sense to save these variables in > the `save` command, because it will not be possible to read > them back in on `load`. Yes, it is reasonable not to 'save' them, I will add this. > gnuplot> GPVAL_TERM_OPTIONS = "something or other" > Cannot set internal variable GPVAL_* Do you know where is code with the variable assignment? --- PM |