Richard Heck wrote:
Here's another idea. Basically, what I've done is added an optional
"setFont" argument to editXY
I thought about that yesterday and i assume it to be the fastest solution for now - but i agree that
it is not very nice:
Anyway, it can be made pretty later.
other ways i can imagine for a solution:
- split editXY in a method that only searches for the inset (checkInsetHit()?) and another that does
the modifications.
- store the font information in the cursor (as suggested in a comment anywhere
in the code)
Comments?
Bernhard
