You can subscribe to this list here.
| 2001 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(83) |
Nov
(57) |
Dec
(111) |
| 2004 |
Jan
(38) |
Feb
(121) |
Mar
(107) |
Apr
(241) |
May
(102) |
Jun
(190) |
Jul
(239) |
Aug
(158) |
Sep
(184) |
Oct
(193) |
Nov
(47) |
Dec
(68) |
| 2005 |
Jan
(190) |
Feb
(105) |
Mar
(99) |
Apr
(65) |
May
(92) |
Jun
(250) |
Jul
(197) |
Aug
(128) |
Sep
(101) |
Oct
(183) |
Nov
(186) |
Dec
(42) |
| 2006 |
Jan
(102) |
Feb
(122) |
Mar
(154) |
Apr
(196) |
May
(181) |
Jun
(281) |
Jul
(310) |
Aug
(198) |
Sep
(145) |
Oct
(188) |
Nov
(134) |
Dec
(90) |
| 2007 |
Jan
(134) |
Feb
(181) |
Mar
(157) |
Apr
(57) |
May
(81) |
Jun
(204) |
Jul
(60) |
Aug
(37) |
Sep
(17) |
Oct
(90) |
Nov
(122) |
Dec
(72) |
| 2008 |
Jan
(130) |
Feb
(108) |
Mar
(160) |
Apr
(38) |
May
(83) |
Jun
(42) |
Jul
(75) |
Aug
(16) |
Sep
(71) |
Oct
(57) |
Nov
(59) |
Dec
(152) |
| 2009 |
Jan
(73) |
Feb
(213) |
Mar
(67) |
Apr
(40) |
May
(46) |
Jun
(82) |
Jul
(73) |
Aug
(57) |
Sep
(108) |
Oct
(36) |
Nov
(153) |
Dec
(77) |
| 2010 |
Jan
(42) |
Feb
(171) |
Mar
(150) |
Apr
(6) |
May
(22) |
Jun
(34) |
Jul
(31) |
Aug
(38) |
Sep
(32) |
Oct
(59) |
Nov
(13) |
Dec
(62) |
| 2011 |
Jan
(114) |
Feb
(139) |
Mar
(126) |
Apr
(51) |
May
(53) |
Jun
(29) |
Jul
(41) |
Aug
(29) |
Sep
(35) |
Oct
(87) |
Nov
(42) |
Dec
(20) |
| 2012 |
Jan
(111) |
Feb
(66) |
Mar
(35) |
Apr
(59) |
May
(71) |
Jun
(32) |
Jul
(11) |
Aug
(48) |
Sep
(60) |
Oct
(87) |
Nov
(16) |
Dec
(38) |
| 2013 |
Jan
(5) |
Feb
(19) |
Mar
(41) |
Apr
(47) |
May
(14) |
Jun
(32) |
Jul
(18) |
Aug
(68) |
Sep
(9) |
Oct
(42) |
Nov
(12) |
Dec
(10) |
| 2014 |
Jan
(14) |
Feb
(139) |
Mar
(137) |
Apr
(66) |
May
(72) |
Jun
(142) |
Jul
(70) |
Aug
(31) |
Sep
(39) |
Oct
(98) |
Nov
(133) |
Dec
(44) |
| 2015 |
Jan
(70) |
Feb
(27) |
Mar
(36) |
Apr
(11) |
May
(15) |
Jun
(70) |
Jul
(30) |
Aug
(63) |
Sep
(18) |
Oct
(15) |
Nov
(42) |
Dec
(29) |
| 2016 |
Jan
(37) |
Feb
(48) |
Mar
(59) |
Apr
(28) |
May
(30) |
Jun
(43) |
Jul
(47) |
Aug
(14) |
Sep
(21) |
Oct
(26) |
Nov
(10) |
Dec
(2) |
| 2017 |
Jan
(26) |
Feb
(27) |
Mar
(44) |
Apr
(11) |
May
(32) |
Jun
(28) |
Jul
(75) |
Aug
(45) |
Sep
(35) |
Oct
(285) |
Nov
(99) |
Dec
(16) |
| 2018 |
Jan
(8) |
Feb
(8) |
Mar
(42) |
Apr
(35) |
May
(23) |
Jun
(12) |
Jul
(16) |
Aug
(11) |
Sep
(8) |
Oct
(16) |
Nov
(5) |
Dec
(8) |
| 2019 |
Jan
(9) |
Feb
(28) |
Mar
(4) |
Apr
(10) |
May
(7) |
Jun
(4) |
Jul
(4) |
Aug
|
Sep
(4) |
Oct
|
Nov
(23) |
Dec
(3) |
| 2020 |
Jan
(19) |
Feb
(3) |
Mar
(22) |
Apr
(17) |
May
(10) |
Jun
(69) |
Jul
(18) |
Aug
(23) |
Sep
(25) |
Oct
(11) |
Nov
(20) |
Dec
(9) |
| 2021 |
Jan
(1) |
Feb
(7) |
Mar
(9) |
Apr
|
May
(1) |
Jun
(8) |
Jul
(6) |
Aug
(8) |
Sep
(7) |
Oct
|
Nov
(2) |
Dec
(23) |
| 2022 |
Jan
(23) |
Feb
(9) |
Mar
(9) |
Apr
|
May
(8) |
Jun
(1) |
Jul
(6) |
Aug
(8) |
Sep
(30) |
Oct
(5) |
Nov
(4) |
Dec
(6) |
| 2023 |
Jan
(2) |
Feb
(5) |
Mar
(7) |
Apr
(3) |
May
(8) |
Jun
(45) |
Jul
(8) |
Aug
|
Sep
(2) |
Oct
(14) |
Nov
(7) |
Dec
(2) |
| 2024 |
Jan
(4) |
Feb
(4) |
Mar
|
Apr
(7) |
May
(2) |
Jun
(1) |
Jul
|
Aug
(5) |
Sep
|
Oct
|
Nov
(4) |
Dec
(14) |
| 2025 |
Jan
(22) |
Feb
(6) |
Mar
(5) |
Apr
(14) |
May
(6) |
Jun
(11) |
Jul
(19) |
Aug
|
Sep
(17) |
Oct
(1) |
Nov
(2) |
Dec
(18) |
| 2026 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
(2) |
Jun
(1) |
Jul
(6) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Daniel J S. <dan...@ie...> - 2011-08-30 17:25:00
|
On 08/30/2011 10:58 AM, Mojca Miklavec wrote: > Hello, > > I would like to fill one square area of the plot with 100 random > points and another one with n random points (n is a parameter). > > If I use > set samples 100 > set parametric > plot rand(0),rand(0) w lines, rand(0)+3,rand(0)+3 > then I cannot vary number of points - I need an equal number of each points. > > Is there a quick remedy for that (apart from writing a C program to > create a list of points for me)? Mojca, I think it should be straightforward to generate the random data in a couple files using the "table" feature, then pull that data into gnuplot. As examples, look at the "random.dem" demo where the number of samples is set quite often. Just do a couple quick so-called plots to create the data files changing the number of samples in between. Dan |
|
From: Mojca M. <moj...@gm...> - 2011-08-30 15:58:22
|
Hello,
I would like to fill one square area of the plot with 100 random
points and another one with n random points (n is a parameter).
If I use
set samples 100
set parametric
plot rand(0),rand(0) w lines, rand(0)+3,rand(0)+3
then I cannot vary number of points - I need an equal number of each points.
Is there a quick remedy for that (apart from writing a C program to
create a list of points for me)?
Thank you,
Mojca
|
|
From: Tatsuro M. <tma...@ya...> - 2011-08-25 09:31:27
|
Hello Thank you for your reply --- On Thu, 2011/8/25, sfeam (Ethan Merritt) wrote: > You might try > 1) in config.mgw #define HAVE_STRUCT_EXCEPTION_IN_MATH_H > 2) sysconfig.h:334 # define GP_EXCEPTION_NAME _exception > (syscfg.h is correct) These make errors in compiling internal.c disappeared. The problem is compile of winmain.c. (/usr/x86_64-w64-mingw32/sys-root/mingw/include/shlguid.h:16:2: error: #error _WIN32_IE setting conflicts) Regards Tatsuro Tatsuro |
|
From: sfeam (E. Merritt) <eam...@gm...> - 2011-08-25 05:16:26
|
On Wednesday, 24 August 2011, Tatsuro MATSUOKA wrote: > Hello > > Thank you for the reply. > > --- On Thu, 2011/8/25, Ethan A Merritt wrote: > > > The only way I can see for that error message to make sense is if > > HAVE_STRUCT_EXCEPTION_IN_MATH_H > > is not defined. Is the setting in config/config.mgw correct? > > The default setting in config.mgw, HAVE_STRUCT_EXCEPTION_IN_MATH_H is not defined. > For math.h for 32 bit gcc complier seems not to require HAVE_STRUCT_EXCEPTION_IN_MATH_H is defined. > > I have manually define HAVE_STRUCT_EXCEPTION_IN_MATH_H in config.mgw and tried compile again. > > ********************* > x86_64-w64-mingw32-gcc -shared-libgcc -c -I/cygdrive/c/Programs/gplibs64/include -O3 -I. -I../../src -D_Windows -DHAVE_CONFIG_H -DPIPES -DWGP_CONSOLE -DUSE_MOUSE=1 -DWIN_IPC -DWITH_HTML_HELP -I/cygdrive/c/PROGRA~2/HELPWO~1/include -DHAVE_LIBGD -DHAVE_LIBPNG -DHAVE_GD_GIF -DGIF_ANIMATION -DHAVE_GD_PNG -DHAVE_GD_JPEG -DHAVE_GD_TTF -DHAVE_CAIROPDF -DHAVE_ICONV ../../src/internal.c > ../../src/internal.c:63:13: warning: 'struct exception' declared inside parameter list You might try 1) in config.mgw #define HAVE_STRUCT_EXCEPTION_IN_MATH_H 2) sysconfig.h:334 # define GP_EXCEPTION_NAME _exception (note the underscore character) Ethan > ../../src/internal.c:63:13: warning: its scope is only this definition or declaration, which is probably not what you want > ../../src/internal.c:63:1: error: conflicting types for '_matherr' > /usr/x86_64-w64-mingw32/sys-root/mingw/include/math.h:179:23: note: previous declaration of '_matherr' was here > make: *** [internal.o] Error 1 > > ********************************************************** > The "error: conflicting types for '_matherr'" appeared. > > internal.c:63 > 62: int > 63: GP_MATHERR( STRUCT_EXCEPTION_P_X ) > > /usr/x86_64-w64-mingw32/sys-root/mingw/include/math.h:179 > > 177: #ifndef _CRT_MATHERR_DEFINED > 178: #define _CRT_MATHERR_DEFINED > 179: _CRTIMP int __cdecl _matherr (struct _exception *); > 180: #endif > > Hmmm! What is wrong? > > Regards > > Tatsuro > > ------------------------------------------------------------------------------ > EMC VNX: the world's simplest storage, starting under $10K > The only unified storage solution that offers unified management > Up to 160% more powerful than alternatives and 25% more efficient. > Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev > _______________________________________________ > gnuplot-beta mailing list > gnu...@li... > https://lists.sourceforge.net/lists/listinfo/gnuplot-beta > |
|
From: Tatsuro M. <tma...@ya...> - 2011-08-25 04:49:26
|
Hello
I have found in syscfg.h
338: #ifndef GP_MATHERR
339: # define GP_MATHERR matherr
340: #endif
So that I have commented out GP_MATHERR function in internal.c and continue to try to build further
******************************
x86_64-w64-mingw32-gcc -shared-libgcc -c -I/cygdrive/c/Programs/gplibs64/include -O3 -I. -I../../src -D_Windows -DHAVE_CONFIG_H -DPIPES -DWGP_CONSOLE -DUSE_MOUSE=1 -DWIN_IPC -DWITH_HTML_HELP -I/cygdrive/c/PROGRA~2/HELPWO~1/include -DHAVE_LIBGD -DHAVE_LIBPNG -DHAVE_GD_GIF -DGIF_ANIMATION -DHAVE_GD_PNG -DHAVE_GD_JPEG -DHAVE_GD_TTF -DHAVE_ICONV -DHELPFILE=\"wgnuplot.chm\" ../../src/win/winmain.c
In file included from ../../src/win/winmain.c:60:0:
/usr/x86_64-w64-mingw32/sys-root/mingw/include/commctrl.h:17:2: error: #error _WIN32_IE setting conflicts
In file included from ../../src/win/winmain.c:61:0:
/usr/x86_64-w64-mingw32/sys-root/mingw/include/shlobj.h:17:2: error: #error _WIN32_IE setting conflicts
In file included from /usr/x86_64-w64-mingw32/sys-root/mingw/include/shlobj.h:91:0,
from ../../src/win/winmain.c:61:
/usr/x86_64-w64-mingw32/sys-root/mingw/include/shlguid.h:16:2: error: #error _WIN32_IE setting conflicts
make: *** [winmain.o] Error 1
********************************************
I will try to investigate what
#error _WIN32_IE setting conflicts
is.
Therefore I am not able to build 64 bit version gnuplot for windows at the moment.
Regards
Tatsuro
--- On Thu, 2011/8/25, Tatsuro MATSUOKA wrote:
> Hello
>
> Thank you for the reply.
>
> --- On Thu, 2011/8/25, Ethan A Merritt wrote:
>
> > The only way I can see for that error message to make sense is if
> > HAVE_STRUCT_EXCEPTION_IN_MATH_H
> > is not defined. Is the setting in config/config.mgw correct?
>
> The default setting in config.mgw, HAVE_STRUCT_EXCEPTION_IN_MATH_H is not defined.
> For math.h for 32 bit gcc complier seems not to require HAVE_STRUCT_EXCEPTION_IN_MATH_H is defined.
>
> I have manually define HAVE_STRUCT_EXCEPTION_IN_MATH_H in config.mgw and tried compile again.
>
> *********************
> x86_64-w64-mingw32-gcc -shared-libgcc -c -I/cygdrive/c/Programs/gplibs64/include -O3 -I. -I../../src -D_Windows -DHAVE_CONFIG_H -DPIPES -DWGP_CONSOLE -DUSE_MOUSE=1 -DWIN_IPC -DWITH_HTML_HELP -I/cygdrive/c/PROGRA~2/HELPWO~1/include -DHAVE_LIBGD -DHAVE_LIBPNG -DHAVE_GD_GIF -DGIF_ANIMATION -DHAVE_GD_PNG -DHAVE_GD_JPEG -DHAVE_GD_TTF -DHAVE_CAIROPDF -DHAVE_ICONV ../../src/internal.c
> ../../src/internal.c:63:13: warning: 'struct exception' declared inside parameter list
> ../../src/internal.c:63:13: warning: its scope is only this definition or declaration, which is probably not what you want
> ../../src/internal.c:63:1: error: conflicting types for '_matherr'
> /usr/x86_64-w64-mingw32/sys-root/mingw/include/math.h:179:23: note: previous declaration of '_matherr' was here
> make: *** [internal.o] Error 1
>
> **********************************************************
> The "error: conflicting types for '_matherr'" appeared.
>
> internal.c:63
> 62: int
> 63: GP_MATHERR( STRUCT_EXCEPTION_P_X )
>
> /usr/x86_64-w64-mingw32/sys-root/mingw/include/math.h:179
>
> 177: #ifndef _CRT_MATHERR_DEFINED
> 178: #define _CRT_MATHERR_DEFINED
> 179: _CRTIMP int __cdecl _matherr (struct _exception *);
> 180: #endif
>
> Hmmm! What is wrong?
>
> Regards
>
> Tatsuro
>
> ------------------------------------------------------------------------------
> EMC VNX: the world's simplest storage, starting under $10K
> The only unified storage solution that offers unified management
> Up to 160% more powerful than alternatives and 25% more efficient.
> Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
>
|
|
From: Tatsuro M. <tma...@ya...> - 2011-08-24 22:20:38
|
Hello Thank you for the reply. --- On Thu, 2011/8/25, Ethan A Merritt wrote: > The only way I can see for that error message to make sense is if > HAVE_STRUCT_EXCEPTION_IN_MATH_H > is not defined. Is the setting in config/config.mgw correct? The default setting in config.mgw, HAVE_STRUCT_EXCEPTION_IN_MATH_H is not defined. For math.h for 32 bit gcc complier seems not to require HAVE_STRUCT_EXCEPTION_IN_MATH_H is defined. I have manually define HAVE_STRUCT_EXCEPTION_IN_MATH_H in config.mgw and tried compile again. ********************* x86_64-w64-mingw32-gcc -shared-libgcc -c -I/cygdrive/c/Programs/gplibs64/include -O3 -I. -I../../src -D_Windows -DHAVE_CONFIG_H -DPIPES -DWGP_CONSOLE -DUSE_MOUSE=1 -DWIN_IPC -DWITH_HTML_HELP -I/cygdrive/c/PROGRA~2/HELPWO~1/include -DHAVE_LIBGD -DHAVE_LIBPNG -DHAVE_GD_GIF -DGIF_ANIMATION -DHAVE_GD_PNG -DHAVE_GD_JPEG -DHAVE_GD_TTF -DHAVE_CAIROPDF -DHAVE_ICONV ../../src/internal.c ../../src/internal.c:63:13: warning: 'struct exception' declared inside parameter list ../../src/internal.c:63:13: warning: its scope is only this definition or declaration, which is probably not what you want ../../src/internal.c:63:1: error: conflicting types for '_matherr' /usr/x86_64-w64-mingw32/sys-root/mingw/include/math.h:179:23: note: previous declaration of '_matherr' was here make: *** [internal.o] Error 1 ********************************************************** The "error: conflicting types for '_matherr'" appeared. internal.c:63 62: int 63: GP_MATHERR( STRUCT_EXCEPTION_P_X ) /usr/x86_64-w64-mingw32/sys-root/mingw/include/math.h:179 177: #ifndef _CRT_MATHERR_DEFINED 178: #define _CRT_MATHERR_DEFINED 179: _CRTIMP int __cdecl _matherr (struct _exception *); 180: #endif Hmmm! What is wrong? Regards Tatsuro |
|
From: Ethan A M. <sf...@us...> - 2011-08-24 19:18:12
|
On Tuesday, August 23, 2011 08:49:33 pm Tatsuro MATSUOKA wrote: > > I am now trying to build gnuplot under mingw64 environments. > > I have encountered compile error. > #********************* > x86_64-w64-mingw32-gcc -shared-libgcc -c -I/cygdrive/c/Programs/gplibs64/incl -O3 -I. -I../../src -D_Windows -DHAVE_CONFIG_H -DPIPES -DWGP_CONSOLE -DUSE_ME=1 -DWIN_IPC -DWITH_HTML_HELP -I/cygdrive/c/PROGRA~2/HELPWO~1/include -DHAVEBGD -DHAVE_LIBPNG -DHAVE_GD_GIF -DGIF_ANIMATION -DHAVE_GD_PNG -DHAVE_GD_JPEG AVE_GD_TTF -DHAVE_CAIROPDF -DHAVE_ICONV ../../src/internal.c > ../../src/internal.c:63:1: warning: '_matherr' redeclared without dllimport aibute: previous dllimport ignored > ../../src/internal.c: In function '_matherr': > ../../src/internal.c:64:1: error: number of arguments doesn't match prototype > /usr/x86_64-w64-mingw32/sys-root/mingw/include/math.h:179:23: error: prototypeclaration > make: *** [internal.o] Error 1 > #************************* > > I have attached zipped math.h used this build. > > Any suggestions ? The only way I can see for that error message to make sense is if HAVE_STRUCT_EXCEPTION_IN_MATH_H is not defined. Is the setting in config/config.mgw correct? Ethan > Regards > > Tatsuro |
|
From: Tatsuro M. <tma...@ya...> - 2011-08-24 03:49:43
|
Hello I am now trying to build gnuplot under mingw64 environments. I have encountered compile error. #********************* x86_64-w64-mingw32-gcc -shared-libgcc -c -I/cygdrive/c/Programs/gplibs64/incl -O3 -I. -I../../src -D_Windows -DHAVE_CONFIG_H -DPIPES -DWGP_CONSOLE -DUSE_ME=1 -DWIN_IPC -DWITH_HTML_HELP -I/cygdrive/c/PROGRA~2/HELPWO~1/include -DHAVEBGD -DHAVE_LIBPNG -DHAVE_GD_GIF -DGIF_ANIMATION -DHAVE_GD_PNG -DHAVE_GD_JPEG AVE_GD_TTF -DHAVE_CAIROPDF -DHAVE_ICONV ../../src/internal.c ../../src/internal.c:63:1: warning: '_matherr' redeclared without dllimport aibute: previous dllimport ignored ../../src/internal.c: In function '_matherr': ../../src/internal.c:64:1: error: number of arguments doesn't match prototype /usr/x86_64-w64-mingw32/sys-root/mingw/include/math.h:179:23: error: prototypeclaration make: *** [internal.o] Error 1 #************************* I have attached zipped math.h used this build. Any suggestions ? Regards Tatsuro |
|
From: Mojca M. <moj...@gm...> - 2011-08-22 23:53:48
|
On Fri, Aug 19, 2011 at 09:17, Xenia wrote: > Dear gnuplot-folks, > > I don't know how many of you are using ConTeXt [1] for creating > documents. I do. And I am sure many ConTeXt-users will agree with me, > that gnuplot really needs a context-terminal, so that you can implement > gnuplot directly in the tex-file. > I would really appreciate this and as far as I know that is not > integrated until now. Since a possibility already seems to exist [2], I > guess it wouldn't be a big problem. This depends on decision from main gnuplot developers. I just wanted to mention that Mandriva 2011 that is going to be released in 6 days contains TeX Live 2010 (updated to TeX Live repository snapshot from March 2011 which is highly confusing, but welll ...). I tested whether ConTeXt terminal works fine there (= if ConTeXt compiles the source code generated with that terminal) using RC2 and it seems that it does. One of the latest mentioned conditions for inclusion of terminal was that linux distributions should start shipping version of ConTeXt suitable to compile the terminal. (TikZ terminal for ConTeXt is broken and useless at the moment; I don't know why or since when, but it never really worked in any released version so far. TikZ developer also had some problems running ConTeXt, so he probably didn't test enough during development.) > I hope I'm writing to the right list. You are. Thanks a lot for your interest. Please ask if you will have any other problems (or report if it is going to work satisfactory). > [1] http://wiki.contextgarden.net/ > [2] https://github.com/mojca/gnuplot/blob/master/term/context.trm Mojca |
|
From: Ethan M. <merritt@u.washington.edu> - 2011-08-22 02:44:11
|
On Sunday, 21 August 2011, Tatsuro MATSUOKA wrote: > Hello > > I have found the warnings in the demo test (stringvar.dem) on the wxt terminal: (gnuplot.exe:2364): Pango-WARNING **: couldn't load font "WingDings Not-Rotated 560", falling back to "Sans Not-Rotated 560", expect ugly output. > > Points are plotted 'J' and 'D' instead of characters. > > This may not be a gnuplot problem but a font handling problem of pango. Yes. It means that the pango library could not find the WingDings font. I do not know why the font would be missing, however, since it is a standard MS Windows font named wingding.ttf. Ethan |
|
From: Tatsuro M. <tma...@ya...> - 2011-08-21 23:15:48
|
Hello I have found the warnings in the demo test (stringvar.dem) on the wxt terminal: (gnuplot.exe:2364): Pango-WARNING **: couldn't load font "WingDings Not-Rotated 560", falling back to "Sans Not-Rotated 560", expect ugly output. Points are plotted 'J' and 'D' instead of characters. This may not be a gnuplot problem but a font handling problem of pango. I will be happy if some one will give me suggestions. Regards Tatsuro |
|
From: Christoph B. <us...@be...> - 2011-08-21 13:54:01
|
On 20.08.2011 16:05 Xenia wrote: > Am 20.08.2011 15:21, schrieb Christoph Bersch: >> >> Further, if you want to compile it with 4.4 you must remove the string >> "| TERM_FONTSCALE | TERM_IS_LATEX" in line 2222, which is not supported >> in 4.4.0. > > Is this documented somewhere (in case I want to update someday and there > are similar behaviours)? No, I tried to compile the context.trm myself with the 4.4 version and got an error about unknown TERM_FONTSCALE and found that this is only defined in the cvs version. >> So completely remove the gnuplot-4* directory, and do all the steps >> again from scratch (apt-get source also does not download the source >> again, but just unpacks them). > > It now really works. Great. Great, good to hear :-) Christoph |
|
From: Xenia <yo...@go...> - 2011-08-20 14:04:30
|
Am 20.08.2011 15:21, schrieb Christoph Bersch: > On 20.08.2011 14:43 Xenia wrote: >> Am 19.08.2011 14:50, schrieb Christoph Bersch: >>>> >>>> Means I have to remove or update the patch debian-changes… first. >>> >>> I am not completely sure, but before the package is build again, >>> dpkg-buildpackage seems to clean the source tree and unpatch the source. >>> If guess your "fiddling" did something which now prevents the sources >>> from being unpatched. >>> >>> The best thing would be to remove the sources, redo the steps (with the >>> original sources, without Mojca's changes) and then give the error >>> messages which you get when you call dpkg-buildpackage. >> >> I deleted all patches, that seemed to disturb with > > You should not do that because you remove also the debian-specific > patches which also change the paths where everything is installed! > > The problem is (I found it out now), that when you call > dpkg-buildpackage for the first time, the build system creates a patch > with the changes that you made (with the context terminal). If after the > first build you change something, running dpkg-buildpackage again does > not work because the sources cannot be unpatched. > >> $ quilt delete … >> and did >> $ dpkg-buildpackage >> again. >> It resulted in the same errormessage, just some parts: >> >> character constant [-Wmultichar] >> ../../../term/context.trm:2919:77133: warning: character constant too >> long for its type [enabled by default] > [...] >> ../../../term/context.trm:3307:1: error: stray ‘`’ in program > > I guess, you downloaded the wrong context.trm, maybe the HTML-view of > the git Repository. The context.trm which I got from > <https://raw.github.com/mojca/gnuplot/master/term/context.trm> has only > 2395 lines! > > Further, if you want to compile it with 4.4 you must remove the string > "| TERM_FONTSCALE | TERM_IS_LATEX" in line 2222, which is not supported > in 4.4.0. Is this documented somewhere (in case I want to update someday and there are similar behaviours)? > So completely remove the gnuplot-4* directory, and do all the steps > again from scratch (apt-get source also does not download the source > again, but just unpacks them). It now really works. Great. Thank you very much. :-) Xenia |
|
From: Christoph B. <us...@be...> - 2011-08-20 13:22:06
|
On 20.08.2011 14:43 Xenia wrote: > Am 19.08.2011 14:50, schrieb Christoph Bersch: >>> >>> Means I have to remove or update the patch debian-changes… first. >> >> I am not completely sure, but before the package is build again, >> dpkg-buildpackage seems to clean the source tree and unpatch the source. >> If guess your "fiddling" did something which now prevents the sources >> from being unpatched. >> >> The best thing would be to remove the sources, redo the steps (with the >> original sources, without Mojca's changes) and then give the error >> messages which you get when you call dpkg-buildpackage. > > I deleted all patches, that seemed to disturb with You should not do that because you remove also the debian-specific patches which also change the paths where everything is installed! The problem is (I found it out now), that when you call dpkg-buildpackage for the first time, the build system creates a patch with the changes that you made (with the context terminal). If after the first build you change something, running dpkg-buildpackage again does not work because the sources cannot be unpatched. > $ quilt delete … > and did > $ dpkg-buildpackage > again. > It resulted in the same errormessage, just some parts: > > character constant [-Wmultichar] > ../../../term/context.trm:2919:77133: warning: character constant too > long for its type [enabled by default] [...] > ../../../term/context.trm:3307:1: error: stray ‘`’ in program I guess, you downloaded the wrong context.trm, maybe the HTML-view of the git Repository. The context.trm which I got from <https://raw.github.com/mojca/gnuplot/master/term/context.trm> has only 2395 lines! Further, if you want to compile it with 4.4 you must remove the string "| TERM_FONTSCALE | TERM_IS_LATEX" in line 2222, which is not supported in 4.4.0. So completely remove the gnuplot-4* directory, and do all the steps again from scratch (apt-get source also does not download the source again, but just unpacks them). Christoph |
|
From: Xenia <yo...@go...> - 2011-08-20 12:43:01
|
Am 19.08.2011 14:50, schrieb Christoph Bersch:
>>
>> Means I have to remove or update the patch debian-changes… first.
>
> I am not completely sure, but before the package is build again,
> dpkg-buildpackage seems to clean the source tree and unpatch the source.
> If guess your "fiddling" did something which now prevents the sources
> from being unpatched.
>
> The best thing would be to remove the sources, redo the steps (with the
> original sources, without Mojca's changes) and then give the error
> messages which you get when you call dpkg-buildpackage.
I deleted all patches, that seemed to disturb with
$ quilt delete …
and did
$ dpkg-buildpackage
again.
It resulted in the same errormessage, just some parts:
character constant [-Wmultichar]
../../../term/context.trm:2919:77133: warning: character constant too
long for its type [enabled by default]
../../../term/context.trm:2919:77160: warning: multi-character character
constant [-Wmultichar]
../../../term/context.trm:2919:77170: warning: character constant too
long for its type [enabled by default]
../../../term/context.trm:2919:77201: warning: multi-character ../../..
This repeats again and again; after that:
/term/context.trm:2919:17: error: stray ‘#’ in program
../../../term/context.trm:2919:17: error: stray ‘\’ in program
../../../term/context.trm:2919:17: error: stray ‘#’ in program
../../../term/context.trm:2919:79373: warning: multi-character character
constant [-Wmultichar]
../../../term/context.trm:2919:79383: warning: character constant too
long for its type [enabled by default]
[…]
../../../term/context.trm:2919:17: error: stray ‘\’ in program
[…]
In file included from ../../../src/term.h:458:0,
from ../../../src/term.c:1476:
../../../term/context.trm:3004:13: error: stray ‘#’ in program
../../../term/context.trm:3004:13: error: stray ‘#’ in program
../../../term/context.trm:3018:5: error: stray ‘#’ in program
[…]
../../../term/context.trm:3158:11: error: stray ‘\342’ in program
../../../term/context.trm:3158:11: error: stray ‘\206’ in program
../../../term/context.trm:3158:11: error: stray ‘\220’ in program
../../../term/context.trm:3162:11: error: stray ‘\342’ in program
../../../term/context.trm:3162:11: error: stray ‘\206’ in program
../../../term/context.trm:3162:11: error: stray ‘\222’ in program
../../../term/context.trm:3166:11: error: stray ‘\342’ in program
../../../term/context.trm:3166:11: error: stray ‘\206’ in program
../../../term/context.trm:3166:11: error: stray ‘\221’ in program
../../../term/context.trm:3170:11: error: stray ‘\342’ in program
../../../term/context.trm:3170:11: error: stray ‘\206’ in program
../../../term/context.trm:3170:11: error: stray ‘\223’ in program
../../../term/context.trm:3180:11: error: stray ‘\342’ in program
../../../term/context.trm:3180:11: error: stray ‘\206’ in program
../../../term/context.trm:3180:11: error: stray ‘\220’ in program
../../../term/context.trm:3184:11: error: stray ‘\342’ in program
../../../term/context.trm:3184:11: error: stray ‘\206’ in program
../../../term/context.trm:3184:11: error: stray ‘\222’ in program
../../../term/context.trm:3188:11: error: stray ‘\342’ in program
../../../term/context.trm:3188:11: error: stray ‘\206’ in program
../../../term/context.trm:3188:11: error: stray ‘\221’ in program
../../../term/context.trm:3192:11: error: stray ‘\342’ in program
../../../term/context.trm:3192:11: error: stray ‘\206’ in program
../../../term/context.trm:3192:11: error: stray ‘\223’ in program
../../../term/context.trm:3231:3: error: invalid preprocessing directive
#This
../../../term/context.trm:3232:1: error: stray ‘##’ in program
../../../term/context.trm:3233:1: error: stray ‘##’ in program
../../../term/context.trm:3233:1: error: stray ‘##’ in program
../../../term/context.trm:3233:1: error: stray ‘##’ in program
../../../term/context.trm:3250:10: error: invalid suffix "a" on integer
constant
../../../term/context.trm:3251:10: error: invalid suffix "b" on integer
constant
../../../term/context.trm:3257:11: error: invalid suffix "a" on integer
constant
../../../term/context.trm:3258:11: error: invalid suffix "b" on integer
constant
../../../term/context.trm:3274:5: warning: missing terminating '
character [enabled by default]
../../../term/context.trm:3274:1: error: missing terminating ' character
../../../term/context.trm:3285:1: error: stray ‘`’ in program
../../../term/context.trm:3285:1: error: stray ‘`’ in program
../../../term/context.trm:3285:1: error: stray ‘`’ in program
../../../term/context.trm:3288:20: warning: multi-character character
constant [-Wmultichar]
../../../term/context.trm:3291:1: error: stray ‘`’ in program
../../../term/context.trm:3291:1: error: stray ‘`’ in program
../../../term/context.trm:3291:1: error: stray ‘`’ in program
../../../term/context.trm:3307:1: error: stray ‘`’ in program
../../../term/context.trm:3307:1: error: stray ‘`’ in program
But not only errors about context.trm, also:
../../../src/term.c:2:14: warning: ‘RCSid’ defined but not used
[-Wunused-function]
../../../term/driver.h:45:13: warning: ‘do_point’ declared ‘static’ but
never defined [-Wunused-function]
../../../term/driver.h:46:13: warning: ‘line_and_point’ declared
‘static’ but never defined [-Wunused-function]
../../../term/driver.h:47:12: warning: ‘null_text_angle’ declared
‘static’ but never defined [-Wunused-function]
../../../term/driver.h:48:12: warning: ‘null_justify_text’ declared
‘static’ but never defined [-Wunused-function]
../../../term/driver.h:49:12: warning: ‘null_scale’ declared ‘static’
but never defined [-Wunused-function]
../../../term/driver.h:50:13: warning: ‘options_null’ declared ‘static’
but never defined [-Wunused-function]
../../../term/driver.h:51:13: warning: ‘UNKNOWN_null’ declared ‘static’
but never defined [-Wunused-function]
make[2]: *** [term.o] Fehler 1
make[2]: Leaving directory `/home/user/gnuplot-4.4.0/debian/build-nox/src'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/home/user/gnuplot-4.4.0/debian/build-nox/src'
make: *** [build-nox-stamp] Fehler 2
dpkg-buildpackage: Fehler: Fehler-Exitstatus von debian/rules build war 2
What to do?
Thanks a lot for you patience and help.
Xenia
|
|
From: Christoph B. <us...@be...> - 2011-08-19 12:50:28
|
On 19.08.2011 14:32, Xenia wrote: > Am 19.08.2011 10:45, schrieb Christoph Bersch: >> dpkg-buildpackage > > Something went wrong here. No .deb-file were created, an errormessage > appeared (unfortenately I didn't save it). Well, that is essential. > After I did some things > (don't remember what I actually did), I tried it again and were > requested to do a > dpkg-buildpackage: Host-Architektur amd64 > dpkg-source --before-build gnuplot-4.4.0 > debian/rules clean > QUILT_PATCHES=debian/patches \ > quilt --quiltrc /dev/null pop -a -R || test $? = 2 > Patch debian-changes-4.4.0-1.1 kann nicht entfernt werden (Patch > aktualisieren oder entfernen erzwingen mit -f) > make: *** [unpatch] Fehler 1 > dpkg-buildpackage: Fehler: Fehler-Exitstatus von debian/rules clean war 2 > > Means I have to remove or update the patch debian-changes… first. I am not completely sure, but before the package is build again, dpkg-buildpackage seems to clean the source tree and unpatch the source. If guess your "fiddling" did something which now prevents the sources from being unpatched. The best thing would be to remove the sources, redo the steps (with the original sources, without Mojca's changes) and then give the error messages which you get when you call dpkg-buildpackage. Christoph |
|
From: Xenia <yo...@go...> - 2011-08-19 12:31:32
|
Am 19.08.2011 10:45, schrieb Christoph Bersch: > On 19.08.2011 10:12, Mojca Miklavec wrote: >> >>> But then I got: >>> --------------------- >>> $ ./prepare >>> >>> ./prepare: 47: aclocal: not found >>> >>> Some part of the preparation process failed. >>> Please refer to INSTALL for details. >>> --------------------- >>> >>> And in "INSTALL" and "INSTALL.gnu" the first step is to do >>> $ ./configure >>> but I only have a configure.in and configure.vms -file. >>> I'm quite confused. >>> So I installed it from the debian-repositories (for sure without any >>> context-implementation), but you could just tell me, how I can make your >>> version work. :-) >> >> One option is probably also to patch gnuplot source package from >> Debian repositories, I don't know how to do that since I don't use >> Debian (but you only need to add context.trm to other terminals and >> add one #include "context.trm" line to src/term.h). > > I guess this is the easiest option if you have no experience with > compilation of source code. > I hope, the following steps do what you need (I do not run wheezy). If > not, just ask again :-) > > Get the source code of the debian package: > apt-get source gnuplot > > Install the required dependencies for building gnuplot (this can be a lot!): > apt-get build-dep gnuplot > > Change the code like Mojca wrote: > 1. copy context.trm to gnuplot-4.4*/term/ (I do not know the exact > version number) > 2. Add #include "context.trm" at the end of file term.h (right before > the last #endif statement) > > cd gnuplot-4.4* > dpkg-buildpackage Something went wrong here. No .deb-file were created, an errormessage appeared (unfortenately I didn't save it). After I did some things (don't remember what I actually did), I tried it again and were requested to do a $ make distclean before. But again trying to build the package I got now: $ sudo dpkg-buildpackage dpkg-buildpackage: exportieren von CFLAGS aus dpkg-buildflags (Quelle: vendor): -g -O2 dpkg-buildpackage: exportieren von CPPFLAGS aus dpkg-buildflags (Quelle: vendor): dpkg-buildpackage: exportieren von CXXFLAGS aus dpkg-buildflags (Quelle: vendor): -g -O2 dpkg-buildpackage: exportieren von FFLAGS aus dpkg-buildflags (Quelle: vendor): -g -O2 dpkg-buildpackage: exportieren von LDFLAGS aus dpkg-buildflags (Quelle: vendor): dpkg-buildpackage: Quellpaket gnuplot dpkg-buildpackage: Quellversion 4.4.0-1.1 dpkg-buildpackage: Quellen geändert durch Agustin Martin Domingo <agm...@de...> dpkg-buildpackage: Host-Architektur amd64 dpkg-source --before-build gnuplot-4.4.0 debian/rules clean QUILT_PATCHES=debian/patches \ quilt --quiltrc /dev/null pop -a -R || test $? = 2 Patch debian-changes-4.4.0-1.1 kann nicht entfernt werden (Patch aktualisieren oder entfernen erzwingen mit -f) make: *** [unpatch] Fehler 1 dpkg-buildpackage: Fehler: Fehler-Exitstatus von debian/rules clean war 2 Means I have to remove or update the patch debian-changes… first. But I'm overextended. :-( > Go and drink a coffee... > > Install the .deb package manually: > > cd .. > dpkg -i gnuplot*.deb > > Mark those packages with 'hold' so that they are not overwritten on the > next upgrade (and this may happen soon on testing): > > echo gnuplot hold | dpkg --set-selections > echo gnuplot-doc hold | dpkg --set-selections > echo gnuplot-nox hold | dpkg --set-selections > echo gnuplot-x11 hold | dpkg --set-selections > > > Christoph > > ------------------------------------------------------------------------------ > Get a FREE DOWNLOAD! and learn more about uberSVN rich system, > user administration capabilities and model configuration. Take > the hassle out of deploying and managing Subversion and the > tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 > _______________________________________________ > gnuplot-beta mailing list > gnu...@li... > https://lists.sourceforge.net/lists/listinfo/gnuplot-beta |
|
From: Christoph B. <us...@be...> - 2011-08-19 08:59:36
|
On 19.08.2011 10:12, Mojca Miklavec wrote:
>
>> But then I got:
>> ---------------------
>> $ ./prepare
>>
>> ./prepare: 47: aclocal: not found
>>
>> Some part of the preparation process failed.
>> Please refer to INSTALL for details.
>> ---------------------
>>
>> And in "INSTALL" and "INSTALL.gnu" the first step is to do
>> $ ./configure
>> but I only have a configure.in and configure.vms -file.
>> I'm quite confused.
>> So I installed it from the debian-repositories (for sure without any
>> context-implementation), but you could just tell me, how I can make your
>> version work. :-)
>
> One option is probably also to patch gnuplot source package from
> Debian repositories, I don't know how to do that since I don't use
> Debian (but you only need to add context.trm to other terminals and
> add one #include "context.trm" line to src/term.h).
I guess this is the easiest option if you have no experience with
compilation of source code.
I hope, the following steps do what you need (I do not run wheezy). If
not, just ask again :-)
Get the source code of the debian package:
apt-get source gnuplot
Install the required dependencies for building gnuplot (this can be a lot!):
apt-get build-dep gnuplot
Change the code like Mojca wrote:
1. copy context.trm to gnuplot-4.4*/term/ (I do not know the exact
version number)
2. Add #include "context.trm" at the end of file term.h (right before
the last #endif statement)
cd gnuplot-4.4*
dpkg-buildpackage
Go and drink a coffee...
Install the .deb package manually:
cd ..
dpkg -i gnuplot*.deb
Mark those packages with 'hold' so that they are not overwritten on the
next upgrade (and this may happen soon on testing):
echo gnuplot hold | dpkg --set-selections
echo gnuplot-doc hold | dpkg --set-selections
echo gnuplot-nox hold | dpkg --set-selections
echo gnuplot-x11 hold | dpkg --set-selections
Christoph
|
|
From: Mojca M. <moj...@gm...> - 2011-08-19 08:12:50
|
Dear Xenia, I'm forwarding your question to the gnuplot mailing list since they can probably help you better with this issue than people on the ConTeXt list. On Fri, Aug 19, 2011 at 09:47, Xenia wrote: >>> >>> I'm having some problems with gnuplot. >>> >>> I tried the minimal example from http://wiki.contextgarden.net/Gnuplot , >>> but I recieve just a .plt-file. >> >> 1.) What operating system are you using? > > debian-wheezy (testing) > >> 2.) Did you compile gnuplot from https://github.com/mojca/gnuplot or >> did you use the default gnuplot as shipped with your system? > > I tried following this instruction: > http://wiki.contextgarden.net/Gnuplot#Unix_or_Mac > > But then I got: > --------------------- > $ ./prepare > > ./prepare: 47: aclocal: not found > > Some part of the preparation process failed. > Please refer to INSTALL for details. > --------------------- > > And in "INSTALL" and "INSTALL.gnu" the first step is to do > $ ./configure > but I only have a configure.in and configure.vms -file. > I'm quite confused. > So I installed it from the debian-repositories (for sure without any > context-implementation), but you could just tell me, how I can make your > version work. :-) One option is probably also to patch gnuplot source package from Debian repositories, I don't know how to do that since I don't use Debian (but you only need to add context.trm to other terminals and add one #include "context.trm" line to src/term.h). The instructions in INSTALL are only valid for released versions when somebody else runs ./prepare instead of you before publishing the files. The ./prepare script creates ./configure. It would be really really helpful if configure script was included in source repository, but many argue that this would bring additional problems. (It could indeed happen that the file would get out-of-sync if somebody was modifying configuration and forgot to run ./prepare afterwards, but that would be spotted and resolved quickly. It would cause way less pain to "end users" trying to compile gnuplot from source.) You probably need to have autoconfigure installed or something like that. Others may know more precisely what is needed / what Debian package you need to install. Mojca |
|
From: Xenia <yo...@go...> - 2011-08-19 07:16:50
|
Dear gnuplot-folks, I don't know how many of you are using ConTeXt [1] for creating documents. I do. And I am sure many ConTeXt-users will agree with me, that gnuplot really needs a context-terminal, so that you can implement gnuplot directly in the tex-file. I would really appreciate this and as far as I know that is not integrated until now. Since a possibility already seems to exist [2], I guess it wouldn't be a big problem. I hope I'm writing to the right list. Thank you. Xenia [1] http://wiki.contextgarden.net/ [2] https://github.com/mojca/gnuplot/blob/master/term/context.trm |
|
From: Mojca M. <moj...@gm...> - 2011-08-18 23:33:10
|
Dear Peter,
there seems to be a problem with colours in ConTeXt with TikZ terminal
in gnuplot. I'm not sure since when the problem exists (when I was
last testing it worked fine, but that was probably several months
ago).
Please keep in mind that \color is an existing command in ConTeXt that
uses a different syntax than LaTeX, so your code using \color is not
really portable.
% wrapper for color settings
\def\gpcolor#1{\tikzset{global #1}}
\tikzset{rgb color/.code={\pgfutil@definecolor{.}{rgb}{#1}\color{.}}}
\tikzset{global rgb color/.code={\pgfutil@definecolor{.}{rgb}{#1}\color{.}}}
\tikzset{global color/.code={\color{#1}}}
Here is a minimal context document to reproduce the problem (you may
try to use TeX Live 2011 to compile it; TikZ has been patched, so it
works with ConTeXt again):
\usemodule[gnuplot-lua-tikz]
\starttext
\starttikzpicture[gnuplot]
\gpcolor{color=gp lt color border}
\gpsetlinetype{gp lt border}
\draw[gp path] (1.410,7.185)--(1.410,0.730)--(12.048,0.730)--(12.048,7.185)--cycle;
\stoptikzpicture
\stoptext
Here is the error:
! Use of \color doesn't match its definition.
\pgfkeys@code #1\pgfeov ->\color {
#1}
\pgfkeysifdefined ...ifcsname pgfk@#1\endcsname #2
\else #3\fi
\pgfkeys@unpack ...pgfeov \else \pgfkeys@case@one
\fi \fi
\pgfkeys@normal ...\pgfkeysnovalue =\pgfkeys@stop
\pgfkeys@parse
\pgfkeys@@qset ...aultpath {#2/}\pgfkeys@parse #3,
\pgfkeys@mainstop \def \pg...
l.5 \gpcolor{color=gp lt color border}
?
You either need to write a different code for ConTeXt or use some
other strategy to apply colours.
Thank you very much,
Mojca
|
|
From: Mojca M. <moj...@gm...> - 2011-08-01 16:40:40
|
On Mon, Aug 1, 2011 at 17:28, sfeam (Ethan Merritt) wrote: > >> - The window stays behind the terminal when plotting to it > > [shrug] I consider that a very desirable feature. But I believe you > can configure it differently using ./configure --raise-console I will try. >> (but on the >> other hand that is almost the same in matlab); this is slightly >> non-desirable and probably easy to fix if one knows what to fix. >> >> - wxt seems to be great in supporting a lot of mouse events (scroll >> left & right, zoom in & out); would there be any chance to add left & >> right scrolling and zoom in & out events based on "mouse gestures" >> supported by apple? Apple's mouse supports scrolling left and right >> and zooming in and out natively. These events would only have to >> become synonyms with current shift+scroll up/down. > > If you can figure out what the event/keystroke/whatever > the system sends when it sees these "gestures", then you can simply > add them to the dispatch table in gpexecute.c and/or mouse.c I don't understand how gpexecute.c and mouse.c work, but I see that wx_gui.c does quite a lot with mouse. There seems to be GetWheelAxis() in http://docs.wxwidgets.org/trunk/classwx_mouse_event.html, but I'm not sure how well that works if it works at all (no idea what happens in case of diagonal movements). I don't find any zoom event in wxt tutorial. There is a documentation for Mac (NSEventTypeSwipe & NSEventTypeMagnify working since 10.6): https://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/EventOverview/HandlingTouchEvents/HandlingTouchEvents.html#//apple_ref/doc/uid/10000060i-CH13-SW10 but I have no idea yet where those events could be plugged it. >> - After I play with zoom a bit, I'm unable to go back to original/auto >> focus; also when I plot the next function, the zoom still stays at >> some weird place where it was left at the first plot; I'm unable to >> figure out how to get default scale. > > Type "u" for "unzoom" in the plot window? > (not sure what you mean by "auto focus") Yes, "u" works perfectly. The problem is that I was playing with buttons in the window: - replot - apply previous zoom settings - apply next zoom settings - apply autoscale None of them was able to reproduce the behaviour of "u". If I can use mouse to change the range, I would find it useful to be able to use the mouse to revert the change as well. > Anyhow, I take it the bottom line is that wxWidgets 2.8 does work, > but 2.9 does not? True. I'm not sure what is wrong with 2.9, but it might also be a bug in their code, not just the need to rewrite the program. It would make a lot of sense to resolve such bugs before 3.0 is released, but I don't know how to create a minimal example to submit a bug report (if there is one). Mojca |
|
From: sfeam (E. Merritt) <eam...@gm...> - 2011-08-01 15:28:33
|
On Monday, 01 August 2011, Mojca Miklavec wrote: > On Sat, Jul 30, 2011 at 19:03, sfeam (Ethan Merritt) wrote: > > On Saturday, 30 July 2011, Mojca Miklavec wrote: > >> Hello, > >> > >> The new gnuplot sources at least compile out of the box with wxt > >> (wxWidgets 2.9.2), > > > > To the best of my knowledge, no one has reported experience with > > gnuplot + wxWidgets 2.9 on any platform. Wouldn't it make more > > sense for you to test first with 2.8, which we know works on > > other platforms? > > After going through some pain, I managed to compile wxWidgets 2.8 and > link gnuplot against it. > > It seems to work fine apart from some minor (not too important) issues: > > - The window stays behind the terminal when plotting to it [shrug] I consider that a very desirable feature. But I believe you can configure it differently using ./configure --raise-console > (but on the > other hand that is almost the same in matlab); this is slightly > non-desirable and probably easy to fix if one knows what to fix. > > - wxt seems to be great in supporting a lot of mouse events (scroll > left & right, zoom in & out); would there be any chance to add left & > right scrolling and zoom in & out events based on "mouse gestures" > supported by apple? Apple's mouse supports scrolling left and right > and zooming in and out natively. These events would only have to > become synonyms with current shift+scroll up/down. If you can figure out what the event/keystroke/whatever the system sends when it sees these "gestures", then you can simply add them to the dispatch table in gpexecute.c and/or mouse.c > - After I play with zoom a bit, I'm unable to go back to original/auto > focus; also when I plot the next function, the zoom still stays at > some weird place where it was left at the first plot; I'm unable to > figure out how to get default scale. Type "u" for "unzoom" in the plot window? (not sure what you mean by "auto focus") Anyhow, I take it the bottom line is that wxWidgets 2.8 does work, but 2.9 does not? That would be consistent with the project web site, which strongly implies that code changes are necessary when switching from 2.8 to 2.9. Ethan |
|
From: Mojca M. <moj...@gm...> - 2011-08-01 12:16:18
|
On Sat, Jul 30, 2011 at 19:03, sfeam (Ethan Merritt) wrote: > On Saturday, 30 July 2011, Mojca Miklavec wrote: >> Hello, >> >> The new gnuplot sources at least compile out of the box with wxt >> (wxWidgets 2.9.2), > > To the best of my knowledge, no one has reported experience with > gnuplot + wxWidgets 2.9 on any platform. Wouldn't it make more > sense for you to test first with 2.8, which we know works on > other platforms? After going through some pain, I managed to compile wxWidgets 2.8 and link gnuplot against it. It seems to work fine apart from some minor (not too important) issues: - The window stays behind the terminal when plotting to it (but on the other hand that is almost the same in matlab); this is slightly non-desirable and probably easy to fix if one knows what to fix. - wxt seems to be great in supporting a lot of mouse events (scroll left & right, zoom in & out); would there be any chance to add left & right scrolling and zoom in & out events based on "mouse gestures" supported by apple? Apple's mouse supports scrolling left and right and zooming in and out natively. These events would only have to become synonyms with current shift+scroll up/down. - After I play with zoom a bit, I'm unable to go back to original/auto focus; also when I plot the next function, the zoom still stays at some weird place where it was left at the first plot; I'm unable to figure out how to get default scale. Mojca |
|
From: Mojca M. <moj...@gm...> - 2011-07-30 19:59:39
|
On Sat, Jul 30, 2011 at 21:19, sfeam (Ethan Merritt) wrote: > On Saturday, 30 July 2011, Mojca Miklavec wrote: > > getcolor needs to be built twice, once for inclusion in gnuplot proper > and once for inclusion in gnuplot_x11. From the error messages you > show, it looks to me that one of the two versions either was not built > at all or was built in the wrong order. It seems that I forgot to clean some parts before making them again. Compilation now works fine with both terminals (but I still didn't test anything). Sorry for the noise. >> But I would strongly suggest to try to make gnuplot work with >> wxWidgets 2.9. > > From the wxWidgets web site: > wxWidgets 2.9.2 Released 2011-07-05 > "While this is still officially a development release because > some API details are still not frozen, we believe that 2.9.2 > can be used in production environment, especially for the new > projects for which (small) changes in behaviour since 2.8 are > not a problem. Give it a try and let us know what do you think!" > > There is also a Change Log with a fairly long list of things that > need to be changed in the calling program to switch from 2.8 to 2.9 > (actually it says 3.0, which is kind of confusing). The version 2.9 will become 3.0 once it gets out of testing phase which should be by the end of 2011. It also says: Next development release: 2.9.3 The next planned release is 2.9.3 and is planned to happen in the autumn of 2011. It should integrate the work done during GSoC 2011 and will be the final 2.9.x release before 3.0. We hope to make 3.0 at the end of 2011. The only remaining issues are: - Cocoa-based wxOSX port running in 64 bit mode: testing and final touches - GTK+ 3 port: in progress as part of GSoC 2011: which means that it has to be finished in August > So I think 2.9 is not yet ready for prime time, and trying to > debug a 2.9 installation when you don't even have 2.8 working > sounds like a difficult task. But also keep in mind that on Mac I can only use fully outdated and unsupported framework that 2.8 depends upon. The bugs that enable building 2.8 have recently been fixed in MacPorts, but I'm still unable to build wxWidgets on my local machine. Maybe the next gnuplot release could depend on 2.8, but it would be great if CVS version could start supporting 2.9, so that if any bugs in wxWidgets are discovered, they can be reported upstream, but also to get enough testing in time for the second gnuplot release from now on. Mojca |