Re: Insert menu

On 1/26/21 4:27 PM, Yuriy Skalko wrote: I would think Marginal Notes could certainly go with notes. But footnotes are so common, at least in academic writing, that I'd be reluctant to move them another keystroke away. Riki But frequent usage of menu for this is not very effective. There is

Re: Insert menu

Also I think marginal notes are too different sorts of notes than the ones in the Notes submenu. Footnotes and marginal notes are part of the document structure, the other notes are more editorial devices (the rather esoteric "gray text", whose purpose I never fully grasped, note might be a

Re: Insert menu

Am Dienstag, dem 26.01.2021 um 13:59 -0500 schrieb Richard Kimberly Heck: > But footnotes are so common, at least in academic writing, that I'd > be reluctant to move them another keystroke away. I agree.  Also I think marginal notes are too different sorts of notes than the ones in the Notes

Re: Insert menu

I would think Marginal Notes could certainly go with notes. But footnotes are so common, at least in academic writing, that I'd be reluctant to move them another keystroke away. Riki But frequent usage of menu for this is not very effective. There is a convenient toolbar button for this.

Re: Insert menu

On 1/26/21 1:50 PM, Yuriy Skalko wrote: But I agree with another Andrew's proposition: I realise this adds another item to a long Insert menu, but an overall shrinkage by one follows if "Footnote" and "Marginal Note" are included under "Note". The Insert m

Re: Insert menu

ver, I do not think that we should structure the menu based on English semantics. Jürgen I agree that current state of menu is better where these items are grouped. Also TOC is very common at the end of the books in Russian and nomenclatures -- at the front. But I agree with anothe

Re: Insert menu

Am Dienstag, dem 26.01.2021 um 15:42 +0100 schrieb Jean-Marc Lasgouttes: > Fair enough. But the naming is more descriptive than conceptual (if I > may say so). Definitely. I hope someone comes with a more succinct label. Looking at the LibreOffice and MS Word cases, I fear this is not easy to

Re: Insert menu

Le 26/01/2021 à 15:08, Jürgen Spitzmüller a écrit : Am Dienstag, dem 26.01.2021 um 11:23 +0100 schrieb Jean-Marc Lasgouttes: Can we have something that combines front and end matters? Like what we have now :-)? Fair enough. But the naming is more descriptive than conceptual (if I may say

Re: Insert menu

Am Dienstag, dem 26.01.2021 um 11:23 +0100 schrieb Jean-Marc Lasgouttes: > Can we have something that combines front and end matters? Like what we have now :-)? BTW LibreOffice has it in "Insert > Table of Contents and Index" (which is odd since this also contains Bibliography, LOF, LOT). German

Re: Insert menu

Le 26/01/2021 à 11:07, Jean-Pierre Chrétien a écrit : Le 26/01/2021 à 09:37, José Abílio Matos a écrit : One striking example for me is the case of Portuguese books where the TOC was placed at the end. The idea is that in this case you can interpret the TOC as some kind of index. Actually it

Re: Insert menu

Le 26/01/2021 à 09:37, José Abílio Matos a écrit : One striking example for me is the case of Portuguese books where the TOC was placed at the end. The idea is that in this case you can interpret the TOC as some kind of index. Actually it even received the name of index while the index was

Re: Insert menu

On Tuesday, January 26, 2021 7:27:06 AM WET Jürgen Spitzmüller wrote: > I prefer functional category over positional. TOC, LOF, LOT (the latter > two often in the backmatter BTW, sometimes even the former), indexes, > nomenclature, references and glossaries all are lists with entries that > refer

Re: Insert menu

Am Dienstag, dem 26.01.2021 um 10:16 +1300 schrieb Andrew Parsloe: > English *syntax* perhaps?  No, semantics (semasiology of "list" vs. "Verzeichnis"). > The semantics I had in mind was the division of a book into three > parts: prelims (i.e. preliminary pages), text or body of the book, > and

Re: Insert menu

On 25/01/2021 11:15 pm, Jürgen Spitzmüller wrote: Am Montag, dem 25.01.2021 um 16:56 +1300 schrieb Andrew Parsloe: (LyX 2.4.0 alpha) Inserted a TOC recently. My eye ran down the Insert menu to Table..., realised that wasn't it, then back up the list to "List/Contents/References", foun

Re: Insert menu

Am Montag, dem 25.01.2021 um 16:56 +1300 schrieb Andrew Parsloe: > (LyX 2.4.0 alpha) Inserted a TOC recently. My eye ran down the Insert > menu to Table..., realised that wasn't it, then back up the list to > "List/Contents/References", found and duly inserted the TOC inset.

Insert menu

(LyX 2.4.0 alpha) Inserted a TOC recently. My eye ran down the Insert menu to Table..., realised that wasn't it, then back up the list to "List/Contents/References", found and duly inserted the TOC inset. Looking at the items in the submenu, I feel three of them (index, no

Re: A better ordering of the Insert menu

I would say that the context menu could be useful too for that. Note also that optional arguments are not only for custom insets... JMarc Le 14 juin 2015 00:38:31 CEST, aparsloe apars...@clear.net.nz a écrit : ). This seems clumsy to me. A simple reordering of the Insert menu places

A better ordering of the Insert menu

Dear LyX devs, With the standard Insert menu, if you want to insert arguments into a custom inset by menu you have to hunt among a lot of miscellaneous items down in the nether region of the Insert menu, unhelpfully distant from the Custom Inset entry that gives rise to them

A better ordering of the Insert menu

Dear LyX devs, With the standard Insert menu, if you want to insert arguments into a custom inset by menu you have to hunt among a lot of miscellaneous items down in the "nether region" of the Insert menu, unhelpfully distant from the Custom Inset entry that gives ri

Re: A better ordering of the Insert menu

I would say that the context menu could be useful too for that. Note also that optional arguments are not only for custom insets... JMarc Le 14 juin 2015 00:38:31 CEST, aparsloe <apars...@clear.net.nz> a écrit : ). > >This seems clumsy to me. A simple reordering of the Insert

Re: [patches] all items are now disabled in insert menu if read only

Date: Wed, 19 Feb 2014 16:58:29 -0500 Subject: [PATCH 2/4] Disable custom insets insert menu if read only Before, if a document was read only and had no custom insets defined, the submenu would be enabled. --- src/frontends/qt4/Menus.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

Re: [patches] all items are now disabled in insert menu if read only

Le 28/07/2014 17:35, Scott Kostyshak a écrit : JMarc (don't worry if you can't look at this before you leave on vacation), I first interpreted your response in this thread as disagreeing with the patches I proposed. Upon rereading I think there was a misunderstanding because of poor description

Re: [patches] all items are now disabled in insert menu if read only

On Mon, Jul 28, 2014 at 11:42 AM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: Le 28/07/2014 17:35, Scott Kostyshak a écrit : JMarc (don't worry if you can't look at this before you leave on vacation), I first interpreted your response in this thread as disagreeing with the patches I

Re: [patches] all items are now disabled in insert menu if read only

Help)) { enabled = true; break; } -- 1.8.3.2 From 2d594c6be3e495b3652474d9a1f8a2aee8586577 Mon Sep 17 00:00:00 2001 From: Scott Kostyshak <skost...@lyx.org> Date: Wed, 19 Feb 2

Re: [patches] all items are now disabled in insert menu if read only

Le 28/07/2014 17:35, Scott Kostyshak a écrit : JMarc (don't worry if you can't look at this before you leave on vacation), I first interpreted your response in this thread as disagreeing with the patches I proposed. Upon rereading I think there was a misunderstanding because of poor description

Re: [patches] all items are now disabled in insert menu if read only

On Mon, Jul 28, 2014 at 11:42 AM, Jean-Marc Lasgouttes wrote: > Le 28/07/2014 17:35, Scott Kostyshak a écrit : > >> JMarc (don't worry if you can't look at this before you leave on >> vacation), I first interpreted your response in this thread as >> disagreeing with the

Re: [patches] all items are now disabled in insert menu if read only

On Thu, Feb 20, 2014 at 4:02 AM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: 19/02/2014 23:02, Scott Kostyshak: I'm planning to commit these after 2.1 is released. If anyone has comments or would like to see them in 2.1 let me know. Concerning menus, the Apple HIG says: Ensure that a

Re: [patches] all items are now disabled in insert menu if read only

Am Freitag, 21. Februar 2014 um 10:36:51, schrieb Scott Kostyshak skost...@lyx.org On Thu, Feb 20, 2014 at 4:02 AM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: 19/02/2014 23:02, Scott Kostyshak: I'm planning to commit these after 2.1 is released. If anyone has comments or would like

Re: [patches] all items are now disabled in insert menu if read only

On Fri, Feb 21, 2014 at 10:50 AM, Kornel Benko kor...@lyx.org wrote: Am Freitag, 21. Februar 2014 um 10:36:51, schrieb Scott Kostyshak skost...@lyx.org On Thu, Feb 20, 2014 at 4:02 AM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: 19/02/2014 23:02, Scott Kostyshak: I'm planning to

Re: [patches] all items are now disabled in insert menu if read only

Am Freitag, 21. Februar 2014 um 10:56:19, schrieb Scott Kostyshak skost...@lyx.org I think that I again gave a poor description of the patch (I'm on a roll here). The patch enables expanding of submenus even when all of the items are disabled. For example, go to Help Introduction. The

Re: [patches] all items are now disabled in insert menu if read only

On Thu, Feb 20, 2014 at 4:02 AM, Jean-Marc Lasgouttes wrote: > 19/02/2014 23:02, Scott Kostyshak: > >> I'm planning to commit these after 2.1 is released. If anyone has >> comments or would like to see them in 2.1 let me know. > > > Concerning menus, the Apple HIG says: > >

Re: [patches] all items are now disabled in insert menu if read only

Am Freitag, 21. Februar 2014 um 10:36:51, schrieb Scott Kostyshak > On Thu, Feb 20, 2014 at 4:02 AM, Jean-Marc Lasgouttes > wrote: > > 19/02/2014 23:02, Scott Kostyshak: > > > >> I'm planning to commit these after 2.1 is released. If anyone has > >>

Re: [patches] all items are now disabled in insert menu if read only

On Fri, Feb 21, 2014 at 10:50 AM, Kornel Benko wrote: > Am Freitag, 21. Februar 2014 um 10:36:51, schrieb Scott Kostyshak > > >> On Thu, Feb 20, 2014 at 4:02 AM, Jean-Marc Lasgouttes > >> wrote: > >> > 19/02/2014 23:02, Scott Kostyshak: > >>

Re: [patches] all items are now disabled in insert menu if read only

Am Freitag, 21. Februar 2014 um 10:56:19, schrieb Scott Kostyshak > I think that I again gave a poor description of the patch (I'm on a > roll here). The patch enables expanding of submenus even when all of > the items are disabled. For example, go to Help > Introduction. The >

Re: [patches] all items are now disabled in insert menu if read only

19/02/2014 23:02, Scott Kostyshak: I'm planning to commit these after 2.1 is released. If anyone has comments or would like to see them in 2.1 let me know. Concerning menus, the Apple HIG says: Ensure that a submenu’s title is undimmed even when all its commands are unavailable. As with

Re: [patches] all items are now disabled in insert menu if read only

19/02/2014 23:02, Scott Kostyshak: I'm planning to commit these after 2.1 is released. If anyone has comments or would like to see them in 2.1 let me know. Concerning menus, the Apple HIG says: Ensure that a submenu’s title is undimmed even when all its commands are unavailable. As with

[patches] all items are now disabled in insert menu if read only

: [PATCH 3/4] Disable branches insert menu if read only --- src/frontends/qt4/Menus.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/frontends/qt4/Menus.cpp b/src/frontends/qt4/Menus.cpp index bf7d1a7..dfba0e6 100644 --- a/src/frontends/qt4/Menus.cpp +++ b/src/frontends/qt4

Re: [patches] all items are now disabled in insert menu if read only

On 02/19/2014 05:02 PM, Scott Kostyshak wrote: I'm planning to commit these after 2.1 is released. If anyone has comments or would like to see them in 2.1 let me know. This looks pretty safe to me. I'd have no objection to its going into 2.1.0, but it's Vincent's call. rh

[patches] all items are now disabled in insert menu if read only

ep 17 00:00:00 2001 From: Scott Kostyshak <skost...@lyx.org> Date: Wed, 19 Feb 2014 16:58:29 -0500 Subject: [PATCH 2/4] Disable custom insets insert menu if read only Before, if a document was read only and had no custom insets defined, the submenu would be enabled. --- src/frontends/qt4/M

Re: [patches] all items are now disabled in insert menu if read only

On 02/19/2014 05:02 PM, Scott Kostyshak wrote: I'm planning to commit these after 2.1 is released. If anyone has comments or would like to see them in 2.1 let me know. This looks pretty safe to me. I'd have no objection to its going into 2.1.0, but it's Vincent's call. rh

Position of Custom InsetLayout Arguments in Insert menu

Custom InsetLayout X has an Argument Y. We have: Insert Custom X, but Insert Y I think both X and Y should appear under Insert Custom. Agreed? Julien

Re: Position of Custom InsetLayout Arguments in Insert menu

Julien Rioux wrote: I think both X and Y should appear under Insert Custom. Agreed? If you refer to InsetArgument: No. All arguments should appear at the same place, namely the inset top level menu. Actually, I think that the Custom submenu is horrible UI design. Likewise Edit

Re: Position of Custom InsetLayout Arguments in Insert menu

On 12/01/2013 4:54 AM, Jürgen Spitzmüller wrote: Julien Rioux wrote: I think both X and Y should appear under Insert Custom. Agreed? If you refer to InsetArgument: No. All arguments should appear at the same place, namely the inset top level menu. Actually, I think that the Custom submenu

Re: Position of Custom InsetLayout Arguments in Insert menu

Julien Rioux wrote: Should we kill the Custom submenu then? We need to have a good alternative first. We cannot simply put all custom insets to the top level menu, since this is too large already. I suppose we should define multiple anchors in the menu where custom insets could be assigned

Re: Position of Custom InsetLayout Arguments in Insert menu

On Sat, Jan 12, 2013 at 11:26 AM, Jürgen Spitzmüller sp...@lyx.org wrote: Julien Rioux wrote: Should we kill the Custom submenu then? We need to have a good alternative first. I think a good starting point would be fixing http://www.lyx.org/trac/ticket/7877 . This looks like a relatively

Position of Custom InsetLayout Arguments in Insert menu

Custom InsetLayout X has an Argument Y. We have: Insert > Custom > X, but Insert > Y I think both X and Y should appear under Insert > Custom. Agreed? Julien

Re: Position of Custom InsetLayout Arguments in Insert menu

Julien Rioux wrote: > I think both X and Y should appear under Insert > Custom. > > Agreed? If you refer to InsetArgument: No. All arguments should appear at the same place, namely the inset top level menu. Actually, I think that the "Custom" submenu is horrible UI design. Likewise Edit >

Re: Position of Custom InsetLayout Arguments in Insert menu

On 12/01/2013 4:54 AM, Jürgen Spitzmüller wrote: Julien Rioux wrote: I think both X and Y should appear under Insert > Custom. Agreed? If you refer to InsetArgument: No. All arguments should appear at the same place, namely the inset top level menu. Actually, I think that the "Custom"

Re: Position of Custom InsetLayout Arguments in Insert menu

Julien Rioux wrote: > Should we kill the Custom submenu then? We need to have a good alternative first. We cannot simply put all custom insets to the top level menu, since this is too large already. I suppose we should define multiple "anchors" in the menu where custom insets could be assigned

Re: Position of Custom InsetLayout Arguments in Insert menu

On Sat, Jan 12, 2013 at 11:26 AM, Jürgen Spitzmüller wrote: > Julien Rioux wrote: >> Should we kill the Custom submenu then? > > We need to have a good alternative first. > I think a good starting point would be fixing http://www.lyx.org/trac/ticket/7877 . This looks like a

#6989 (regression in r35855) Opening AdvFind pane and Insert Menu causes Crash.

Hi, Vincent you suggested I report recent regressions to the list, and this commit was from yesterday. To reproduce: 1) Press Ctrl-Shift-F to open the advanced find pane (KK: \CF) 2) Press Alt-I to open the insert menu (KK: \Ai) I then get the following Crash. This appears to be a regression

Re: #6989 (regression in r35855) Opening AdvFind pane and Insert Menu causes Crash.

Hi, Vincent you suggested I report recent regressions to the list, and this commit was from yesterday. Yes, I did. My suggestion was even to not create a bugreport for it. This kind of things will be fixed very quickly. Fixed at r35863. Vincent

Re: #6989 (regression in r35855) Opening AdvFind pane and Insert Menu causes Crash.

Ah.. and thanks for reporting and checking upon us. Vincent

#6989 (regression in r35855) Opening AdvFind pane and Insert Menu causes Crash.

Hi, Vincent you suggested I report recent regressions to the list, and this commit was from yesterday. To reproduce: 1) Press Ctrl-Shift-F to open the advanced find pane (KK: \CF) 2) Press Alt-I to open the insert menu (KK: \Ai) I then get the following Crash. This appears to be a regression

Re: #6989 (regression in r35855) Opening AdvFind pane and Insert Menu causes Crash.

> Hi, Vincent you suggested I report recent regressions to the list, and > this commit was from yesterday. Yes, I did. My suggestion was even to not create a bugreport for it. This kind of things will be fixed very quickly. Fixed at r35863. Vincent

Re: #6989 (regression in r35855) Opening AdvFind pane and Insert Menu causes Crash.

Ah.. and thanks for reporting and checking upon us. Vincent

Re: Insert menu shortcut

"Baruch" == Baruch Even [EMAIL PROTECTED] writes: Baruch On Fri, 13 Oct 2000, Lior Silberman wrote: Int 1.1.5, the shortcut for "Insert-Figure" was M-i g and for "Insert-Footnote" it was M-i f. In the current menu defs, the Figure entry also has an 'F', overriding the 'footnote'. Since

Re: Insert menu shortcut

> "Baruch" == Baruch Even <[EMAIL PROTECTED]> writes: Baruch> On Fri, 13 Oct 2000, Lior Silberman wrote: >> Int 1.1.5, the shortcut for "Insert->Figure" was M-i g and for >> "Insert->Footnote" it was M-i f. In the current menu defs, the >> Figure entry also has an 'F', overriding the

Re: Insert menu shortcut

On Fri, 13 Oct 2000, Lior Silberman wrote: Int 1.1.5, the shortcut for "Insert-Figure" was M-i g and for "Insert-Footnote" it was M-i f. In the current menu defs, the Figure entry also has an 'F', overriding the 'footnote'. Since there is no 'o' in this menu so far, I think we should

Re: Insert menu shortcut

On Fri, 13 Oct 2000, Lior Silberman wrote: > Int 1.1.5, the shortcut for "Insert->Figure" was M-i g and for > "Insert->Footnote" it was M-i f. In the current menu defs, the Figure > entry also has an 'F', overriding the 'footnote'. > > Since there is no 'o' in this menu so far, I think we