On 24-Apr-2002 Andre Poenitz wrote:
> That's kind of you.
#:O)
> But what is the additional 'if !mathcursor' in 'case 1' good for?
>
> If we click in an inset for the very first time, we need to create the
> cursor. Or is this done in the edit() call?
>
> As I said, I am lost...
What do you drink in the morning instead of coffee or tea? :P
I told you in my former mail that when calling insetButtonPress the
edit() call is NOT called anymore (for HiglyEditableInsets!), but
(and maybe I forgot about that) only bv->lockInset(inset, false) is
called to lock the inset. So you have to assure in the insetButtonPress
call that you ARE "internally" locked and it seemed to me that mathed
knows it is locked if mathcursor != 0, did I assume wrong?
Jug
--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Dr. Jürgen Vigna E-Mail: [EMAIL PROTECTED]
Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253
I-39100 Bozen Web: http://www.sad.it/~jug
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Fundamentally, there may be no basis for anything.
