On Aug 28, 2012, at 8:53 AM, Alan W. Irwin wrote:

> To Arjen and Jerry:
> 
> Jerry was not running pltcl correctly.  See
> examples/tcl/README.tcldemos for how to do that (plinit first).

Indeed, in the commands that I posted in a recent e-mail I did not run plinit, 
as the README.tcldemos says to do. However, the x?? files each contain plinit 
so it would seem to not be required to otherwise run it.

[This ^ is just repeating Arjen's new post.]

Also, this is what I take away from the readme: "To run individual examples, 
run the x?? script corresponding to the x??.tcl example, where ?? is 01 through 
19.?

In any case, here is what happens when I add that command:

MBPro:~ jerrybauck$ cd /usr/local/plplot_build_dir/examples/tcl
MBPro:tcl jerrybauck$ export PATH=/usr/local/plplot/lib:$PATH
MBPro:tcl jerrybauck$ /usr/local/plplot/bin/pltcl
pltcl> plinit

Plotting Options:
 < 1> xwin       X-Window (Xlib)
 < 2> tk         Tcl/TK Window
 < 3> ps         PostScript File (monochrome)
 < 4> psc        PostScript File (color)
 < 5> xfig       Fig file
 < 6> null       Null device
 < 7> tkwin      New tk driver
 < 8> mem        User-supplied memory device
 < 9> svg        Scalable Vector Graphics (SVG 1.1)
 <10> bmpqt      Qt Windows bitmap driver
 <11> jpgqt      Qt jpg driver
 <12> pngqt      Qt png driver
 <13> ppmqt      Qt ppm driver
 <14> tiffqt     Qt tiff driver
 <15> svgqt      Qt SVG driver
 <16> qtwidget   Qt Widget
 <17> epsqt      Qt EPS driver
 <18> pdfqt      Qt PDF driver
 <19> extqt      External Qt driver
 <20> memqt      Memory Qt driver

Enter device number or keyword: 4
Enter graphics output file name: /testpltcl.ps

<<<< At this point a ps file is made which contains only a tiny black square, 
perhaps 3 x 3 pixels at 100% zoom. >>>

pltcl> source x01
PLplot library version: 5.9.9

Plotting Options:
 < 1> xwin       X-Window (Xlib)
 < 2> tk         Tcl/TK Window
 < 3> ps         PostScript File (monochrome)
 < 4> psc        PostScript File (color)
 < 5> xfig       Fig file
 < 6> null       Null device
 < 7> tkwin      New tk driver
 < 8> mem        User-supplied memory device
 < 9> svg        Scalable Vector Graphics (SVG 1.1)
 <10> bmpqt      Qt Windows bitmap driver
 <11> jpgqt      Qt jpg driver
 <12> pngqt      Qt png driver
 <13> ppmqt      Qt ppm driver
 <14> tiffqt     Qt tiff driver
 <15> svgqt      Qt SVG driver
 <16> qtwidget   Qt Widget
 <17> epsqt      Qt EPS driver
 <18> pdfqt      Qt PDF driver
 <19> extqt      External Qt driver
 <20> memqt      Memory Qt driver

Enter device number or keyword: 4
Enter graphics output file name: /testx01.ps

<<< At this point a ps file is made which contains 344 NANs. >>>

pltcl> 

When I execute x01 directly and choose xwin, an X window appears which is all 
black and persists until I hit Return. If I choose qtwidget, a black 1/10 
second window flashes that looks like it _could_ be the Qt widget. At the same 
time, in my dock (which shows icons for running programs), an icon labelled 
"pltcl" appears briefly. Also, this text appears:

*** PLPLOT ERROR, IMMEDIATE EXIT ***
plP_setphy: device minima must not exceed maxima
Program aborted

Sorry if I'm repeating myself but I just want to make sure I'm being accurate.


>  Those
> directions are followed in the configured file
> plplot_test/test_tcl.sh(.in) which in turn is run by the configured
> file plplot_test/plplot-test.sh(.in).  The CMake logic in
> examples/CMakeLists.txt that uses plplot_test/plplot-test.sh, is
> somewhat complicated since there are many languages (and associated
> targets) which need to be set up in a loop to test those languages
> with -dev psc), but the result is the test_tcl_psc target runs
> plplot_test/plplot-test.sh for the tcl language and psc device which
> in turn runs test_tcl.sh.
> 
> In the past, both of you have reported good results for tcl using the
> test_diff_psc target (which in turn depends on the test_tcl_psc
> target). So if the test_tcl_psc target still works for you, then you
> have proved that Tcl and pltcl continues to be set up correctly on
> your systems.

I ran a fuller test than I normally do (test_noninteractive in this case), just 
to make sure that this is still true. At one point this appears in the output:

14: tcl
14:   Missing examples            : 
14:   Differing postscript output : 
14:   Missing stdout              : 
14:   Differing stdout            : 

which I think confirms that the Tcl stuff is still working.
> 
> Those directions in examples/tcl/README.tcldemos are also followed in
> the configured version of examples/tcl/standard_examples.in in the
> build tree, which in turn is run by the test_tcl_standard_examples
> target that is available if you use the -DBUILD_TEST=ON option.  To
> see what is actually run by that target look in
> examples/CMakeLists.txt where you will find the line
> 
> COMMAND ${CMAKE_CURRENT_BINARY_DIR}/tcl/standard_examples -dev xwin -np
> 
> where, of course, ${CMAKE_CURRENT_BINARY_DIR} refers to the examples
> subdirectory of the build tree and the -np option stands for "no pause"
> (so you don't have to keep hammering the return key to get through the
> examples).
> 
> @Jerry: I think that test_tcl_standard_examples target should just
> work for you if -dev xwin works and if you have Tcl set up properly on
> your system.

Not sure what this means. Is test_tcl_standard_examples a subset of 
test_noninteractive?
> 
> 
> @Arjen: that target depends on -dev xwin which is not available on
> your Windows system.  But I believe in the past you have gotten
> examples/tcl/standard_examples in the the build tree to work by hand
> for the interactive devices that are available to you on Windows.  If
> you confirm that again, and assuming the interactive device you use is wingcc 
> then
> I suggest you add another stanza to the examples/CMakeLists.txt file
> like this:
> 
>  if(ENABLE_tcl AND PLD_xwin)
>    .... current logic ....
>  elseif(ENABLE_tcl AND PLD_wingcc)
>    .... almost exact copy of current logic with xwin replaced
>    by wingcc ....
>  endif(ENABLE_tcl AND PLD_xwin)
> 
> Then you should also be able to run the test_tcl_standard_examples
> target without issues if Tcl and -dev wingcc are set up properly on
> your system.
> 
> @both of you: of course the test_tcl_psc target and the
> test_tcl_standard_examples target only test Tcl and do not test Tk. I
> think the only chance for you to test Tk for your non-X versions of Tk
> will involve the tkwin shared object.  However, some C source code
> updating will be required to get that shared object to work with
> modern PLplot as discussed previously in this thread.
> 
> 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); the Time
> Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> software package (plplot.sf.net); 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
> __________________________


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to