Martin Vermeer wrote:
On Fri, 2006-02-24 at 12:45 +0100, Jean-Marc Lasgouttes wrote:
"Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
Martin> BTW Jean-Marc, this works, but would it perhaps be better to
Martin> make MathNestInset inherit (from InsetBase) and modify
Martin> covers(x,y)?
What is the idea BTW? That nestinsets have a margin around them? So it
depends why one uses covers() (real area covered vs. mouse accesible
area).
It seems to be only used (in text2 and nestinset) to detect whether the
mouse has hit it (and then respond accordingly). It is thus certainly
possible to have the "mouse sensitive area" differ from the drawn area
of the inset.
I only want an "inert zone" on the left edge of 2 pixels wide. Then, if
you click there, you will not descend into the inset, but the cursor
will end up -- on current slice depth -- on the inset's left side. That
solves the ")(" problem.
- Martin
This new patch is great, things are really becoming better!
It looks like it fixes all issues, it only needs a bit of fine-tuning. I
think the area that is currently 2 pixels should be larger. If possible,
it should be the complete area between the brackets. Currently you have
to click very close to ( in order to get cursor between ) and (.
The area could also overlap a bit with the left side of the ( bracket.
Try clicking between two ordinary characters, say a and b (ab). Clicking
on the left side of b still gets the cursor between a and b.
The same thing applies to clicking on the right side of the last
bracket. There are a few pixels between the bracket and the position
where you can click to get the mouse there. If the bracket is the last
part of the equation there is only about 1 pixel left to click on.
Joost
