[Chandler-dev] Last Alpha 3 bug needs a question answered: What
commands are active when a modeless dialog is active?
grant at osafoundation.org
Tue Jul 11 10:25:06 PDT 2006
On 10 Jul, 2006, at 17:52, John Anderson wrote:
> It seems like I have the last Alpha 3 bug to fix. Fortunately, it's
> pretty easy, but it does raise and interesting question that I need
> to answer before fixing the bug:
> Suppose you have a modeless dialog frontmost, i.e. on top of the
> Chandler window. Should commands other than those for the dialog be
> active, e.g. all the usual Chandler commands, or should only the
> commands appropriate for that dialog, e.g. cut/copy/paste be active.
> My personal opinion is that it's probably most convenient for the
> user to make all the commands active. However, that may lead to a
> situation where a modeless dialog might need to reflect changes
> from some Chandler command that happens while it's frontmost.
Making the commands active can also lead to situations where menu
items work, but behave in unexpected ways. i.e. there would now be
more configurations of the app's global state when the menu code runs.
More information about the chandler-dev