|
From: Daniel B. <dbo...@gm...> - 2018-02-07 18:35:16
|
On 7 February 2018 at 18:17, Ethan A Merritt <eam...@gm...> wrote: > > Now add "mousing" to the "set terminal" line. > > > > That results in the background being lost, so everything is white on > white, > > and thus invisible. > > Yes. That seems to be a bug. > > > It looks like the code that creates the mousing bounding box > > unconditionally sets a white rectangle with a black stroke, thus > > overridding or hiding the background the user wants. > > Other way around I think. If you set a background color then > normally the plot output begins with a filled rectangle of that color. > However if you select "standalone mousing" the program starts the > output with a copy of the mousing code and omits the filled background > rectangle. > > > Is this bugworthy, or is there a reason that it has to be this way? > > According to the code, it was intentional. But quick testing does > not show any obvious problem so I am not sure why that was. > I will investigate further. > Thanks for that! > I would really like to be able to render white (and other colours) on > > black, as I prefer "inverted" colours - but I also want to be able to use > > mousing in my reports. At present, it doesn't look like I can have both. > > Sure you can. No problem. > You can always include a filled background rectangle as a separate > command. This should work independent of anything else: > > set obj 1 rectangle from screen 0,0 to screen 1,1 behind > set obj 1 fillstyle solid fillcolor "black" > Ta again - I found others suggesting this method shortly after posting. It'll probably be fine for now, at least since you revealed the secrets of the key title textcolor(s). :D |