On 26-Oct-98 Asger K. Alstrup Nielsen wrote:
>> Asger> This last bit can be solved using signals. However, we can
>> Asger> also just use the simpler solution: When we define the toolbar,
>> Asger> we also define which LyXFunc to trigger when the button is
>> Asger> pressed. I.e. this action question is a property of each
>> Asger> individual button.
>>
>> This is what we have now, and I see indeed no reason to change
>> that. Each button has a pseudoaction attached.
>
>Rather than the pseudo-action, I propose that we simply use the command.
>This will make the stuff for the drop-down list simpler.
As one who worked on the read-only buffer protection for 0.12, I have a
warning: We should be careful about using commands directly from the
toolbar. Currently, read-only buffer protection is provided centrally by
Dispatch. Calling functions directly from the toolbar would force us to
distribute this protection to every function that can possibly be
attached to a button. Depending on exactly how the kernel turns out,
this might be easy or very, very painful.
For this reason, my vote is to use pseudo-actions, including for
drop-down lists.
Carl
----------------------------------
Carl Ollivier-Gooch [EMAIL PROTECTED]
Department of Mechanical Engineering Voice: +1-604-822-1854
University of British Columbia Fax: +1-604-822-2403
2324 Main Mall URL: http://www.mech.ubc.ca/~cfog
Vancouver, BC V6T 1Z4 Canada
----------------------------------
