From: Alex T. <al...@tw...> - 2005-04-26 01:10:10
|
On Pythoncard-users, Alex Tweedly wrote: > > C. Resource Editor > > (these are in descending order of importance to me, or increasing > difficulty of implementation) > > 1. property editor window. > I find the current property window pretty clunky. Instead of > displaying (and allowing editing of) one property at a time, with a > list to select which property, I'd rather see a "display panel" > approach where all the properties of the current component were shown > (and all available for direct editing). If this takes up too much > screen real-estate, we could drop back to showing one of a number of > subsets (basic, appearance, etc.) - but given that there relatively > few properties, I think this won't be a problem. I decided to tackle this - and was amazed to find how easy it was (or at least, seems to have been). In about 1-1/2 days I've go this up and running (as far as I can tell with the limited testing I've done so far). I don't know of any NEW bugs - but I've run into a few that all seem to be there in the released version (0.8.1 - not cvslatest). Before I go and look into these, I thought I'd just check to see if anyone else has seen these, or looked at them at all, or have any ideas/suggestions, or ... 1. Menu selection using Alt- sequences (WinXP) are flaky. Shortcuts always appear to work, as does the mouse - but sometimes the Alt-key sequences don't - the "primary" letters show as underlined, but other letters don't trigger any action that I can see. 2. Moving components using arrow keys is flaky. Usually it works, but after selecting some component types, the arrow keys stop working. Noticed this with Bitmap Canvases, and I *think* I've seen it with other components. Once they've stopped, it's hard to get them to work again but can be done most days. 3. Clicking on the "File..." button to specify a file name (for an Image or ImageButton) will fail unless the background has already been saved. (This seems to give a value of None to one of the path names, and hence cause an error in Pythoncard/util.relativepath). Any ideas ? Or should I start debugging these ? -- Alex Tweedly http://www.tweedly.net -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.10.2 - Release Date: 21/04/2005 |
From: Andy T. <an...@ha...> - 2005-04-29 12:46:46
|
Alex Tweedly wrote: > On Pythoncard-users, Alex Tweedly wrote: > >> >> C. Resource Editor >> >> (these are in descending order of importance to me, or increasing >> difficulty of implementation) >> >> 1. property editor window. >> I find the current property window pretty clunky. Instead of >> displaying (and allowing editing of) one property at a time, with a >> list to select which property, I'd rather see a "display panel" >> approach where all the properties of the current component were shown >> (and all available for direct editing). If this takes up too much >> screen real-estate, we could drop back to showing one of a number of >> subsets (basic, appearance, etc.) - but given that there relatively >> few properties, I think this won't be a problem. > > > I decided to tackle this - and was amazed to find how easy it was (or at > least, seems to have been). In about 1-1/2 days I've go this up and > running (as far as I can tell with the limited testing I've done so > far). I don't know of any NEW bugs - but I've run into a few that all > seem to be there in the released version (0.8.1 - not cvslatest). > If it's working for you I think you should check it into CVS. If you inadvertently introduce any serious bugs we can always back out your changes, that's the joy of version control. Regards, Andy -- -------------------------------------------------------------------------------- From the desk of Andrew J Todd esq - http://www.halfcooked.com/ |
From: Alex T. <al...@tw...> - 2005-04-29 14:03:59
|
Andy Todd wrote: > Alex Tweedly wrote: > >> I decided to tackle this - and was amazed to find how easy it was (or >> at least, seems to have been). In about 1-1/2 days I've go this up >> and running (as far as I can tell with the limited testing I've done >> so far). I don't know of any NEW bugs - but I've run into a few that >> all seem to be there in the released version (0.8.1 - not cvslatest). > > If it's working for you I think you should check it into CVS. If you > inadvertently introduce any serious bugs we can always back out your > changes, that's the joy of version control. Thanks Andy, but it is, IMHO, too big a behaviour change to check in without getting some agreement. I'm actually not (in this case) worried so much about a serious bug, but more about a serious surprise for users. I think this style is much better, though quite different - but I decided to give myself this week (i.e. until end of tonight, Friday) to work on it, then post to the users list to ask people to have a look and see what they think. Incidentally, I did get carried away .... so as well as the simple "panel display" change, it also has buttons for changing layers, moving the component (alternative to arrow-keys), and multiple component selection and manipulation as well. Don't yet have all the obvious manipulations; I've got move, align, distribute and equalize - haven't yet got delete, copy or re-layer - for multiple components. (I do have separate diffs so can commit only the panel changes if I need to). Anyway - look for a posting to the users list tonight with a version to take a look at. -- Alex Tweedly http://www.tweedly.net -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.10.4 - Release Date: 27/04/2005 |