On Thu, 12 May 2005, James Graham wrote:
Attached is a simple patch that ought to: Allow Ctrl+P as a shortcut for Print Cause "New" to open a new window Cause "Open" to open a new window Cause NameError exceptions when loading a file to be dealt with like IOErrors
Okay. I've put in the Ctrl+P patch, and the New patch (slightly modified). I had to fix a bug in the CommandInterpreter which meant the same document was shared between each command line in different windows! I now copy the environment so it's not shared. Also the environment is made before importing things, so it should be cleaner.
Other random things whilst I remember (some of which I'll get to eventually no doubt): The Edit Dataset dialog seems to be borked. The rename button stays in the depressed state once pressed. The close button is too wide.
Will look at it.
The "New Dataset" dialog is fun but it should probably have a menu item and be called "Create Dataset" or something that makes it clear it's not
It has a menu item doesn't it? Probably should change as you suggest to "Create Dataset".
importing a dataset. As well as a link to that, the Edit Dataset dialog needs a button to open the import dialog.
Good idea.
New datasets should, by default, be given the number of points that one of the datasets in the document has (in the most common case these will all be equal... otherwise it probably doesn't matter much).
Sounds fine.
There should be a way to unlink a file... although I suppose this happens automagically when all the datasets are deleted?
Yes. I should probably show the file the dataset is linked to in edit datasets. There should be an unlink button.
Settings that require the selection of one of the axes should be a dropdown rather than a input box
Good.
It would be neat to have a little [...] button at the end of text inputs for e.g. functions which opened a (non-modal) dialog to update the text in that input using a textarea - this would allow more space
Yes - I was thinking of that...
An easy way of converting a fit into a function would be good (maybe the paramaters for the fit should go into some sort of grid with a column for the name and one for the value? This would make entering things easier but the results harder to copy)
I'm not sure how to do this cleanly. I might have to break open the python parser, substitute in the variables and work out how to write it.
Is keyboard focus in the settings panels going to the labels a result of the context menus or is it normal? In either case, it seems suboptimal...
I made it so that it was clear there was a context menu. Otherwise keyboard users wouldn't be able to get the menu. Try it now with the new QTable properties code. Any suggestions are welcome...
Jeremy -- Jeremy Sanders <[EMAIL PROTECTED]> http://www.jeremysanders.net/ Cambridge, UK Public Key Server PGP Key ID: E1AAE053
