This happens with Copy&Paste:
1) Create a note
2) Collapse it
3) Place the mouse cursor over the inset button.
4) Select the inset with the keyboard
5) type Ctrl-v immediately followed by Ctrl-v. The note inset is then
replaced by its own copy.
6) move the inset out of the inset
I find a simple
This happens with Copy&Paste:
1) Create a note
2) Collapse it
3) Place the mouse cursor over the inset button.
4) Select the inset with the keyboard
5) type Ctrl-v immediately followed by Ctrl-v. The note inset is then
replaced by its own copy.
6) move the inset out of the inset
This is somehow
Bo Peng wrote:
There is an easy crash to reproduce though with mouse-hover when you
pass on top of the first Note with the mouse. The crash happens at line
1073 of BufferView.C because last_inset points to invalid memory...
Bo, I guess this is for you ;-)
I can not reproduce it. Could you ple
> * insert->note->lyx note, enter a few chars, collapse the note. Copy the note
> several times (three lines?), use mouse to select. Lyx crashes with
>
> Assertion triggered in void lyx::LyXText::dispatch(lyx::LCursor&, lyx::FuncRequest&)
by failing check "cur.text() == this" in file src/text
Peter Kümmel wrote:
* insert->note->lyx note, enter a few chars, collapse the note. Copy the note
several times (three lines?), use mouse to select. Lyx crashes with
Assertion triggered in void lyx::LyXText::dispatch(lyx::LCursor&, lyx::FuncRequest&) by
failing check "cur.text() == this" in
Abdelrazak Younes wrote:
> Enrico Forestieri wrote:
>> Latest svn. Load any sufficiently long document and scroll it down and up
>> using the arrow keys. Sooner than later LyX asserts. I get two different
>> assertions:
>>
>> Assertion triggered in lyx::Point lyx::CoordCache::get(const
>> lyx::LyXT
Enrico Forestieri wrote:
Latest svn. Load any sufficiently long document and scroll it down and up
using the arrow keys. Sooner than later LyX asserts. I get two different
assertions:
Assertion triggered in lyx::Point lyx::CoordCache::get(const lyx::LyXText*, lyx::pit_type)
const by failing che
Enrico Forestieri wrote:
Latest svn. Load any sufficiently long document and scroll it down and up
using the arrow keys. Sooner than later LyX asserts. I get two different
assertions:
Assertion triggered in lyx::Point lyx::CoordCache::get(const lyx::LyXText*, lyx::pit_type)
const by failing che
Latest svn. Load any sufficiently long document and scroll it down and up
using the arrow keys. Sooner than later LyX asserts. I get two different
assertions:
Assertion triggered in lyx::Point lyx::CoordCache::get(const lyx::LyXText*,
lyx::pit_type) const by failing check "posit != it->second.end
On Thu, Apr 07, 2005 at 05:10:48PM +0300, Martin Vermeer wrote:
> > I know I am repeating myself, but we should understand the
> > LFUN_FINISHED stuff before doing that. Either it makes sense and we
> > should fix it, or it does not, and we should remove it completely.
The main purpose of the LFUN
On Wed, Apr 06, 2005 at 06:09:10PM +0200, Jean-Marc Lasgouttes wrote:
> > "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
>
> Martin> Nice, those small attachments ;-/
>
> case LFUN_UPSEL:
> case LFUN_UP:
> + if (cur.inMacroMode()) break;
> cur.sel
On Thu, Apr 07, 2005 at 11:36:22AM +0200, Helge Hafting wrote:
> Apparently, there are fundamental differences between
> going up/down and left/right.
Up/down is mainly 'visual by coordinate', left/right 'by structure'.
There are exceptions when following these base rules is 'obviously'
wrong. Up/
On Wed, Apr 06, 2005 at 06:51:22PM +0300, Martin Vermeer wrote:
> OK, here's a patch for this one. The problem is an unfinished math macro
> is already defined as an inset, but hasn't drawn + added a coordinate
> cache entry yet. So it now tests for macro mode and does nothing then.
There is at mo
On Fri, 2005-04-08 at 15:05, Jean-Marc Lasgouttes wrote:
> > "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
>
> Martin> On Thu, Apr 07, 2005 at 03:58:00PM +0200, Jean-Marc Lasgouttes
> Martin> wrote:
> >> I know I am repeating myself, but we should understand the
> >> LFUN_FINISHED st
> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
Martin> On Thu, Apr 07, 2005 at 03:58:00PM +0200, Jean-Marc Lasgouttes
Martin> wrote:
>> I know I am repeating myself, but we should understand the
>> LFUN_FINISHED stuff before doing that. Either it makes sense and we
>> should fix it,
Martin Vermeer wrote:
>> Ideally, the first arrow down/up should move the cursor,
>> not merely close the macro. I guess that is much harder to do?
>
> Yes, I didn't manage that. The problem seems to be that we have to first
> force a redraw/setPosCache after closing the macro, before we are
> a
On Fri, 2005-04-08 at 11:11, Helge Hafting wrote:
> Martin Vermeer wrote:
...
> >This is the part that is unrelated to LFUN_FINISHED: it fixes
> >Helge's bug and does nothing else. It's a crashing bug and this is the
> >correct fix IMHO*). Agreed?
> >
> >
> This works fine. No more crash when
Martin Vermeer wrote:
On Thu, Apr 07, 2005 at 03:58:00PM +0200, Jean-Marc Lasgouttes wrote:
"Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
Martin> Here is the patch fixing Helge's unfinished macro up/down bug,
Martin> as well as making the cursor move properly for HOME/END
On Thu, Apr 07, 2005 at 03:58:00PM +0200, Jean-Marc Lasgouttes wrote:
> > "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
>
> Martin> Here is the patch fixing Helge's unfinished macro up/down bug,
> Martin> as well as making the cursor move properly for HOME/END. Also
> Martin> a slight
On Thu, Apr 07, 2005 at 03:58:00PM +0200, Jean-Marc Lasgouttes wrote:
> > "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
>
> Martin> Here is the patch fixing Helge's unfinished macro up/down bug,
> Martin> as well as making the cursor move properly for HOME/END. Also
> Martin> a slight
> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
Martin> Here is the patch fixing Helge's unfinished macro up/down bug,
Martin> as well as making the cursor move properly for HOME/END. Also
Martin> a slight simplification/dead code removal.
Martin> Unfortunately I didn't get Page Up/D
Here is the patch fixing Helge's unfinished macro up/down bug, as well as
making the
cursor move properly for HOME/END. Also a slight simplification/dead code
removal.
Unfortunately I didn't get Page Up/Down to behave, so I left that part out.
OK to commit? Works for me.
- Martin
Index: Cha
On Thu, Apr 07, 2005 at 11:36:22AM +0200, Helge Hafting wrote:
> Martin Vermeer wrote:
...
> >Just give it a try anyway ;-)
> >
> >
> Did that.
> The crash is gone, and replaced with inconvenience. ;-)
> I can now type in math latex like \bmod, and if I
> press down while it is still red, nothi
Martin Vermeer wrote:
This did not apply to yesterday's CVS (plus those
patches for paranthesis issues.)
Two hunks would apply with offsets, two were rejected.
Probably because they were already in. You could check for that.
Ok, they were in already. :-)
Just give it a try anyway ;-)
Did
Martin Vermeer wrote:
> On Wed, Apr 06, 2005 at 06:09:10PM +0200, Jean-Marc Lasgouttes wrote:
>> Why don't you use cur.macroModeClose() as for LFUN_LEFT/RIGHT?
>>
>> JMarc
>
> I tried that; didn't do the trick :-(
> Neither did cur.clearTargetX() by the way.
Could you please add a FIXME comment
On Thu, Apr 07, 2005 at 09:50:48AM +0200, Helge Hafting wrote:
> Martin Vermeer wrote:
>
> >
> >>OK, here's a patch for this one. The problem is an unfinished math macro
> >>is already defined as an inset, but hasn't drawn + added a coordinate
> >>cache entry yet. So it now tests for macro mode an
Martin Vermeer wrote:
OK, here's a patch for this one. The problem is an unfinished math macro
is already defined as an inset, but hasn't drawn + added a coordinate
cache entry yet. So it now tests for macro mode and does nothing then.
(Were there any other keys that did this?)
This contains the n
On Wed, Apr 06, 2005 at 06:09:10PM +0200, Jean-Marc Lasgouttes wrote:
> > "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
>
> Martin> Nice, those small attachments ;-/
>
> case LFUN_UPSEL:
> case LFUN_UP:
> + if (cur.inMacroMode()) break;
> cur.sel
On Wed, Apr 06, 2005 at 06:03:02PM +0200, Georg Baum wrote:
> Martin Vermeer wrote:
>
> > OK, here's a patch for this one. The problem is an unfinished math macro
> > is already defined as an inset, but hasn't drawn + added a coordinate
> > cache entry yet. So it now tests for macro mode and does
Jean-Marc Lasgouttes wrote:
> Why don't you use cur.macroModeClose() as for LFUN_LEFT/RIGHT?
I think that that would be the correct fix, but I suspect (untested) that
macroModeClose() invalidates the coord cache, because it removes the
unfinished inset and inserts a new one. But if this is the ca
Martin Vermeer wrote:
> OK, here's a patch for this one. The problem is an unfinished math macro
> is already defined as an inset, but hasn't drawn + added a coordinate
> cache entry yet. So it now tests for macro mode and does nothing then.
>
> (Were there any other keys that did this?)
What do
> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
Martin> Nice, those small attachments ;-/
case LFUN_UPSEL:
case LFUN_UP:
+ if (cur.inMacroMode()) break;
cur.selHandle(cmd.action == LFUN_UPSEL);
if (!cur.up())
On Wed, 2005-04-06 at 18:51, Martin Vermeer wrote:
> On Wed, 2005-04-06 at 10:15, Martin Vermeer wrote:
> > On Tue, Apr 05, 2005 at 11:03:19PM +0200, Helge Hafting wrote:
> > > Move into a math inset.
> > > Type \bmod
> > > It will show as red text. Press down arrow while it still is red,
> > > a
On Wed, 2005-04-06 at 10:15, Martin Vermeer wrote:
> On Tue, Apr 05, 2005 at 11:03:19PM +0200, Helge Hafting wrote:
> > Move into a math inset.
> > Type \bmod
> > It will show as red text. Press down arrow while it still is red,
> > and lyx crashes with the usual emergency save.
> >
> > Pressing
On Wed, Nov 27, 2002 at 01:54:46PM +0100, Andre Poenitz wrote:
> The "big change" is to let 'setCursorFromCoordinates' descent into insets.
> The necessary code was already present in the handler for LFUN_DOWN, but
> not used by e.g. LFUN_NEXT. So apart from removing code that I did not
> understa
On Wed, Nov 27, 2002 at 06:11:38PM +0100, Lars Gullik Bjønnes wrote:
> So in present state this patch does not improve anything.
>
We should spend some time seeing if we can get it to work though, this
would solve a large number of serious problems. I'll see if I can look
at it ...
regards
john
Andre Poenitz <[EMAIL PROTECTED]> writes:
| The following patch seems to provide a smoother Cursor/Page up/down
| than we currently have.
I just tested it.
Continues page-down flashes between beginnign of document and where
the corsor is supposed to be.
When the cursor enters an inset it is una
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Wed, Nov 27, 2002 at 03:51:53PM +0100, Andre' Poenitz wrote:
>> And now please: What about actually testing the patch?
>
| Ok, forget about the patch.
why?
--
Lgb
Angus Leeming <[EMAIL PROTECTED]> writes:
| On Wednesday 27 November 2002 2:52 pm, Lars Gullik Bjønnes wrote:
>> Andre Poenitz <[EMAIL PROTECTED]> writes:
>> | On Wed, Nov 27, 2002 at 01:59:45PM +, Angus Leeming wrote:
>> >> This is inconsistent, would't compile on my box and will have Lars
>>
On Wednesday 27 November 2002 2:52 pm, Lars Gullik Bjønnes wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
> | On Wed, Nov 27, 2002 at 01:59:45PM +, Angus Leeming wrote:
> >> This is inconsistent, would't compile on my box and will have Lars
> >> jumping up and down crying "don't pass const
On Wed, Nov 27, 2002 at 03:51:53PM +0100, Andre' Poenitz wrote:
> And now please: What about actually testing the patch?
Ok, forget about the patch.
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)
On Wed, Nov 27, 2002 at 03:52:31PM +0100, Lars Gullik Bjønnes wrote:
> const on pod types in signatures have no meaning.
I know.
But they have a meaning in the .C, namely raising compiler errors when one
tries to change them.
> So better to leave them out.
I ran into a function that modified t
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Wed, Nov 27, 2002 at 01:59:45PM +, Angus Leeming wrote:
>> This is inconsistent, would't compile on my box and will have Lars jumping up
>> and down crying "don't pass const int". For reasons I've yet to fathom.
>
| And actually I doubt Lars will
On Wed, Nov 27, 2002 at 01:59:45PM +, Angus Leeming wrote:
> This is inconsistent, would't compile on my box and will have Lars jumping up
> and down crying "don't pass const int". For reasons I've yet to fathom.
And actually I doubt Lars will jump as it adds modern cruft ("const" is not
even
On Wed, Nov 27, 2002 at 01:59:45PM +, Angus Leeming wrote:
> This is inconsistent, would't compile on my box
That's funny, because it should.
> and will have Lars jumping up
> and down crying "don't pass const int". For reasons I've yet to fathom.
> +++ lyxtext.h 27 Nov 2002 12:43:43 -
>
On Wednesday 27 November 2002 12:54 pm, Andre Poenitz wrote:
> The following patch seems to provide a smoother Cursor/Page up/down
> than we currently have.
>
> As it is fairly intrusive (over 100 lines removed) I would not mind if
> someone else had a look.
This is inconsistent, would't compile o
The following patch seems to provide a smoother Cursor/Page up/down
than we currently have.
As it is fairly intrusive (over 100 lines removed) I would not mind if
someone else had a look.
The "big change" is to let 'setCursorFromCoordinates' descent into insets.
The necessary code was already pr
On Tue, Apr 23, 2002 at 06:49:04PM +0200, Asger K. Alstrup Nielsen wrote:
> Agreed. My experience after using Bugzilla intensively for two years
> is that you should relentlessly use WONTFIX, INVALID when you decide
> that it's not beneficial to fix it for the next release.
Nooo, please let's no
On Mon, 22 Apr 2002, John Levon wrote:
> On Mon, Apr 22, 2002 at 05:28:21PM +0300, Eran Tromer wrote:
>
> > A naive question of Bugzilla policy -- if this is an acknowledged by all
> > as a problematic issue, why mark it WONTFIX as opposed to setting a
> > far-away milestone or something? Definit
On Mon, Apr 22, 2002 at 05:28:21PM +0300, Eran Tromer wrote:
> A naive question of Bugzilla policy -- if this is an acknowledged by all
> as a problematic issue, why mark it WONTFIX as opposed to setting a
> far-away milestone or something? Definitely not 1.2.x stuff, but you do
> want it addr
On Mon, Apr 22, 2002 at 05:01:12PM +0200, Juergen Vigna wrote:
> Well in a certain mode we do this already, we draw it so many times until
> we got all metrics ready and this can be a multiple step and it can take
> more than 1 go to get it right depending on the nesting level. Look that
> in diff
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> On Mon, Apr 22, 2002 at 04:42:08PM +0200, Juergen Vigna wrote:
>> > BTW, did you notice how LyX gets horribly slow when you create
>> comments > that are nested 15 levels deep?
>>
>> We have to do too much update calls the more ne
On 22-Apr-2002 Andre Poenitz wrote:
> Did I mention "drawing in two phases: one for metrics computation and one
> for the actual drawing" lately?
Well in a certain mode we do this already, we draw it so many times until
we got all metrics ready and this can be a multiple step and it can take
mo
On Mon, Apr 22, 2002 at 04:42:08PM +0200, Juergen Vigna wrote:
> > BTW, did you notice how LyX gets horribly slow when you create comments
> > that are nested 15 levels deep?
>
> We have to do too much update calls the more nesting we get because we
> can never be sure what our child did.
Did I
On 22-Apr-2002 Eran Tromer wrote:
> A naive question of Bugzilla policy -- if this is an acknowledged by all
> as a problematic issue, why mark it WONTFIX as opposed to setting a
> far-away milestone or something? Definitely not 1.2.x stuff, but you do
> want it addressed *sometime* by *someo
> "Eran" == Eran Tromer <[EMAIL PROTECTED]> writes:
Eran> BTW, did you notice how LyX gets horribly slow when you create
Eran> comments that are nested 15 levels deep?
I see why this may happen. But do you really want to do that?
JMarc
Juergen Vigna wrote:
> On 22-Apr-2002 Eran Tromer wrote:
> Now in this special case you don't have a row below the inset so it just
> stays there. But IMO this is the right thing to do, so you just can go
> on editing from that spot on.
Ah. If it happens only this case then ignoring it is fine b
On 22-Apr-2002 Andre Poenitz wrote:
> On Mon, Apr 22, 2002 at 12:31:16PM +0200, Juergen Vigna wrote:
>> I may agree on this with you. The problem is that we cannot fix this and
>> it is REALLY a very special case, isn't it? The problem is that the inset
>> wants to go down sees there is no row be
orms and I can assure
you, you don't want to see the rest. I believe there is no "one size fits
all solution" regarding cursor up/down and even if there were some close
approximation of it (e.g. by using some "clever" combination of logical
and visual movement), implementi
On Mon, Apr 22, 2002 at 12:31:16PM +0200, Juergen Vigna wrote:
> Hope you understand now that this is REALLY a minor annoyance in a VERY
> certain situation, which, in your case, is VERY theoretical, isn't it?
My tuppenny's: I agree with both of you. From the user's point of view
this is a (very
On 22-Apr-2002 Eran Tromer wrote:
> Anyway, at least now we're in sync: the criterion is strictly visual, to
> the level of single pixels. Got it. Please allow me to try your patience
> and go back to the original example (ERT in footnote).
#:O)
> >>Cursor at beginning of footnote (right be
Juergen Vigna wrote:
> On 19-Apr-2002 Eran Tromer wrote:
>
>>(Note: the old screenshot was inaccurate, since I faked the cursor (it
>>wasn't captured) just to show where I'm putting it logically. I've now
>>updated the screenshow to be perfectly accurate.)
>>
>>The inset is one line below and 1
On 19-Apr-2002 Eran Tromer wrote:
> (Note: the old screenshot was inaccurate, since I faked the cursor (it
> wasn't captured) just to show where I'm putting it logically. I've now
> updated the screenshow to be perfectly accurate.)
>
> The inset is one line below and 1 pixel to the right of t
John Levon wrote:
> On Fri, Apr 19, 2002 at 11:34:24PM +0300, Eran Tromer wrote:
http://dl.tromer.org/nested.png
>>>
>>This prefers logical behavior to visual behavior, in contradiction to
>>what you said earlier. Visually, the thing directly below the cursor is
>>the inset, so if you want v
On Fri, Apr 19, 2002 at 11:34:24PM +0300, Eran Tromer wrote:
> >> http://dl.tromer.org/nested.png
>
> This prefers logical behavior to visual behavior, in contradiction to
> what you said earlier. Visually, the thing directly below the cursor is
> the inset, so if you want visual behavior then
John Levon wrote:
> On Fri, Apr 19, 2002 at 10:24:15PM +0300, Eran Tromer wrote:
>
>
>>We're missing something. Here's what I see with current CVS:
>> http://dl.tromer.org/nested.png
>>Since the footnote inset is the only thing visually below the cursor, I
>>would expect to go there.
>>
>
>
On Fri, Apr 19, 2002 at 10:24:15PM +0300, Eran Tromer wrote:
> We're missing something. Here's what I see with current CVS:
> http://dl.tromer.org/nested.png
> Since the footnote inset is the only thing visually below the cursor, I
> would expect to go there.
>
Down should move down to the
Juergen Vigna wrote:
> It's easier to discuss this on lyx-devel so I go for that way.
>
>>As before, in a new document create a footnote and within it an ERT inset.
>>Don't enter any text.
>>
>>Cursor right before footnote:
>> does nothing, should enter footnote
>
> Why you are at the left of
On Fri, Apr 19, 2002 at 04:46:09PM +0200, Juergen Vigna wrote:
> > As before, in a new document create a footnote and within it an ERT inset.
> > Don't enter any text.
> >
> > Cursor right before footnote:
> >does nothing, should enter footnote
>
> Why you are at the left of the footnote an
It's easier to discuss this on lyx-devel so I go for that way.
> As before, in a new document create a footnote and within it an ERT inset.
> Don't enter any text.
>
> Cursor right before footnote:
>does nothing, should enter footnote
Why you are at the left of the footnote and press DOWN w
> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> Everyone: what bugs need fixing for 1.2 ? the .eps thing in user
John> dirs must be fixed IMHO and it would be nice if Jug could fix
John> the small table update problems (polish thing ...)
The problem with the .eps thing is that it pr
On Fri, Apr 19, 2002 at 05:16:18AM +0300, Eran Tromer wrote:
> In a new document, create an ERT inset inside a footnote inset.
> Watch how and misbehave in each of the four possible cursor
> locations.
Yes, that is an interesting set of events ;)
> By the way, should I report bugs here or di
Bug in current CVS:
In a new document, create an ERT inset inside a footnote inset.
Watch how and misbehave in each of the four possible cursor
locations.
By the way, should I report bugs here or directly into Bugzilla?
Regards,
Eran Tromer
The "prototype for mathed" that I mentioned earlier today looks well enough
to serve as "final" solution for mathed...
Just try moving up/down in nested arrays...
Andre'
--
André Pönitz .. [EMAIL PROTECTED]
74 matches
Mail list logo
