On 2009-11-18 13:20-0600 Hezekiah M. Carty wrote: > On Tue, Nov 17, 2009 at 1:29 PM, Alan W. Irwin >> There are several issues you have touched on. >> >> As far as the default window title is concerned, I think it should identify >> the device (some of them do not identify themselves as I discovered when >> running "make test_interactive"). I also like what the wxwidgets device >> driver does which is to add some information about which fundamental version >> of the device driver is being used. I don't think there is such a >> fundamental choice for any other interactive device, but I thought I should >> mention it for the wxwidgets case. >> > > I am ok with this idea as long as it could be overridden by the > -plwindow flag and from the PLplot API. If the user selects the plot > device they want to use then they would likely have this information > fresh in their mind. If the plot device is somehow hard-coded there > is likely a reason for this and showing the output device in the > window frame may provide more confusion that it alleviates. > > Once proper -plwindow command line support is added to the supported > interactive output devices it could be used to show this information > when desired.
Agreed. I was too focussed above on my recent confusing experience with identification from the test framework. Try "make -j4 test_interactive" for yourself, and you will see why the identification issue is important in that context. However, for that context, I can easily change the tests (with -plwindow once it is implemented) to identify each GUI that pops up so I now agree there is no need to hard code such an identification (except in the wxwidgets case where there is currently no easy way other than the title to figure out which kind of wxwidgets device you are using). > >> I think adding the prompt "Press enter or right click to continue" to the >> title is probably overkill for xcairo. I lean instead toward outputting >> that prompt _once_ (for all interactive device drivers) to stderr. You may >> also want to add some information about terminating the device as well >> to the stderr prompt for all interactive devices. >> > > I do feel that this prompt is worth keeping around, at least as a > default. It will help with user questions like the recent thread on > plplot-general regarding plend not automatically closing an > interactive plot window. It also makes it clear to whoever is viewing > the plot window that the system is waiting for their input. I agree a prompt should be available for all interactive devices, but to me stderr (or stdout) output is fine (and can allow for a longer prompt). Is there some reason why you prefer the prompt in the windows title rather than stderr or stdout? Note, I am talking here about the PLplot interactive devices run from the command line, not standalone GUI's where access to stderr or stdout might be more problematic. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); PLplot scientific plotting software package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
