Russ Woodroofe wrote:
ATTACHMENTS:
Patch against 1.5.4
Patch against 'trunk' as downloaded Mar 22, 2008
Paul, could you have a look at these patches, please?
Thanks,
Jürgen
Michal Skrzypek wrote:
I wanted to report something relatively harmless, but strange. I am
currently using LyX 1.5.2 (XP SP2, Polish version). I apologize that I
cannot check this with the current version, but for now I cannot
upgrade/test it due to time constraints, as I am nearing the
Here are some changes that enlarge the possibilities to alter inset settings
via context menus.
Similar menus should be implemented for boxes, notes and friends, and for
citations (but there, things are a bit more complex due to the specifics of
the cite engines).
Comments?
Jürgen
Index:
bpeng wrote:
+ case LFUN_EXTERNAL_EDIT: {
+ FuncRequest fr(cmd);
+ InsetExternal * inset =
getInsetByCodeInsetExternal(d-cursor_,
+ EXTERNAL_CODE);
+ if (inset)
+ inset-dispatch(d-cursor_, fr);
+
rgheck wrote:
It certainly does at the moment, but that's at least in part because
there's a general problem with the dispatch mechanism in BufferView.
Well, the behaviour was introduced _intentionally_ (somewhere in the 1.5
cycle, IIRC).
Jürgen
Les Sharpe wrote:
Good Morning All,
Not sure who can best advise me so I am sending to both suggested
addresses.
I cannot get past the first example/test in the Tutorial (2.1.1 et
seq). I type in the suggested sentence and whether I hit the view -
dvi item in the drop down menu or the
Bo Peng wrote:
Note that the mysterious listings setting crash is still there
Can you remind me how to reproduce this?
rh
Jürgen Spitzmüller wrote:
Here are some changes that enlarge the possibilities to alter inset settings
via context menus.
Similar menus should be implemented for boxes, notes and friends, and for
citations (but there, things are a bit more complex due to the specifics of
the cite engines).
Jürgen Spitzmüller wrote:
rgheck wrote:
It certainly does at the moment, but that's at least in part because
there's a general problem with the dispatch mechanism in BufferView.
Well, the behaviour was introduced _intentionally_ (somewhere in the 1.5
cycle, IIRC).
Which behavior
rgheck wrote:
Which behavior do you mean?
Opening Editable (not HIGHLY_EDITABLE) inset's dialog with C-i.
My puzzlement concerns why Ctrl-I works to
collapse (say) ERT that the cursor is inside in 1.5 but not in current
trunk.
Ah, then we are talking about different issues.
Jürgen
rgheck wrote:
Right. These menus will have to be dynamically generated somehow, given
information about the cite engine. But that shouldn't be too terribly
bad. We do that kind of thing in so many cases.
Yes, this is what I had in mind as well.
Comments?
Yes. This is excellent. I
Jürgen Spitzmüller wrote:
rgheck wrote:
Which behavior do you mean?
Opening Editable (not HIGHLY_EDITABLE) inset's dialog with C-i.
My puzzlement concerns why Ctrl-I works to
collapse (say) ERT that the cursor is inside in 1.5 but not in current
trunk.
Ah, then we are
On Mon, Mar 24, 2008 at 7:21 AM, rgheck [EMAIL PROTECTED] wrote:
Bo Peng wrote:
Note that the mysterious listings setting crash is still there
Can you remind me how to reproduce this?
Open a document with a listings inset, right click, settings. Most of
the time, lyx will crash
Bo Peng wrote:
On Mon, Mar 24, 2008 at 7:21 AM, rgheck [EMAIL PROTECTED] wrote:
Bo Peng wrote:
Note that the mysterious listings setting crash is still there
Can you remind me how to reproduce this?
Open a document with a listings inset, right click, settings. Most of
the
rgheck wrote:
Open a document with a listings inset, right click, settings. Most of
the time, lyx will crash here (Linux, RHEL4, gcc 4.1, qt 4.22)
Weird.
FWIW, I see this too:
http://bugzilla.lyx.org/show_bug.cgi?id=4607
Jürgen
spitz wrote:
+#
+# InsetNote context menu
+#
+
+ Menu context-note
+ Submenu Change Type|y edit_notetype
+ Item Settings...|S inset-settings note
+ End
+
+ Menu edit_notetype
+ Item LyX Note|N next-inset-modify note Note Note
On Mon, Mar 24, 2008 at 9:13 AM, Jürgen Spitzmüller
[EMAIL PROTECTED] wrote:
rgheck wrote:
Open a document with a listings inset, right click, settings. Most of
the time, lyx will crash here (Linux, RHEL4, gcc 4.1, qt 4.22)
FWIW, I see this too:
Author: spitz
Date: Mon Mar 24 15:12:19 2008
New Revision: 23923
URL: http://www.lyx.org/trac/changeset/23923
Log:
* src/BufferView.cpp:
* src/Text3.cpp:
- fix LFUN_INSET_SETTINGS so that it also works at cursor position.
* LyXAction.cpp:
- doxy.
/*!
* \var
[EMAIL PROTECTED] wrote:
I'm for the KISS approach here, but would also like to suggest that we
use some version of the wiki engine with a CMS extension. There are many
users that have taken this particular wiki engine and used it as a CMS.
The advantage is that I can help with setting it up,
Pavel Sanda wrote:
e.g inset-settings inside ert does nothing for me.
because there's no more ERT dialog?
also i would ask if this lfun shouldn't be used for uncollapsable insets?
it will make much more sense than next-inset-toggle.
I would rather let inset-settings call next-inset-toggle,
On Mon, Mar 24, 2008 at 9:12 AM, [EMAIL PROTECTED] wrote:
Author: spitz
Date: Mon Mar 24 15:12:19 2008
New Revision: 23923
URL: http://www.lyx.org/trac/changeset/23923
Log:
* src/BufferView.cpp:
* src/Text3.cpp:
- fix LFUN_INSET_SETTINGS so that it also works at cursor
An integration of the main site and the wiki is a great idea. If the wiki
functions are hidden for the official content and only shown when an
authenticated user is logged in, it still looks professional and not too
much like a wiki.
then you have problem that many pages in wiki which are
Pavel Sanda wrote:
e.g inset-settings inside ert does nothing for me.
because there's no more ERT dialog?
yes, the doxy is wrong. anyway it doesn't work for note either.
also i would ask if this lfun shouldn't be used for uncollapsable insets?
it will make much more sense than
Bo Peng wrote:
Do we really need this
Yes. Try to open the Listings (or any other collapsable) dialog via context
menu by pressing on the button: it is disabled (without my change). It is
only enabled if you pressed _inside_ the collapsable.
since we can use LFUN_NEXT_INSET_TOGGLE for the
Pavel Sanda wrote:
An integration of the main site and the wiki is a great idea. If the wiki
functions are hidden for the official content and only shown when an
authenticated user is logged in, it still looks professional and not too
much like a wiki.
then you have problem that many pages
In my opinion the current wiki content should be something like a separate
community section, not a part of the official web. But I think using the
yes.
I only wanted to say that we should keep it this way for the new wiki CMS
accounts.
yes, it may be that wiki way of changing things on
Pavel Sanda wrote:
because there's no more ERT dialog?
yes, the doxy is wrong. anyway it doesn't work for note either.
The documentation was wrong.
BTW the ERT dialog is also superseded by the context menu.
Jürgen
Bo Peng wrote:
On Mon, Mar 24, 2008 at 9:13 AM, Jürgen Spitzmüller
[EMAIL PROTECTED] wrote:
rgheck wrote:
Open a document with a listings inset, right click, settings. Most of
the time, lyx will crash here (Linux, RHEL4, gcc 4.1, qt 4.22)
FWIW, I see this too:
Joost Verburg wrote:
Joost Verburg wrote:
Abdelrazak Younes wrote:
FYI, I implemented just that before 1.5.0 and part of the code is
still there commented out. Unfortunately, it was rejected then for
the very same reason as now. I too think this option would be useful.
One use case I can
Jürgen Spitzmüller wrote:
spitz wrote:
+#
+# InsetNote context menu
+#
+
+ Menu context-note
+ Submenu Change Type|y edit_notetype
+ Item Settings...|S inset-settings note
+ End
+
+ Menu edit_notetype
+ Item LyX Note|N
All cross-file cross-references in 1.6 seem to show up as broken.
rh
When I traced it, gdb reported it elsewhere, in a totally unhelpful way.
Could it be some initialization problem with qt_() itself?
I also suspected this, maybe we can change qt_() (no translation, for
example) and test.
Bo
Bo Peng wrote:
Do we really need this
Yes. Try to open the Listings (or any other collapsable) dialog via context
menu by pressing on the button: it is disabled (without my change). It is
only enabled if you pressed _inside_ the collapsable.
since we can use LFUN_NEXT_INSET_TOGGLE
Bo Peng wrote:
Thank you for explaining this. I still do not know 'exactly' what
LFUN_NEXT_INSET_TOGGLE is. If INSET_SETTINGS can do most of its work,
maybe they should be merged.
It toggles a collapsable at cursor position. If you are in front of a
collapsed index inset, for instance, it
Now some people requested that this also works for non-collapsables such as
labels. They expect that if you press C-i in front of these, that they can
edit the contents as well (i.e. that the label dialog pops up).
It does work for InsetLabel and InsetRef, right?
Bo
Bo Peng wrote:
It does work for InsetLabel and InsetRef, right?
yes, amonst others.
Jürgen
rgheck wrote:
In any event, the attached patch fixes the Ctrl-I problem. It also
addresses what looks like it would be a similar problem in the mouse
handling code. Comments, anyone?
While I was at fixing the context menu stuff, I fixed this one as well (albeit
a bit differently).
Jürgen
rgheck wrote:
All cross-file cross-references in 1.6 seem to show up as broken.
cross-file means reference from child to master, right? xrefs from master to
child or from child to child work here.
Jürgen
On Mon, Mar 24, 2008 at 12:31:15PM +, [EMAIL PROTECTED] wrote:
Author: rgheck
Date: Mon Mar 24 13:31:07 2008
New Revision: 23913
URL: http://www.lyx.org/trac/changeset/23913
Log:
Add support for document-local layout information. GUI is to follow.
That's a tall order to do generally
Martin Vermeer wrote:
On Mon, Mar 24, 2008 at 12:31:15PM +, [EMAIL PROTECTED] wrote:
Author: rgheck
Date: Mon Mar 24 13:31:07 2008
New Revision: 23913
URL: http://www.lyx.org/trac/changeset/23913
Log:
Add support for document-local layout information. GUI is to follow.
That's a
1.insert float
2.go with cursor before Figure 1:
3.press ctrl+i
4.kaboom
p
Bo Peng wrote:
Thank you for explaining this. I still do not know 'exactly' what
LFUN_NEXT_INSET_TOGGLE is. If INSET_SETTINGS can do most of its work,
maybe they should be merged.
It toggles a collapsable at cursor position. If you are in front of a
collapsed index inset, for instance,
Pavel Sanda wrote:
here cursor is not moved inside (tried with ert and note).
right. Also not in 1.5. I stand corrected.
also there is chaos on left button actions:
e.g.:
ert + left click collapses and open menu simultaneously.
note + left click open both context menu and dialog.
cannot
also there is chaos on left button actions:
e.g.:
ert + left click collapses and open menu simultaneously.
note + left click open both context menu and dialog.
cannot reproduce.
Left click should not open the context menu whatsoever.
because i'm moron and write left instead of
Pavel Sanda wrote:
because i'm moron and write left instead of right.
try once again with the right mouse button.
of course I did that, and I cannot reproduce the problems there either. Only
the context menu opens, as expected.
Jürgen
Jürgen Spitzmüller wrote:
rgheck wrote:
All cross-file cross-references in 1.6 seem to show up as broken.
cross-file means reference from child to master, right? xrefs from master to
child or from child to child work here.
In this case, I'm looking at e.g. Customization to
rgheck wrote:
In this case, I'm looking at e.g. Customization to Extended Features.
Those don't show up right. But maybe they shouldn't show up right?
I don't think we support such refs beyond document scope (in the GUI).
Jürgen
Pavel Sanda wrote:
1.insert float
2.go with cursor before Figure 1:
3.press ctrl+i
4.kaboom
try again, please.
Jürgen
On Mon, 24 Mar 2008, Pavel Sanda wrote:
I also think the LyX.org site is OK except for the background and the
white text... changing that alone could make a huge difference. I
we have fix for this long time, but nobody on dev list commented the
design so i let it die.
hi,
is there some reason why we have PlainLayout instead of Plain Layout
pavel
On Mon, 24 Mar 2008, Joost Verburg wrote:
Rich Shepard wrote:
Regardless of what layout you choose and how you go about building
it (I, too, support xhtml and css), there is one universal design
criterion I urge you to follow: high contrast between text and
background.
I fully agree.
Pavel Sanda wrote:
1.insert float
2.go with cursor before Figure 1:
3.press ctrl+i
4.kaboom
try again, please.
works, thanks.
pavel
Jürgen Spitzmüller wrote:
rgheck wrote:
In this case, I'm looking at e.g. Customization to Extended Features.
Those don't show up right. But maybe they shouldn't show up right?
I don't think we support such refs beyond document scope (in the GUI).
OK. This is some kind of
Hi,
I am posting my message on this list, as I would like to know more
about the internal image processing of LyX.
As per my understanding, I define two converters for SVG files:
1. SVG = PNG, as png files can be rendered by the QT-GUI widgets.
2. SVG = EPS, as EPS is natively supported by
hi,
is there some reason why we have PlainLayout instead of Plain Layout?
if not i will commit the attached (Richard, please look that it makes sense).
pavel
diff --git a/src/TextClass.cpp b/src/TextClass.cpp
index da80c56..3c2afbc 100644
--- a/src/TextClass.cpp
+++ b/src/TextClass.cpp
@@
On Mon, 24 Mar 2008, Joost Verburg wrote:
I'm for the KISS approach here, but would also like to suggest that we use
some version of the wiki engine with a CMS extension. There are many users
skins you find everywhere. http://cms.ww-a.de/index.php/Main/HomePage for
Ok, so no one seems to
On Mon, Mar 24, 2008 at 8:13 PM, Dominik Böhm [EMAIL PROTECTED] wrote:
Why is that so, what didn't I understand w.r.t. the image handling of
LyX? What can I do about the bad image quality?
Well, I guess I actually have understand how the things are working in LyX...
The problem was that I
On Mon, 24 Mar 2008, [EMAIL PROTECTED] wrote:
1. Set up a framework
I've started on the framework and there is now a basic wiki here:
http://www.lyx.org/~chr/www/org/index.php
This wiki, or rather, it's contents, will later become the new web site.
Feel free to start editing pages
Pavel Sanda wrote:
hi,
is there some reason why we have PlainLayout instead of Plain Layout?
if not i will commit the attached (Richard, please look that it makes sense).
If it works, it's fine with me.
rh
On Mon, Mar 24, 2008 at 03:15:17PM +0100, Jürgen Spitzmüller wrote:
spitz wrote:
+#
+# InsetNote context menu
+#
+
+ Menu context-note
+ Submenu Change Type|y edit_notetype
+ Item Settings...|S inset-settings note
+ End
+
+ Menu
I've gone through and updated the Customization manual, including
modernizing its use of LyX. I've committed the changes to trunk so they
can be viewed.
Here are a few of the larger, and so potentially more controversial,
things I did, in case anyone has any comment. Of course, nothing is
On Mon, Mar 24, 2008 at 03:52:12PM +0100, Joost Verburg wrote:
Pavel Sanda wrote:
An integration of the main site and the wiki is a great idea. If the wiki
functions are hidden for the official content and only shown when an
authenticated user is logged in, it still looks professional and
Andre Poenitz wrote:
I don't think I agree. The community is much better at keeping vital
contents up-to-date then the core developers are. Look at what we have
now: The developer maintained official pages that are mostly correct
when talking about last millenium's achievements, and a wiki page
[EMAIL PROTECTED] wrote:
* wiki.lyx.org will remain the wiki - there is no integration of content.
It will be clear what is official and what is community.
The wiki may, or may not, keep it's current look.
Why not integrate the current wiki with the new site, so they can share
the same
[EMAIL PROTECTED] wrote:
It's an improvement in my eyes at least, I'd be fine with you committing
it. Are there anyone that objects? (It might take a little while for
Rex to come up with something, and if all you have to do is a commit...)
At least it makes the site somewhat easier to read.
On Mon, Mar 24, 2008 at 10:36:33PM +0100, Joost Verburg wrote:
Andre Poenitz wrote:
I don't think I agree. The community is much better at keeping vital
contents up-to-date then the core developers are. Look at what we have
now: The developer maintained official pages that are mostly correct
Great, Christian! Should we now manually copy and paste content over
from the current website and wikify it?
Rex
On Mon, Mar 24, 2008 at 4:48 PM, [EMAIL PROTECTED] wrote:
On Mon, 24 Mar 2008, [EMAIL PROTECTED] wrote:
1. Set up a framework
I've started on the framework and there is now a
This patch prevents InsetGraphics from being created without a Buffer.
Comments?
rh
Index: src/CutAndPaste.cpp
===
--- src/CutAndPaste.cpp (revision 23930)
+++ src/CutAndPaste.cpp (working copy)
@@ -859,7 +859,7 @@
return;
Russ Woodroofe wrote:
> ATTACHMENTS:
> Patch against 1.5.4
> Patch against 'trunk' as downloaded Mar 22, 2008
Paul, could you have a look at these patches, please?
Thanks,
Jürgen
Michal Skrzypek wrote:
> I wanted to report something relatively harmless, but strange. I am
> currently using LyX 1.5.2 (XP SP2, Polish version). I apologize that I
> cannot check this with the current version, but for now I cannot
> upgrade/test it due to time constraints, as I am nearing the
Here are some changes that enlarge the possibilities to alter inset settings
via context menus.
Similar menus should be implemented for boxes, notes and friends, and for
citations (but there, things are a bit more complex due to the specifics of
the cite engines).
Comments?
Jürgen
Index:
bpeng wrote:
> + case LFUN_EXTERNAL_EDIT: {
> + FuncRequest fr(cmd);
> + InsetExternal * inset =
> getInsetByCode(d->cursor_,
> + EXTERNAL_CODE);
> + if (inset)
> + inset->dispatch(d->cursor_, fr);
> +
rgheck wrote:
> It certainly does at the moment, but that's at least in part because
> there's a general problem with the dispatch mechanism in BufferView.
Well, the behaviour was introduced _intentionally_ (somewhere in the 1.5
cycle, IIRC).
Jürgen
Les Sharpe wrote:
Good Morning All,
Not sure who can best advise me so I am sending to both suggested
addresses.
I cannot get past the first example/test in the Tutorial (2.1.1 et
seq). I type in the suggested sentence and whether I hit the view -
dvi item in the drop down menu or the
Bo Peng wrote:
Note that the mysterious listings setting crash is still there
Can you remind me how to reproduce this?
rh
Jürgen Spitzmüller wrote:
Here are some changes that enlarge the possibilities to alter inset settings
via context menus.
Similar menus should be implemented for boxes, notes and friends, and for
citations (but there, things are a bit more complex due to the specifics of
the cite engines).
Jürgen Spitzmüller wrote:
rgheck wrote:
It certainly does at the moment, but that's at least in part because
there's a general problem with the dispatch mechanism in BufferView.
Well, the behaviour was introduced _intentionally_ (somewhere in the 1.5
cycle, IIRC).
Which behavior
rgheck wrote:
> Which behavior do you mean?
Opening Editable (not HIGHLY_EDITABLE) inset's dialog with C-i.
> My puzzlement concerns why Ctrl-I works to
> collapse (say) ERT that the cursor is inside in 1.5 but not in current
> trunk.
Ah, then we are talking about different issues.
Jürgen
rgheck wrote:
> Right. These menus will have to be dynamically generated somehow, given
> information about the cite engine. But that shouldn't be too terribly
> bad. We do that kind of thing in so many cases.
Yes, this is what I had in mind as well.
> > Comments?
> >
> >
>
> Yes. This is
Jürgen Spitzmüller wrote:
rgheck wrote:
Which behavior do you mean?
Opening Editable (not HIGHLY_EDITABLE) inset's dialog with C-i.
My puzzlement concerns why Ctrl-I works to
collapse (say) ERT that the cursor is inside in 1.5 but not in current
trunk.
Ah, then we are
On Mon, Mar 24, 2008 at 7:21 AM, rgheck <[EMAIL PROTECTED]> wrote:
> Bo Peng wrote:
> > Note that the mysterious listings setting crash is still there
> >
> >
> Can you remind me how to reproduce this?
>
Open a document with a listings inset, right click, settings. Most of
the time, lyx
Bo Peng wrote:
On Mon, Mar 24, 2008 at 7:21 AM, rgheck <[EMAIL PROTECTED]> wrote:
Bo Peng wrote:
> Note that the mysterious listings setting crash is still there
>
>
Can you remind me how to reproduce this?
Open a document with a listings inset, right click, settings. Most of
rgheck wrote:
> > Open a document with a listings inset, right click, settings. Most of
> > the time, lyx will crash here (Linux, RHEL4, gcc 4.1, qt 4.22)
> >
> >
>
> Weird.
FWIW, I see this too:
http://bugzilla.lyx.org/show_bug.cgi?id=4607
Jürgen
spitz wrote:
> +#
> +# InsetNote context menu
> +#
> +
> + Menu "context-note"
> + Submenu "Change Type|y" "edit_notetype"
> + Item "Settings...|S" "inset-settings note"
> + End
> +
> + Menu "edit_notetype"
> + Item "LyX Note|N"
On Mon, Mar 24, 2008 at 9:13 AM, Jürgen Spitzmüller
<[EMAIL PROTECTED]> wrote:
> rgheck wrote:
> > > Open a document with a listings inset, right click, settings. Most of
> > > the time, lyx will crash here (Linux, RHEL4, gcc 4.1, qt 4.22)
>
> FWIW, I see this too:
>
> Author: spitz
> Date: Mon Mar 24 15:12:19 2008
> New Revision: 23923
>
> URL: http://www.lyx.org/trac/changeset/23923
> Log:
> * src/BufferView.cpp:
> * src/Text3.cpp:
> - fix LFUN_INSET_SETTINGS so that it also works at cursor position.
>
> * LyXAction.cpp:
> - doxy.
>
> /*!
> *
[EMAIL PROTECTED] wrote:
I'm for the KISS approach here, but would also like to suggest that we
use some version of the wiki engine with a CMS extension. There are many
users that have taken this particular wiki engine and used it as a CMS.
The advantage is that I can help with setting it up,
Pavel Sanda wrote:
> e.g inset-settings inside ert does nothing for me.
because there's no more ERT dialog?
> also i would ask if this lfun shouldn't be used for uncollapsable insets?
> it will make much more sense than next-inset-toggle.
I would rather let inset-settings call
On Mon, Mar 24, 2008 at 9:12 AM, <[EMAIL PROTECTED]> wrote:
> Author: spitz
> Date: Mon Mar 24 15:12:19 2008
> New Revision: 23923
>
> URL: http://www.lyx.org/trac/changeset/23923
> Log:
> * src/BufferView.cpp:
> * src/Text3.cpp:
> - fix LFUN_INSET_SETTINGS so that it also works at
> An integration of the main site and the wiki is a great idea. If the wiki
> functions are hidden for the "official" content and only shown when an
> authenticated user is logged in, it still looks professional and not too
> much like a wiki.
then you have problem that many pages in wiki
> Pavel Sanda wrote:
> > e.g inset-settings inside ert does nothing for me.
>
> because there's no more ERT dialog?
yes, the doxy is wrong. anyway it doesn't work for note either.
>
> > also i would ask if this lfun shouldn't be used for uncollapsable insets?
> > it will make much more sense
Bo Peng wrote:
> Do we really need this
Yes. Try to open the Listings (or any other collapsable) dialog via context
menu by pressing on the button: it is disabled (without my change). It is
only enabled if you pressed _inside_ the collapsable.
> since we can use LFUN_NEXT_INSET_TOGGLE for the
Pavel Sanda wrote:
An integration of the main site and the wiki is a great idea. If the wiki
functions are hidden for the "official" content and only shown when an
authenticated user is logged in, it still looks professional and not too
much like a wiki.
then you have problem that many pages
> In my opinion the current wiki content should be something like a separate
> "community" section, not a part of the official web. But I think using the
yes.
> I only wanted to say that we should keep it this way for the new wiki CMS
> accounts.
yes, it may be that wiki way of changing
Pavel Sanda wrote:
> > because there's no more ERT dialog?
>
> yes, the doxy is wrong. anyway it doesn't work for note either.
The documentation was wrong.
BTW the ERT dialog is also superseded by the context menu.
Jürgen
Bo Peng wrote:
On Mon, Mar 24, 2008 at 9:13 AM, Jürgen Spitzmüller
<[EMAIL PROTECTED]> wrote:
rgheck wrote:
> > Open a document with a listings inset, right click, settings. Most of
> > the time, lyx will crash here (Linux, RHEL4, gcc 4.1, qt 4.22)
FWIW, I see this too:
Joost Verburg wrote:
Joost Verburg wrote:
Abdelrazak Younes wrote:
FYI, I implemented just that before 1.5.0 and part of the code is
still there commented out. Unfortunately, it was rejected then for
the very same reason as now. I too think this option would be useful.
One use case I can
Jürgen Spitzmüller wrote:
spitz wrote:
+#
+# InsetNote context menu
+#
+
+ Menu "context-note"
+ Submenu "Change Type|y" "edit_notetype"
+ Item "Settings...|S" "inset-settings note"
+ End
+
+ Menu "edit_notetype"
+ Item "LyX Note|N"
All cross-file cross-references in 1.6 seem to show up as "broken".
rh
> When I traced it, gdb reported it elsewhere, in a totally unhelpful way.
> Could it be some initialization problem with qt_() itself?
I also suspected this, maybe we can change qt_() (no translation, for
example) and test.
Bo
1 - 100 of 136 matches
Mail list logo
