Angus Leeming wrote:
> Also, if you enter using the keyboard arrow keys, then the cursor is
> displayed elsewhere, even though the inset is 'active'. Typing new
> stuff into the inset works fine.
>
> This is current cvs, including Andre's 1 line change to
> math_scriptinset.C.
This seems to be c
Andre Poenitz wrote:
> Fix the macro stuff for good.
>
> The macro stuff is (a) cool, (b) conceptionally broken since day
> one, (c) broken in current CVS.
My take on this: good! I do think that this is the right time to fix
the math macros correctly. As you say, they are currently broken
anyway.
On Wed, Apr 07, 2004 at 07:51:52PM +0200, Alfredo Braunstein wrote:
> Andre Poenitz wrote:
>
> > On Wed, Apr 07, 2004 at 02:18:38PM +0100, Angus Leeming wrote:
> >> Also, if you enter using the keyboard arrow keys, then the cursor is
> >> displayed elsewhere,
> >
> > I don't see this 'elsewhere'
Andre Poenitz wrote:
> On Wed, Apr 07, 2004 at 02:18:38PM +0100, Angus Leeming wrote:
>> Also, if you enter using the keyboard arrow keys, then the cursor is
>> displayed elsewhere,
>
> I don't see this 'elsewhere' except for macros which still are broken.
>
> Alfredo: Would you think we could a
On Wed, Apr 07, 2004 at 04:12:20PM +0100, Angus Leeming wrote:
> Angus Leeming wrote:
> > Also, if you enter using the keyboard arrow keys, then the cursor is
> > displayed elsewhere, even though the inset is 'active'. Typing new
> > stuff into the inset works fine.
>
> Ok, Andre's latest patch pa
Andre Poenitz wrote:
>> Also, if you enter using the keyboard arrow keys, then the cursor
>> is displayed elsewhere,
> I don't see this 'elsewhere' except for macros which still are
> broken.
No, you've fixed this. What is broken is entering a math inset with a
mouse press.
--
Angus
On Wed, Apr 07, 2004 at 02:18:38PM +0100, Angus Leeming wrote:
> Also, if you enter using the keyboard arrow keys, then the cursor is
> displayed elsewhere,
I don't see this 'elsewhere' except for macros which still are broken.
Alfredo: Would you think we could afford a traversal of the whole
do
Angus Leeming wrote:
> Also, if you enter using the keyboard arrow keys, then the cursor is
> displayed elsewhere, even though the inset is 'active'. Typing new
> stuff into the inset works fine.
Ok, Andre's latest patch partially cured this. The cursor is now
displayed at the expected position w