Attached I have a Function plotter INX file without the notebooks. The dialog is ugly, very ugly. But can someone check to see if it works on Win32 without the notebooks?
Thanks, Ted
On Tue, 2008-01-15 at 13:25 -0600, Aaron Spike wrote:
Ted Gould wrote:
Attached I have a Function plotter INX file without the notebooks. The dialog is ugly, very ugly. But can someone check to see if it works on Win32 without the notebooks?
I think this actually works. But why?
Uhm, no clue, can you send the same command line dumps you send earlier but with the new INX file?
--Ted
Ted Gould wrote:
On Tue, 2008-01-15 at 13:25 -0600, Aaron Spike wrote:
Ted Gould wrote:
Attached I have a Function plotter INX file without the notebooks. The dialog is ugly, very ugly. But can someone check to see if it works on Win32 without the notebooks?
I think this actually works. But why?
Uhm, no clue, can you send the same command line dumps you send earlier but with the new INX file?
Most certainly.
share\extensions\funcplot.py C:\DOCUME~1\NS\LOCALS~1\Temp\ink_ext_XXXXXX.svg3LCY4T --id=rect2363 --xstart=0 --xend=10 --times2pi=true --ybottom=-11.600000381469727 --ytop=24.600000381469727 --samples=180 --isoscale=false --polar=false --funcplotuse= --pythonfunctions= --fofx=sin(-x) --fponum=true --fpofx=x --remove=true --drawaxis=true
['share\extensions\funcplot.py', 'C:\DOCUME~1\NS\LOCALS~1\Temp\ink_ext_XXXXXX.svg3LCY4T', '--id=rect2363', '--xstart=0', '--xend=10', '--times2pi=true', '--ybottom=-11.600000381469727', '--ytop=24.600000381469727', '--samples=180', '--isoscale=false', '--polar=false', '--funcplotuse=', '--pythonfunctions=', '--fofx=sin(-x)', '--fponum=true', '--fpofx=x', '--remove=true', '--drawaxis=true']
{'polar': False, 'ytop': 24.600000381469727, 'funcplotuse': '', 'drawaxis': True, 'fpofx': 'x', 'ybottom': -11.600000381469727, 'ids': ['rect2363'], 'remove': True, 'fofx': 'sin(-x)', 'pythonfunctions': '', 'isoscale': False, 'fponum': True, 'tab': 'sampling', 'xstart': 0.0, 'xend': 10.0, 'times2pi': True, 'samples': 180}
Aaron Spike
hope I'm not going to embarrass myself here, but I think the problem is that the notebook parameter is not transmitted with the same syntax as the other parameters. Typically the other parameters arrive in the form : --fontsize=14 whereas the notebook parameter arrives in the form : --tab="measure"
I believe the extra quotation marks are causing the problem, which leads to the parser failing and using default values. (data is copied from bug 183030)
So where do the extra quotation marks come from? It is interesting to note that the notebook parameter is distinctly different from the other parameters in terms of how it gets its data. All the other parameters get their default data from the same 'node' in the inx file. The notebook parameter is unique in that it has a subnode called page, so it gets its data indirectly from page, not directly from its own node.
Is it possible that this extra step in the data transfer could lead to the unwanted quotation marks?
Sorry for the mangled terminology, this is not my usual field of endeavor.
On Tue, 2008-01-15 at 18:14 -0500, Alvin Penner wrote:
hope I'm not going to embarrass myself here, but I think the problem is that the notebook parameter is not transmitted with the same syntax as the other parameters. Typically the other parameters arrive in the form : --fontsize=14 whereas the notebook parameter arrives in the form : --tab="measure"
Yeah, I think that the double quotes are probably causing the problem, but I wonder if it's just that the GTK+ wrappers are not escaping them within other strings properly.
Anyway, does anyone really care which tab is selected in a notebook? Is that a useful thing to pass to a script? Can we get around the problem by deleting that?
--Ted
I agree, can't think of any reason why the python script would need to know which tab was selected.
Would it be possible to just transmit a null value for the "notebook" parameter to the python script? This could be similar to what is done for the "description" type parameters, where nothing is actually transmitted to the python script, as far as I can tell.
- Alvin
At 09:32 PM 1/15/2008 -0800, Ted Gould wrote:
On Tue, 2008-01-15 at 18:14 -0500, Alvin Penner wrote:
hope I'm not going to embarrass myself here, but I think the problem is that the notebook parameter is not transmitted with the same syntax as the other parameters. Typically the other parameters arrive in the form : --fontsize=14 whereas the notebook parameter arrives in the form : --tab="measure"
Yeah, I think that the double quotes are probably causing the problem, but I wonder if it's just that the GTK+ wrappers are not escaping them within other strings properly.
Anyway, does anyone really care which tab is selected in a notebook? Is that a useful thing to pass to a script? Can we get around the problem by deleting that?
--TedAttachment Converted: "c:\program files\eudora\attach\signature3.asc"
participants (3)
-
Aaron Spike -
Alvin Penner -
Ted Gould