On Sun, 15 May 2005, James Graham wrote:
Excellent :) I played with the code a little since then... I'll have to look at how the new code will play with you bugfixes... in essence I changed the behavior so that opening a file overwrites the current window if it's a blank unmodified file. I also have drag and drop of files from a file manager (apparently) working, and added support for globbing of command line arguments (so something like veusz *.vsz will open all veusz files in the current directory). Oh and a reload button/command... but I'll test these things a bit more I think ;)
Forgot to say - I have put some code in stopping a new window being opened if the current is blank.
Right, the correct behavior is probably to initiate the new window so that the working directory is the same as the window which opened it. After that, each window should be able to change working directories independently.
Maybe...
Which doesn't work because the console traps and displays the error first. Is there an easy elegant way to make the error propogate when calling from a GUI object but not when calling from the command line?
Yes - I forgot to say it wasn't working! I think we need a separate function to load the data. I'll look into it.
Well, if you know what the variables names are, it's not hard to parse the expression as a string and do string substitution to replace the variable names with their values. But that's not really clean.
Yes, but I need to know all the ways variable names are placed in the expression. Presumably I could code a regexp up to only look for variable names. It could be fun if people use variables that are the same name as function names, but I expect they'll get what's coming to them...
The problem with the new setup is that the label behaves like left-clicking will have an effect, but it doesn't (well it focuses the table cell but that doesn't _do_ anything). I really don't know what the solution is (short of dropping those functions which I assume you use...). Maybe if clicking selected the whole table row (rather than just a single cell) and the context menu was defined on the row?
It now allows the use of cursor keys, which is nice for keyboard navigation. I'll keep my thinking cap on.
Yesterday I worked on some code which put the subsettings into the property window with the normal settings. It didn't seem to work very well, so I've left the current behaviour.
Jeremy -- Jeremy Sanders <[EMAIL PROTECTED]> http://www.jeremysanders.net/ Cambridge, UK Public Key Server PGP Key ID: E1AAE053
