On Sat, 23 Jan 1999, Alexander Larsson verbalised:
> On 23 Jan, Lars Clausen wrote:
>> By using a registry based on the object type, we can keep it totally
>> seperate. I find that nicer. But again, if all objects have a menu, it
>> might go into the object. In either case, there should just be a
>> standard way to add the menu for an object.
> I vote for in the ObjectOps, se my other mail.
>
>> Arg! My control key is broken -- I have to keep control down to type
>> normally. Suns suck.
> Nah, sun:s are ok.
True, they're better than most machines. But all hardware sucks.
>> In both menus? Well, why not... possibly there could be a standard menu
>> that objects can then add their own stuff to?
>
> Or another idea. Why not have both in the right mouse-button menu.
> Separated by a separator. That's how Visio does it i think.
There are arguments both for and against:
One menu means you won't have to think about which menu an operation is in,
and people will see the operations when they see the right-button menu
(which most should be used to from Gimp).
Two menus means there will be a 'general' menu that you can get anywhere,
and a 'specific' menu that is based on the object. It also means that the
object operations will be more accessible, since there won't be as many
menu points to traverse. Also, we won't have to make the general menu know
about the clicked point, which is necessary for the object menu.
A separate problem is the keyboard shortcuts. Should the active object
determine which shortcuts are available? What about the click point?
We could have both, you know. Just append the object menu to the general
menu, but still bind it on the middle button. We would still have to
consider the click point for the general menu, though.
-Lars
--
Lars R. Clausen ([EMAIL PROTECTED])
A *real* smart bomb would call in sick, perhaps move to another country,
changing its name in the process, open a beach bar maybe and live out its
days in safe anonymity. -- Barry O'Neill in rhod
