Re: Beamer usage again

Am Mittwoch, den 03.01.2018, 16:49 -0500 schrieb Scott Kostyshak: > On Wed, Jan 03, 2018 at 12:25:52PM +, Jürgen Spitzmüller wrote: > > Am Montag, den 01.01.2018, 17:57 +0100 schrieb Jürgen Spitzmüller: > > > > I think we could add one more separator below the inset > > > > arguments. > > > >

Re: Beamer usage again

On Wed, Jan 03, 2018 at 12:25:52PM +, Jürgen Spitzmüller wrote: > Am Montag, den 01.01.2018, 17:57 +0100 schrieb Jürgen Spitzmüller: > > > I think we could add one more separator below the inset arguments. > > > And > > > in general, some thought about potential improvements of the order > > >

Re: Beamer usage again

Am Montag, den 01.01.2018, 17:57 +0100 schrieb Jürgen Spitzmüller: > > I think we could add one more separator below the inset arguments. > > And > > in general, some thought about potential improvements of the order > > cannot harm. > > Here's a first small attempt to improve the grouping a bit.

Re: Beamer usage again

On Tue, Jan 02, 2018 at 12:33:16PM +, Jürgen Spitzmüller wrote: > > P.S. Sorry to feel like an overzealous hawk, but I've spent an > > inordinate amount of time in LyX with Beamer over the past year or > > so, so improvements are dear to me. Since we're (you're) working in > > the area, many

Re: Beamer usage again

On Mon, Jan 01, 2018 at 06:00:35PM +, Uwe Stöhr wrote: > El 01.01.2018 a las 11:06, Scott Kostyshak escribió: > > > I believe that Uwe is not going to be available to build the Windows > > binary for the next month, so we will not be able to get rc2 out soon > > anyway. In fact, I think the

Re: Beamer usage again

On Mon, Jan 01, 2018 at 11:47:10AM +, Jürgen Spitzmüller wrote: > Thank you. And Happy New Year everybody. Thanks for all your work, Jürgen, and best wishes to everyone for the new year. Scott signature.asc Description: PGP signature

Re: Beamer usage again

Am Dienstag, den 02.01.2018, 21:15 +0900 schrieb Joel Kulesza: > Jürgen, > > Thank you for working to clean-up the Insert menu and for moving > around a couple of the items. Am I correct that these ui.diff > changes haven't yet been applied? Yes. > I don't see them as of 8d8ee12e. Is the

Re: Beamer usage again

On Tue, Jan 2, 2018 at 1:57 AM, Jürgen Spitzmüller wrote: > Am Montag, den 01.01.2018, 14:54 +0100 schrieb Jürgen Spitzmüller: > > Am Montag, den 01.01.2018, 21:52 +0900 schrieb Joel Kulesza: > > > I think the separators help reduce the need to "hunt" for the new > > > items *a

Re: Beamer usage again

El 01.01.2018 a las 11:06, Scott Kostyshak escribió: I believe that Uwe is not going to be available to build the Windows binary for the next month, so we will not be able to get rc2 out soon anyway. In fact, I think the last day Uwe will be able to work on LyX for a while is on Tuesday. I

Re: Beamer usage again

Am Montag, den 01.01.2018, 14:54 +0100 schrieb Jürgen Spitzmüller: > Am Montag, den 01.01.2018, 21:52 +0900 schrieb Joel Kulesza: > > I think the separators help reduce the need to "hunt" for the new > > items *a lot*. > > > > However, there are now five Insert menu "sections" (using Beamer) >

Re: Beamer usage again

Am Montag, den 01.01.2018, 21:52 +0900 schrieb Joel Kulesza: > I think the separators help reduce the need to "hunt" for the new > items *a lot*. > > However, there are now five Insert menu "sections" (using Beamer) > with only the first two discernibly grouping items. A question > regarding

Re: Beamer usage again

On Mon, Jan 1, 2018 at 9:41 PM, Jürgen Spitzmüller wrote: > Am Montag, den 01.01.2018, 11:52 +0100 schrieb Jürgen Spitzmüller: > > Am Montag, den 01.01.2018, 05:01 -0500 schrieb Scott Kostyshak: > > > However, in the context menu we just have "Separated itemize > > > above". > > >

Re: Beamer usage again

Am Montag, den 01.01.2018, 11:52 +0100 schrieb Jürgen Spitzmüller: > Am Montag, den 01.01.2018, 05:01 -0500 schrieb Scott Kostyshak: > > However, in the context menu we just have "Separated itemize > > above". > > Should we prepend an "insert" in the context menu? > > I don't think we know which

Re: Beamer usage again

Am Montag, den 01.01.2018, 05:06 -0500 schrieb Scott Kostyshak: > Let's go ahead with the beamer changes for 2.3.0. There seems to be > strong opinions that the improvements are a clear step forward and > that > it is worth doing it this late in the release process because it > improves on an

Re: Beamer usage again

Am Montag, den 01.01.2018, 05:01 -0500 schrieb Scott Kostyshak: > However, in the context menu we just have "Separated itemize above". > Should we prepend an "insert" in the context menu? I don't think we know which menu we populate when passing the strings. Jürgen > > Scott signature.asc

Re: Beamer usage again

On Mon, Jan 01, 2018 at 06:06:13AM +, Pavel Sanda wrote: > Richard Heck wrote: > > That said, this strikes me too as enough of an improvement to warrant a > > late change. > > I've found these same aspects of the Beamer implementation unintuitive. > > +1 Let's go ahead with the beamer

Re: Beamer usage again

On Mon, Jan 01, 2018 at 05:41:46AM +, Joel Kulesza wrote: > I agree that "separated" is correct; however, I was wondering if separate > (or I should have specified, another word) was better in an overall sense > of clarity, lack of awkwardness, etc. Regardless, of all the issues that > have

Re: Beamer usage again

On Sun, Dec 31, 2017 at 08:40:04AM +, Jürgen Spitzmüller wrote: > Note that max. 3 entries are added. In many cases only 2 or 1. But I > agree it's a long menu. OK. > A submenu is not an option IMO. That lowers accessibility. Agreed. Scott signature.asc Description: PGP signature

Re: Beamer usage again

On Mon, Jan 01, 2018 at 05:59:51AM +, Pavel Sanda wrote: > I had the same thought. Still if there are these 3 options (edit menu/submenu > in insert/insert menu) the last one wins. But your concern is right. Fine with me. Scott signature.asc Description: PGP signature

Re: Beamer usage again

Richard Heck wrote: > That said, this strikes me too as enough of an improvement to warrant a > late change. > I've found these same aspects of the Beamer implementation unintuitive. +1 Pavel

Re: Beamer usage again

Scott Kostyshak wrote: > Not thinking about screen space, I do think that Insert is the most > intuitive for new users. I think the Edit menu could be more intuitive > if the names of the entries were "split environment" (like in the LFUN > name): splitting to me is an edit operation, but "adding"

Re: Beamer usage again

On Mon, Jan 1, 2018 at 12:54 AM, Jürgen Spitzmüller wrote: > Am Sonntag, den 31.12.2017, 23:20 +0900 schrieb Joel Kulesza: > > On Sun, Dec 31, 2017 at 10:44 PM, Jürgen Spitzmüller > > wrote: > > > Am Sonntag, den 31.12.2017, 21:35 +0900 schrieb Joel Kulesza: > > >

Re: Beamer usage again

Am Sonntag, den 31.12.2017, 23:20 +0900 schrieb Joel Kulesza: > On Sun, Dec 31, 2017 at 10:44 PM, Jürgen Spitzmüller > wrote: > > Am Sonntag, den 31.12.2017, 21:35 +0900 schrieb Joel Kulesza: > > > Is "Separated" or "Separate" the better word to use in the Insert > > > menu? > > >

Re: Beamer usage again

On Sun, Dec 31, 2017 at 10:44 PM, Jürgen Spitzmüller wrote: > Am Sonntag, den 31.12.2017, 21:35 +0900 schrieb Joel Kulesza: > > Is "Separated" or "Separate" the better word to use in the Insert > > menu? > > I'm not a native speaker of English, but my feeling was "Separated". >

Re: Beamer usage again

Am Sonntag, den 31.12.2017, 21:35 +0900 schrieb Joel Kulesza: > Is "Separated" or "Separate" the better word to use in the Insert > menu? I'm not a native speaker of English, but my feeling was "Separated". > Either way, the above/below meaning seems somewhat lost when in the > middle of a

Re: Beamer usage again

On Sun, Dec 31, 2017 at 6:40 PM, Jürgen Spitzmüller wrote: > Am Sonntag, den 31.12.2017, 09:30 +0100 schrieb Jürgen Spitzmüller: > > Am Samstag, den 30.12.2017, 22:52 -0500 schrieb Richard Heck: > > > Can someone put the 9261 patch on trac so it's more accessible? > > > > Done. >

Re: Beamer usage again

Am Sonntag, den 31.12.2017, 09:30 +0100 schrieb Jürgen Spitzmüller: > Am Samstag, den 30.12.2017, 22:52 -0500 schrieb Richard Heck: > > Can someone put the 9261 patch on trac so it's more accessible? > > Done. I've now also pushed it to master so everybody can try out more easily. I will revert

Re: Beamer usage again

Am Sonntag, den 31.12.2017, 09:40 +0100 schrieb Jürgen Spitzmüller: > > Not thinking about screen space, I do think that Insert is the most > > intuitive for new users. I think the Edit menu could be more > > intuitive > > if the names of the entries were "split environment" (like in the > > LFUN

Re: Beamer usage again

Am Sonntag, den 31.12.2017, 09:25 +0100 schrieb Jürgen Spitzmüller: > I'd think: If we touch the docs and strings (two new UI strings BTW, > and [rather small] changes to Customization.lyx, UserGuide.lyx and > beamer.lyx), we could do it now (or later) for all changes. I have now done all

Re: Beamer usage again

Am Sonntag, den 31.12.2017, 08:56 +0900 schrieb Joel Kulesza: > I pulled 9f9c2e02 and applied the 9261 patch. From there, attempting > to use Insert > Frame gives me a crash. Stupid thinko of mine. Fixed. Jürgen signature.asc Description: This is a digitally signed message part

Re: Beamer usage again

Am Samstag, den 30.12.2017, 17:52 -0500 schrieb Scott Kostyshak: > I'm concerned that the insert menu is becoming too long. See the > attached screenshot. I recognize that I do have a small laptop screen > (13 in, with 1360 x 767 resolution), but I'm guessing I'm not the > only > one. If four

Re: Beamer usage again

Am Samstag, den 30.12.2017, 22:52 -0500 schrieb Richard Heck: > Can someone put the 9261 patch on trac so it's more accessible? Done. Jürgen > > rh > signature.asc Description: This is a digitally signed message part

Re: Beamer usage again

Am Sonntag, den 31.12.2017, 01:28 -0500 schrieb Scott Kostyshak: > On Sat, Dec 30, 2017 at 04:07:19PM +, Richard Heck wrote: > > > That said, this strikes me too as enough of an improvement to > > warrant a > > late change. > > I've found these same aspects of the Beamer implementation > >

Re: Beamer usage again

Am Samstag, 30. Dezember 2017 um 11:40:19, schrieb Jürgen Spitzmüller > Am Samstag, den 30.12.2017, 10:32 + schrieb José Abílio Matos: > > The invariant in our stable series was always to keep the same file > > format. In my humble opinion this is a very good practice and > >

Re: Beamer usage again

On Sat, Dec 30, 2017 at 04:07:19PM +, Richard Heck wrote: > That said, this strikes me too as enough of an improvement to warrant a > late change. > I've found these same aspects of the Beamer implementation unintuitive. What exactly are we talking about potentially backporting? Is it the

Re: Beamer usage again

On Sun, Dec 31, 2017 at 12:52 PM, Richard Heck wrote: > On 12/30/2017 06:56 PM, Joel Kulesza wrote: > > On Sun, Dec 31, 2017 at 1:55 AM, Jürgen Spitzmüller wrote: > >> Am Samstag, den 30.12.2017, 10:48 +0100 schrieb Pavel Sanda: >> > I think we can safely go for

Re: Beamer usage again

On 12/30/2017 06:56 PM, Joel Kulesza wrote: > On Sun, Dec 31, 2017 at 1:55 AM, Jürgen Spitzmüller > wrote: > > Am Samstag, den 30.12.2017, 10:48 +0100 schrieb Pavel Sanda: > > I think we can safely go for it. > > Given that we already have two

Re: Beamer usage again

Am Samstag, den 30.12.2017, 10:48 +0100 schrieb Pavel Sanda: > I think we can safely go for it. > Given that we already have two overlay item in the menu, we might > want to group > them at the end of insert menu? Done. Jürgen > > Pavel signature.asc Description: This is a digitally signed

Re: Beamer usage again

On 12/30/2017 05:52 AM, José Abílio Matos wrote: > > On Saturday, 30 December 2017 10.40.19 WET Jürgen Spitzmüller wrote: > > > Right. I am talking about the layout format here, though. > > > > > > Jürgen > >   > > Oops. :-) > > You are right. > >   > > IIRC we have been a little bit more

Re: Beamer usage again

Am Samstag, den 30.12.2017, 21:25 +0900 schrieb Joel Kulesza: > I've pulled (1ff34a97) and tested along with your 9261 patch. It > doesn't appear to work for me as I'd expect; please > see: https://youtu.be/sEIFW9Vo0UY. OK, I see now that it does not make sense to have this separate function. I

Re: Beamer usage again

On 12/30/2017 06:00 AM, Jürgen Spitzmüller wrote: > Am Samstag, den 30.12.2017, 11:30 +0900 schrieb Joel Kulesza: >> I've tried to demonstrate with screen recording what I tried to >> illustrate with my screenshot previously. There are places I can >> position the cursor where the Edit menus vary

Re: Beamer usage again

On Sat, Dec 30, 2017 at 8:52 PM, Jürgen Spitzmüller wrote: > Am Samstag, den 30.12.2017, 20:19 +0900 schrieb Joel Kulesza: > > > I am not sure how to fix the first issue. Actually, the procedure > > > works. The problem ist, though, that an empty new frame is > > > inserted, > > >

Re: Beamer usage again

Am Samstag, den 30.12.2017, 20:19 +0900 schrieb Joel Kulesza: > > I am not sure how to fix the first issue. Actually, the procedure > > works. The problem ist, though, that an empty new frame is > > inserted, > > which is rightly deleted again by the delete empty paragraphs > > mechanism. This is

Re: Beamer usage again

Am Samstag, den 30.12.2017, 20:25 +0900 schrieb Joel Kulesza: > Thank you for the clarification; however, I would leave out the word > environment (I'm not sure what value it's adding for the novice or > average user). I would suggest adding new expanding menus in the > Insert Menu so > > Insert

Re: Beamer usage again

On Sat, Dec 30, 2017 at 8:19 PM, Jürgen Spitzmüller wrote: > Am Samstag, den 30.12.2017, 20:09 +0900 schrieb Joel Kulesza: > > One concern: the language used, while precise, isn't too self- > > descriptive for a LaTeX / LyX novice. My understanding is that part > > of the need

Re: Beamer usage again

On Sat, Dec 30, 2017 at 8:00 PM, Jürgen Spitzmüller wrote: > Am Samstag, den 30.12.2017, 11:30 +0900 schrieb Joel Kulesza: > > Please excuse the typos in: https://youtu.be/yZyx_RaFynU > > > > Please let me know if there is a better way to provide such examples. > > This is

Re: Beamer usage again

Am Samstag, den 30.12.2017, 20:09 +0900 schrieb Joel Kulesza: > One concern: the language used, while precise, isn't too self- > descriptive for a LaTeX / LyX novice. My understanding is that part > of the need for precision stems from covering various environments > (e.g. an inner enumerate

Re: Beamer usage again

On Sat, Dec 30, 2017 at 7:14 PM, Jürgen Spitzmüller wrote: > Am Samstag, den 30.12.2017, 10:46 +0100 schrieb Pavel Sanda: > > > From what I understand, there is no new string that would be added. > > > The > > > question is just about the translations of the help documents. Is > >

Re: Beamer usage again

Am Samstag, den 30.12.2017, 11:30 +0900 schrieb Joel Kulesza: > Please excuse the typos in: https://youtu.be/yZyx_RaFynU > > Please let me know if there is a better way to provide such examples. This is excellent, thank you for the efforts. > I've tried to demonstrate with screen recording what

Re: Beamer usage again

On Saturday, 30 December 2017 10.40.19 WET Jürgen Spitzmüller wrote: > Right. I am talking about the layout format here, though. > > Jürgen Oops. :-) You are right. IIRC we have been a little bit more permissive in this case. :-) Happy new year. :-) -- José Abílio

Re: Beamer usage again

Am Samstag, den 30.12.2017, 10:32 + schrieb José Abílio Matos: > The invariant in our stable series was always to keep the same file > format. In my humble opinion this is a very good practice and > something that we should continue. Right. I am talking about the layout format here, though.

Re: Beamer usage again

On Saturday, 30 December 2017 10.14.53 WET Jürgen Spitzmüller wrote: > Note, further, that this entails a layout format change. I am not sure > what our current policy is wrt introducing this within a stable series. > If we don't do that, no for 2.3.0 would mean no for 2.3.x. > > Jürgen The

Re: Beamer usage again

Am Samstag, den 30.12.2017, 10:46 +0100 schrieb Pavel Sanda: > > From what I understand, there is no new string that would be added. > > The > > question is just about the translations of the help documents. Is > > that > > right? > > Unfortunately no, there is another new string for prepending

Re: Beamer usage again

Am Samstag, den 30.12.2017, 10:44 +0100 schrieb Pavel Sanda: > I do not see how this patch affects things out of beamer scope It applies to all environments with a label. But I think they all benefit from the improvement. Jürgen signature.asc Description: This is a digitally signed message part

Re: Beamer usage again

Jürgen Spitzmüller wrote: > Am Donnerstag, den 28.12.2017, 22:58 +0100 schrieb Pavel Sanda: > > We can definitely do it in the master. > > Any objections to this? I think we can safely go for it. Given that we already have two overlay item in the menu, we might want to group them at the end of

Re: Beamer usage again

Scott Kostyshak wrote: > On Thu, Dec 28, 2017 at 09:58:23PM +, Pavel Sanda wrote: > > Jürgen Spitzmüller wrote: > > > >a) one looks into insert menu, but starting new beamer environment > > > > is hidden in edit menu once it appears, not intuitive > > > > > > Moving this to Insert is the

Re: Beamer usage again

Jürgen Spitzmüller wrote: > Am Freitag, den 29.12.2017, 09:52 +0100 schrieb Jürgen Spitzmüller: > > Exactly. Frame is the thing to use if you need just a standard > > paragraph (nested standard is practically the same). > > > > The on-screen display is sub-optimal, which leads to irritation. See

Re: Beamer usage again

On Thu, Dec 28, 2017 at 09:58:23PM +, Pavel Sanda wrote: > Jürgen Spitzmüller wrote: > > >a) one looks into insert menu, but starting new beamer environment > > > is hidden in edit menu once it appears, not intuitive > > > > Moving this to Insert is the easiest thing. I don't have a

Re: Beamer usage again

On Sat, Dec 30, 2017 at 12:45 AM, Jürgen Spitzmüller wrote: > Am Freitag, den 29.12.2017, 22:16 +0900 schrieb Joel Kulesza: > > When within the Frame (e.g., I've typed my last itemize bullet), > > Append new parent environment works as expected. However, if after > > having made

Re: Beamer usage again

Am Freitag, den 29.12.2017, 21:54 +0900 schrieb Joel Kulesza: > Thank you for the quick and extensive work to address several of > these beamer issues! Given all that, I've downloaded/compiled master > @3a4b233d. The issue I'm commenting on is shown in the attached > screenshot. To reproduce: >

Re: Beamer usage again

Am Freitag, den 29.12.2017, 22:16 +0900 schrieb Joel Kulesza: > When within the Frame (e.g., I've typed my last itemize bullet), > Append new parent environment works as expected. However, if after > having made additional modifications, there are a couple positions > that the cursor can exist

Re: Beamer usage again

Am Freitag, den 29.12.2017, 09:52 +0100 schrieb Jürgen Spitzmüller: > Exactly. Frame is the thing to use if you need just a standard > paragraph (nested standard is practically the same). > > The on-screen display is sub-optimal, which leads to irritation. See >

Re: Beamer usage again

Jürgen Spitzmüller wrote: > I don't know either. In any case, I will trac all these changes so we > have them recorded for potential later backports. Thanks Juergen for your prompt feedback :) Pavel

Re: Beamer usage again

Am Donnerstag, den 28.12.2017, 17:14 -0500 schrieb Richard Heck: > Yes, it works just like Theorem. Note that the Frame environment does > NOT need to be nested, whereas Standard does have to be. This takes a > little getting used to, but in the end I think it works. Exactly. Frame is the thing

Re: Beamer usage again

Am Donnerstag, den 28.12.2017, 22:58 +0100 schrieb Pavel Sanda: > We can definitely do it in the master. Any objections to this? > The change looks valuable enough to have it in 2.3 as well, > but we already added new string I do not know whether we'd get > green light from Scott? I don't know

Re: Beamer usage again

Am Donnerstag, den 28.12.2017, 23:07 +0100 schrieb Pavel Sanda: > Now I see what you mean. Is the fact that enter in frame environment > leads to > new line with (again) frame environment instead of (say) standard > environment > intentional? Yes. Jürgen > > Pavel signature.asc Description:

Re: Beamer usage again

On 12/28/2017 05:07 PM, Pavel Sanda wrote: > Pavel Sanda wrote: >> Jürgen Spitzmüller wrote: >>> Am Donnerstag, den 28.12.2017, 10:24 +0100 schrieb Jürgen Spitzmüller: >b) maybe there is some visual way to signalize that nesting is needed? I thought about something like auto-nesting.

Re: Beamer usage again

Pavel Sanda wrote: > Jürgen Spitzmüller wrote: > > Am Donnerstag, den 28.12.2017, 10:24 +0100 schrieb Jürgen Spitzmüller: > > > >b) maybe there is some visual way to signalize that nesting is > > > > needed? > > > > > > I thought about something like auto-nesting. But this is certainly > > >

Re: Beamer usage again

Pavel Sanda wrote: > Jürgen Spitzmüller wrote: > > > > 1. Can't find way how to insert new slide. > > > >b) if one breaks proper nesting in already existing slide the menu > > > > option completely disappears so one has no clue whether such option > > > > even exists in lyx > > > > maybe

Re: Beamer usage again

Jürgen Spitzmüller wrote: > >a) one looks into insert menu, but starting new beamer environment > > is hidden in edit menu once it appears, not intuitive > > Moving this to Insert is the easiest thing. I don't have a strong > preference on this, but take care to do it at a point where the >

Re: Beamer usage again

Jürgen Spitzmüller wrote: > Am Donnerstag, den 28.12.2017, 10:24 +0100 schrieb Jürgen Spitzmüller: > > >b) maybe there is some visual way to signalize that nesting is needed? > > > > I thought about something like auto-nesting. But this is certainly > > tricky to implement. > > Done in

Re: Beamer usage again

Jürgen Spitzmüller wrote: > Am Donnerstag, den 28.12.2017, 10:24 +0100 schrieb Jürgen Spitzmüller: > > >c) what is the fastest way how to add new beamer slide when one is > > > in the _begining_ of slides? > > > 'Start New Environment' just breaks the first slide instead of > > >

Re: Beamer usage again

Jürgen Spitzmüller wrote: > > > 1. Can't find way how to insert new slide. > > >b) if one breaks proper nesting in already existing slide the menu > > > option completely disappears so one has no clue whether such option > > > even exists in lyx > > > maybe we can have disable menu

Re: Beamer usage again

Am Donnerstag, den 28.12.2017, 10:26 +0100 schrieb Jürgen Spitzmüller: > Am Donnerstag, den 28.12.2017, 13:54 +0900 schrieb Joel Kulesza: > > Another point of feedback that was brought to me from a new-ish but > > enthusiastic and savvy LyX user: once a new slide/frame is inserted > > and the

Re: Beamer usage again

Am Donnerstag, den 28.12.2017, 10:24 +0100 schrieb Jürgen Spitzmüller: > >b) maybe there is some visual way to signalize that nesting is > > needed? > > I thought about something like auto-nesting. But this is certainly > tricky to implement. Done in master. Please test. Jürgen

Re: Beamer usage again

Am Donnerstag, den 28.12.2017, 10:24 +0100 schrieb Jürgen Spitzmüller: > >c) what is the fastest way how to add new beamer slide when one > is > > in the _begining_ of slides? > > 'Start New Environment' just breaks the first slide instead > of > > creating a new one. > > I need to

Re: Beamer usage again

Am Donnerstag, den 28.12.2017, 10:24 +0100 schrieb Jürgen Spitzmüller: > Am Donnerstag, den 28.12.2017, 05:27 +0100 schrieb Pavel Sanda: > > The major issues I experienced right now: > > 1. Can't find way how to insert new slide. > >b) if one breaks proper nesting in already existing slide the

Re: Beamer usage again

Am Donnerstag, den 28.12.2017, 13:54 +0900 schrieb Joel Kulesza: > Another point of feedback that was brought to me from a new-ish but > enthusiastic and savvy LyX user: once a new slide/frame is inserted > and the frame title is entered, going to a new line and hitting > keeps the Frame

Re: Beamer usage again

Am Donnerstag, den 28.12.2017, 05:27 +0100 schrieb Pavel Sanda: > The major issues I experienced right now: > 1. Can't find way how to insert new slide. >b) if one breaks proper nesting in already existing slide the menu > option completely disappears so one has no clue whether such option >

Re: Beamer usage again

On Thu, Dec 28, 2017 at 1:27 PM, Pavel Sanda wrote: > Hi Juergen, > > ... > > I do not expect that all the points raised above have some solution, but > if we > can make at least some of them more obvious that would be improvement IMHO. I've also been meaning to write some

Beamer usage again

Hi Juergen, I am sorry if any of these points was already raised but even though I already did some slides within the new framework months back working with it again was so unintuitive that I needed to read beamer manual again just to start even simplest slides. Maybe we could do better? The