Re: [SE2.0 beta] bugs and feature requests
Re: [SE2.0 beta] bugs and feature requests
- Subject: Re: [SE2.0 beta] bugs and feature requests
- From: Tim Bumgarner <email@hidden>
- Date: Mon, 13 Jan 2003 16:20:50 -0500
Hi Sander,
Comments below...
On Tuesday, January 7, 2003, at 08:40 AM, Sander Tekelenburg wrote:
[Is this the best place to send this? Or do the Chrisses, Sal, Tim
and/or
Cricket prefer direct email? (Since I have some feature requests, I
thought
this list would be apprpriate - allow others to squash my suggestions
;))]
This list is just fine.
- The Event Log is broken. When you have the results tab selected, run
a
script, switch to the Event Log, it shows you either nothing, or the
*previous* event log (from the last time you ran the script with the
Event
Log open). I noticed the "Log only when window is visible" option, but
switching that off doesn't affect this.
The reason for the "Log only when window is visible" item is that it
slows down the execution of a script when the event log has to be
generated, and by default this is on (meaning the log is not
generated), since we want the script to execute a quickly as possible.
The intention was that if this check box was on and the event log tab
wasn't visible that it would still generate the correct log. The
feature works correctly for the "Event Log History" window, but isn't
working correctly for the event log tab of the script window. So I'll
fix this, and perhaps re-word the check box in the preferences to "Log
only when window or tab is visible".
- How do you tell SE 2.0b to remember the default window size of a new
script
window?
Move and size the window (including the split window position and
active tab) to the way you like it and then choose "Save As Default"
from the Window menu. The next new window you create will then have the
same size properties (though it might get offset due to window tiling
of new documents).
- When saving a script, its window size/position is not saved.
This is a problem in that a compiled script (.scpt) is saved as
data-fork only and we aren't allowed to save anything in the resource
fork (where window positions are normally saved). I'm not going to get
into the politics of this decision, but we hope to have a solution for
this when SE 2 final ships that doesn't violate the resource for rule.
- Same for the "Open Dictionary" window. I think this should remember
its
previous state.
Agreed, but again it will have to be solved keeping the above in mind.
- SE 2.0b can't open its own dictionary... ;)
There was a bug that was fixed in AppleScript 1.9.1 for 10.2.3 that
fixed this problem, though it still happens to me occasionally,
especially if I have several different version of SE 2 lying around.
I'll look into this further. It seem to work reliably if I choose "Open
Dictionary..." and then browse to the actual location of SE 2 or drag
it's icon (from the Finder) onto itself.
- In the "Open Dictionary" window, how about allowing the user to type
the
first few letters of the app he's searching for? I think that would be
a nice
improvement.
This is an irritant of mine as well, and hopefully will be fixed soon.
The actual implementation of that dialog is using the data browser from
Carbon and apparently the fix needs to come from there (I could be
wrong about this but that's what I understand).
- How about better keyboard navigation through dictionary windows?
Currently,
you can use the arrow keys to scroll up and down and you can TAB from
the
left pane to the right. But you can't TAB back from the right pane to
the
left, and you can't open/close sections in the left pane with the
left/right
arrow keys. Would be very nice if that would be added.
It's true you can't tab back into the outline view (I'll see what i can
do about this), but you can use Command-Left Arrow and Command-Right
Arrow to expand collapse items in the outline view. I see that the
Finder supports both (Command and non-Command) left right arrow keys,
and I'll see what I can do about that.
- The Find dialog could do with a "start at top/from current position"
switch
and a "stop searching at end of script" checkbox.
We are trying to stay consistent with the find panels in other Apple
products, such as TextEdit, Mail, etc, but it's a good suggestion.
--
Sander Tekelenburg, <http://www.euronet.nl/~tekelenb/>
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.
Thanks for the feedback, it's really appreciated!
Tim Bumgarner
AppleScript Engineering
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.