On Fri, Aug 30, 2002 at 04:49:38PM +1000, Allan Rae wrote:
> > | > \bind "mouse-button-1" "cursor-set"
> > | > \global_inset_bind "mouse-button-1" "popup-dialog"
> > |
> > | Or maybe
> > |
> > | \localbind "insetname" "mouse-button-1" "popup-dialog"
> > |
> > | with "insetname" being the inset id
On 28 Aug 2002, Lars Gullik Bjønnes wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> | > \bind "mouse-button-1" "cursor-set"
> | > \global_inset_bind "mouse-button-1" "popup-dialog"
> |
> | Or maybe
> |
> | \localbind "insetname" "mouse-button-1" "popup-dialog"
> |
> | with "insetname" bei
Andre Poenitz <[EMAIL PROTECTED]> writes:
| > The binding between "mouse-button-1" and "popup-dialog" handle the
| > rest. But to do this we need some kind of context to the bindings.
|
| Right... we don't have that currently, though... So I'd suggest to use the
| mouse lfuns temporarily (the ne
On Wed, Aug 28, 2002 at 09:43:49AM +0200, Lars Gullik Bjønnes wrote:
> | \bind "mouse-button-1" "cursor-set"
> | \global_inset_bind "mouse-button-1" "popup-dialog"
>
> The problem is of course when and where to lookup the binding.
I am not sure. I'd postpone that until we are a bit closer...
An
On Wed, Aug 28, 2002 at 09:36:36AM +0200, Lars Gullik Bjønnes wrote:
> An inset should never want to popup a dialog on mouse-left, it should
> only popup a dialog on the LFUN "popup-dialog"
Understood.
> The binding between "mouse-button-1" and "popup-dialog" handle the
> rest. But to do this w
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| Andre Poenitz <[EMAIL PROTECTED]> writes:
|
| | On Wed, Aug 28, 2002 at 09:12:54AM +0200, Lars Gullik Bjønnes wrote:
| | > What I really want is for all dispatch to be really ignorant about
| | > mouse buttons. (and the rest of the code as well..
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Wed, Aug 28, 2002 at 09:12:54AM +0200, Lars Gullik Bjønnes wrote:
| > What I really want is for all dispatch to be really ignorant about
| > mouse buttons. (and the rest of the code as well...)
|
| So how should an inset describe that it wants to po
On Wed, Aug 28, 2002 at 09:12:54AM +0200, Lars Gullik Bjønnes wrote:
> What I really want is for all dispatch to be really ignorant about
> mouse buttons. (and the rest of the code as well...)
So how should an inset describe that it wants to popup a dialog on
mouse-left?
Andre'
--
Those who de
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Wed, Aug 28, 2002 at 08:38:39AM +0200, Lars Gullik Bjønnes wrote:
| > Not too bad. But I feel that the switch/cases are a bit too big and
| > really should be kept in separate functions.
|
| I said I'll move them down to LyXText (which will make the
On Wed, Aug 28, 2002 at 08:38:39AM +0200, Lars Gullik Bjønnes wrote:
> Not too bad. But I feel that the switch/cases are a bit too big and
> really should be kept in separate functions.
I said I'll move them down to LyXText (which will make them slimmer).
If they are still big than, I'll put them
Andre Poenitz <[EMAIL PROTECTED]> writes:
| This patch makes the work areas (both xforms and qt2) producing directly
| FuncRequests for the mouse clicks. For the double and triple clicks I've
| introduced new lfuns LFUN_MOUSE_DOUBLE and LFUN_MOUSE_TRIPLE (which btw
| would enable insets to handle
This patch makes the work areas (both xforms and qt2) producing directly
FuncRequests for the mouse clicks. For the double and triple clicks I've
introduced new lfuns LFUN_MOUSE_DOUBLE and LFUN_MOUSE_TRIPLE (which btw
would enable insets to handle them, for mathed there is a bug on bugzilla
pendi
12 matches
Mail list logo
