Re: beamer editing

[Edwin Leuven]

On 20 Apr 2017, at 22:47, Guillaume MM  wrote:
> 
> At the time I reviewed your patch and pointed out regressions of the new
> behaviour: .

i don’t see any of those regressions 

(unless i misunderstood you)

> I also suggested to introduce instead a new layout that uses
> flex insets for frames, to solve this exact issue. It is now available
> at . I had positive feedback about
> it on the general list. Would you like to give it a try?

it’s editing wise definitely an improvement!

(and aesthetically a minor regression ;-)

best, ed.

Re: beamer editing

[Edwin Leuven]

On 20 Apr 2017, at 10:08, Jürgen Spitzmüller <sp...@lyx.org> wrote:
> Am Donnerstag, den 20.04.2017, 09:40 +0200 schrieb Edwin Leuven:
>> quite some time ago i complained about editing frame content in lyx
>> 
>> …
>> i think the desired/expected behavior is that  preserves the
>> identing and environment
>> 
>> and that  only resets things if the line is empty
> 
> I think your proposal makes sense at least for the beamer case.

feel free to apply the patch ;-)

ed.

beamer editing

[Edwin Leuven]

hello,

quite some time ago i complained about editing frame content in lyx

basic frame content is indented and has a standard environment

a new line  however removes the indent and resets the standard 
environment to frame

to continue editing one has to re-ident and reset the environment, which is imo 
disruptive and unnecessary

i think the desired/expected behavior is that  preserves the identing 
and environment

and that  only resets things if the line is empty

(just like in itemize) 

at the time i send in the attached little patch

i was wondering what you think about the suggested behavior, and whether you 
have some comments on the patch

it would be nice to have this fixed for 2.3

regards, edwin





depth.diff
Description: Binary data

Re: GUI changes for inserting citations in 2.2x

[Edwin Leuven]

what about adding above the right pane a “search” combobox where the matching 
items would show up in a dropdown list as you type, and hitting enter would add 
the top/selected match to the selected citations

the search options could then be in a tabwidget

(not sure i like dialogs that resize ;-)

?

ed.



> On 09 Sep 2016, at 10:33, Jürgen Spitzmüller  wrote:
> 
> Am Freitag, den 09.09.2016, 09:23 +0200 schrieb Jean-Marc Lasgouttes:
>> What happens when options are expanded on a 800x600 screen? 
> 
> The dialog expands the screen. However, it can be collapsed again after
> the options have been set, so this is IMHO bearable.
> 
>> Could the 
>> options be put in a menu instead ? Since there is no text entry
>> field, 
>> this seems doable. I do not know whether Qt has some special UI for 
>> menus-in-dialogs.
> 
> I am not sure. Sounds like unusual UI to me. We could move it in a sub-
> dialog, but that sounds rather clumsy as well.
> 
> Jürgen
> 
>> 
>> JMarc

Re: Wishlist for future LyX

[Edwin Leuven]

On 03 Jun 2016, at 18:35, Helge Hafting  wrote:
> 
> Now that we have 2.2.0,

I love the new shiny lyx on my retina screen

congrats on a great job!

> here are some wishes for the future:

Hide changes (in lyx)

...

Fwiw ;-)

Re: Status on Mac with El Capitan

[Edwin Leuven]

On 05 Jan 2016, at 02:13, Stephan Witt  wrote:
> Hi Lyxers,
> 
> it’s a long overdue task I had on my ToDo list: 
> the update of my system to latest OS X - El Capitan.
> 
> It’s accompanied by an update of many components including the
> development tools, the compiler, the IDE, etc.
> 
> The situation after doing so is as follows:
> 
> 2. The build with cmake is broken in two different ways

i can build with

cmake ../lyx  -DLYX_USE_QT=QT5 -DLYX_ENABLE_CXX11=ON -GXcode

Re: beamer workflow

[Edwin Leuven]

On 15 Dec 2015, at 18:36, Kornel Benko <kor...@lyx.org> wrote:
> Am Dienstag, 15. Dezember 2015 um 12:31:26, schrieb Scott Kostyshak 
> <skost...@lyx.org>
>> On Tue, Dec 15, 2015 at 03:58:41PM +0100, Edwin Leuven wrote:
>>> On 12 Nov 2015, at 13:38, Jürgen Spitzmüller <sp...@lyx.org> wrote:
>>>> 2015-11-12 10:43 GMT+01:00 Edwin Leuven:
>>>> but even so, perhaps we should consider the behaviour that we have with 
>>>> itemize:
>>>> 
>>>>  preserves indent, and  on an empty itemize decreases indent
>>>> 
>>>> we could do the same with nesting no?
>>>> 
>>>> i think that would be natural
>>>> 
>>>> I agree.
>>> 
>>> what about the attached?
>> 
>> I do not see an attachment.
> 
> It is there, hidden between the html parts.

another try:



depth.diff
Description: Binary data

Re: beamer workflow

[Edwin Leuven]

On 12 Nov 2015, at 13:38, Jürgen Spitzmüller <sp...@lyx.org> wrote:2015-11-12 10:43 GMT+01:00 Edwin Leuven:
but even so, perhaps we should consider the behaviour that we have with itemize:

 preserves indent, and  on an empty itemize decreases indent

we could do the same with nesting no?

i think that would be naturalI agree.what about the attached?

depth.diff
Description: Binary data

Re: beamer workflow

[Edwin Leuven]

On 11 Nov 2015, at 19:07, Jürgen Spitzmüller <sp...@lyx.org> wrote:
> Am Dienstag 10 November 2015, 10:21:02 schrieb Edwin Leuven:
>> dear all,
>> 
>> when i insert a new frame, add the title and hit enter the new line is set
>> to “Frame”
> 
>> similarly if i am editing the contents of my frame which is an indented
>> standard environment enter gives me a new line set to “Frame”
> 
>> is it possible to have the environment default to “Standard" in these two
>> cases?
> 
>> i think the current default basically never makes sense, or am i missing
>> something?
> 
> Frame is just fine. It behaves equivalently to (nested) standard.

thanks Jürgen, but in my experience Frame does not behave the same as nested 
Standard

once i start add for example an Itemize my slide is all messed up (both the 
alignment, and a a new slide is added)

also, when i then exit the Itemize with a double  the new environment is 
now a Standard even though i started with a Frame

things get very messy

my slide layout is however as i expect it to be when i put the content in a 
nested Standard (which the manual also recommends)

so atm i need to reset Frame to Standard and increasing the nesting every time 
i add a line to my slide

this is interrupting my workflow, and my thought was that this could be avoided 
if LyX would default to having a nested Standard as the default environment in 
a Frame

but again, perhaps i am missing something?

regards, edwin

Re: beamer workflow

[Edwin Leuven]

On 12 Nov 2015, at 10:32, Jürgen Spitzmüller <sp...@lyx.org> wrote:
> 2015-11-12 10:19 GMT+01:00 Edwin Leuven:
> 
> thanks Jürgen, but in my experience Frame does not behave the same as nested 
> Standard
> 
> once i start add for example an Itemize my slide is all messed up (both the 
> alignment, and a a new slide is added)
> 
> Itemize is not Standard. All except Frame need to be nested (as documented).
>  
> 
> also, when i then exit the Itemize with a double  the new environment 
> is now a Standard even though i started with a Frame
> 
> As far as the LaTeX output is concerned, this makes no difference to 
> non-nested Frame. So it's just a cosmetic issue in the workarea. But maybe we 
> should indeed reset to Frame rather than Standard here to avoid confusion.

yes, that would be cleaner

> things get very messy
> 
> my slide layout is however as i expect it to be when i put the content in a 
> nested Standard (which the manual also recommends)
> 
> so atm i need to reset Frame to Standard and increasing the nesting every 
> time i add a line to my slide
> 
> Use Alt+Return to maintain the nesting level.

ah, i didn’t know that

but even so, perhaps we should consider the behaviour that we have with itemize:

 preserves indent, and  on an empty itemize decreases indent

we could do the same with nesting no?

i think that would be natural


> this is interrupting my workflow, and my thought was that this could be 
> avoided if LyX would default to having a nested Standard as the default 
> environment in a Frame
> 
> I thought about this, too. But I think it's not easy to implement this in a 
> sane way.

a pity, so there’s no “environment_on_enter” among the layout options?

thanks, ed.

beamer workflow

[Edwin Leuven]

dear all,

when i insert a new frame, add the title and hit enter the new line is set to 
“Frame”

similarly if i am editing the contents of my frame which is an indented 
standard environment enter gives me a new line set to “Frame”

is it possible to have the environment default to “Standard" in these two cases?

i think the current default basically never makes sense, or am i missing 
something?

thanks, ed.

ps. recently made the switch from 2.0 to 2.2dev because of the font trouble, 
you did a great job on 2.2dev which seems already very stable!

Re: screen indenting after frames

[Edwin Leuven]

On 06 Nov 2015, at 08:34, Jürgen Spitzmüller <sp...@lyx.org> wrote:
> Am Donnerstag 05 November 2015, 18:57:52 schrieb Edwin Leuven:
>> i agree
>> 
>> may i suggest that you push this change to master?
> 
> I've pushed something similar.

great

> Might be something to consider for branch.

yes please

best, ed.

Re: screen indenting after frames

[Edwin Leuven]

On 05 Nov 2015, at 18:27, Jürgen Spitzmüller <sp...@lyx.org> wrote:
> Am Mittwoch 04 November 2015, 10:28:38 schrieb Edwin Leuven:
>> atm when using beamer the text is indented after a new frame:
>> 
>> Frame  [title]
>> 
>> ->|Text starts here
>> 
>> and with a fragile frame it is indented even more
>> 
>> Frame (fragile)  [title]
>> 
>> >|Text starts here
> 
> This is due to the "Margin Dynamic" setting in the Frame style definition.
> 
> A probably better choice might be
> 
> Margin First_Dynamic
> LeftMargin “M"

i agree

may i suggest that you push this change to master?

thanks, edwin

screen indenting after frames

[Edwin Leuven]

dear all,

atm when using beamer the text is indented after a new frame:

Frame  [title]

->|Text starts here

and with a fragile frame it is indented even more

Frame (fragile)  [title]

>|Text starts here


not only is the unequal indenting across different frame types ugly,
but i find this indenting more in general a waste of screen estate

i was therefore wondering whether there is a way to get rid of it altogether?

thanks, edwin

ident itemize regression

[Edwin Leuven]

suppose i have

* a
* b
* c

in lyx 2.0 if i select the lines with ‘b' and ‘c’ and hit tab they get 
indented once:

* a
  - b
  - c

in lyx 2.2 (perhaps 2.1 as well) however ‘c’ gets indented twice:

* a
  - b
# c

ed.

Re: ident itemize regression

[Edwin Leuven]

On Jun 5, 2015, at 12:23 , Jürgen Spitzmüller sp...@lyx.org wrote:
 Qt5 bug. Will be fixed in Qt 5.5. See
 http://www.lyx.org/trac/ticket/9218 http://www.lyx.org/trac/ticket/9218

good to know, thanks

ident itemize regression

[Edwin Leuven]

suppose i have

* a
* b
* c

in lyx 2.0 if i select the lines with ‘b' and ‘c’ and hit  they get 
indented once:

* a
  - b
  - c

in lyx 2.2 (perhaps 2.1 as well) however ‘c’ gets indented twice:

* a
  - b
# c

ed.

Re: ident itemize regression

[Edwin Leuven]

On Jun 5, 2015, at 12:23 , Jürgen Spitzmüller  wrote:
> Qt5 bug. Will be fixed in Qt 5.5. See
> http://www.lyx.org/trac/ticket/9218 

good to know, thanks

tab in tables

[Edwin Leuven]

hitting the tab key in a table makes the cursor skip 4(!) cells

i tried to see what is causing this, but didn’t manage to track it down

perhaps someone can have a look?

thanks, edwin

Re: tab in tables

[Edwin Leuven]

On Apr 5, 2015, at 08:51 , Liviu Andronic landronim...@gmail.com wrote:
 What LyX version, OS, and can you provide a minimal .lyx document
 exhibiting this issue?

trunk, osx, and i just add a new table, put the cursor in and hit tab

thanks, ed.

tab in tables

[Edwin Leuven]

hitting the tab key in a table makes the cursor skip 4(!) cells

i tried to see what is causing this, but didn’t manage to track it down

perhaps someone can have a look?

thanks, edwin

Re: tab in tables

[Edwin Leuven]

On Apr 5, 2015, at 08:51 , Liviu Andronic  wrote:
> What LyX version, OS, and can you provide a minimal .lyx document
> exhibiting this issue?

trunk, osx, and i just add a new table, put the cursor in and hit tab

thanks, ed.

Re: tabular cell merge bug

[Edwin Leuven]

On Mar 24, 2015, at 10:58 , Jean-Marc Lasgouttes lasgout...@lyx.org wrote:
 OK, I committed your patch, and as soon as you feel like it, please ask for 
 commit rights. Then you will get to write your commit messages :)

thanks, i will

regards, ed.

Re: tabular cell merge bug

[Edwin Leuven]

On Mar 24, 2015, at 09:54 , Jürgen Spitzmüller sp...@lyx.org wrote:
 2015-03-24 9:31 GMT+01:00 Edwin Leuven
 can someone commit?
 
 Did you lose your commit rights?

yes, with the move to git

 That could be fixed ;-)

but i am such a happy lurker ;-)

now that i have lyx compiling again i may scratch the occasional itch, or 
squash a rare bug

but i suspect that my contributions will be incidental at best…

regards, ed.

Re: tabular cell merge bug

[Edwin Leuven]

On Mar 23, 2015, at 15:40 , Richard Heck rgh...@lyx.org wrote:
 On 03/23/2015 06:15 AM, Edwin Leuven wrote:
 
 the attached patch fixes it for me…
 
 Makes sense.

can someone commit?

i suspect it can also go into branch...

regards, ed.

Re: tabular cell merge bug

[Edwin Leuven]

On Mar 23, 2015, at 15:40 , Richard Heck <rgh...@lyx.org> wrote:
> On 03/23/2015 06:15 AM, Edwin Leuven wrote:
>> 
>> the attached patch fixes it for me…
> 
> Makes sense.

can someone commit?

i suspect it can also go into branch...

regards, ed.

Re: tabular cell merge bug

[Edwin Leuven]

On Mar 24, 2015, at 09:54 , Jürgen Spitzmüller <sp...@lyx.org> wrote:
> 2015-03-24 9:31 GMT+01:00 Edwin Leuven
> can someone commit?
> 
> Did you lose your commit rights?

yes, with the move to git

> That could be fixed ;-)

but i am such a happy lurker ;-)

now that i have lyx compiling again i may scratch the occasional itch, or 
squash a rare bug

but i suspect that my contributions will be incidental at best…

regards, ed.

Re: tabular cell merge bug

[Edwin Leuven]

On Mar 24, 2015, at 10:58 , Jean-Marc Lasgouttes  wrote:
> OK, I committed your patch, and as soon as you feel like it, please ask for 
> commit rights. Then you will get to write your commit messages :)

thanks, i will

regards, ed.

Re: tabular cell merge bug

[Edwin Leuven]

Le 17/03/2015 21:26, Edwin Leuven a écrit :
 first i merge the top-left two cells in a small, say 3x3, table
 
 if i then merge this multicolumn cell with the remaining cell in the
 first row, my table ends up all bonkers


the attached patch fixes it for me…



tabularbug.diff
Description: Binary data

Re: tabular cell merge bug

[Edwin Leuven]

Le 17/03/2015 21:26, Edwin Leuven a écrit :
> first i merge the top-left two cells in a small, say 3x3, table
> 
> if i then merge this multicolumn cell with the remaining cell in the
> first row, my table ends up all bonkers


the attached patch fixes it for me…



tabularbug.diff
Description: Binary data

Re: [PATCH] LyX HiDPI support in OS X with Qt 5

[Edwin Leuven]

On Oct 18, 2014, at 17:32 , Stephan Witt st.w...@gmx.net wrote:
 Here is a first version for an evaluation of the feature:
 
 https://dl.dropboxusercontent.com/u/27842660/LyX-2.2.0dev-a09eaf44%2Bqt5-x86_64-cocoa.dmg
  
 https://dl.dropboxusercontent.com/u/27842660/LyX-2.2.0dev-a09eaf44+qt5-x86_64-cocoa.dmg
looks great, but does not recognize my latex installation...

thanks for the effort!

edwin

Re: [PATCH] LyX HiDPI support in OS X with Qt 5

[Edwin Leuven]

On Oct 18, 2014, at 17:32 , Stephan Witt  wrote:
> Here is a first version for an evaluation of the feature:
> 
> https://dl.dropboxusercontent.com/u/27842660/LyX-2.2.0dev-a09eaf44%2Bqt5-x86_64-cocoa.dmg
>  
> 
looks great, but does not recognize my latex installation...

thanks for the effort!

edwin

Re: Is it possible to get the old behavior of Flex insets (before the fix for #8442)?

[Edwin Leuven]

On Apr 30, 2014, at 21:33 , Jürgen Spitzmüller sp...@lyx.org wrote:
 2014-04-30 21:02 GMT+02:00 Scott Kostyshak:
 This came up here:
 http://tex.stackexchange.com/questions/174447/lyx-how-to-hide-text-style-labels-by-default/174543#174543
   […]
 we probably need to provide a choice.

only show when the cursor is in the inset?

...and congrats with the baby (2.1 and real ones)!

Re: Is it possible to get the old behavior of Flex insets (before the fix for #8442)?

[Edwin Leuven]

On Apr 30, 2014, at 21:33 , Jürgen Spitzmüller  wrote:
> 2014-04-30 21:02 GMT+02:00 Scott Kostyshak:
> This came up here:
> http://tex.stackexchange.com/questions/174447/lyx-how-to-hide-text-style-labels-by-default/174543#174543
>   […]
> we probably need to provide a choice.

only show when the cursor is in the inset?

...and congrats with the baby (2.1 and real ones)!

layout file question

[Edwin Leuven]

hi guys,

i am putting together a layout file for a local letter class file we use

my latex file should look like this:

\documentclass{ourletter}
\signature{My name}
\begin{document}
\begin{letter}{An \\ Address \\ Here}
\opening{Dear,}
Some text here
\closing{Sincerely,}
\cc{Someone}
\end{letter} 
\end{document}

i was wondering whether it is possible to handle the stuff in the preamble like

\signature{My name}

through a layout in the main text?

thanks!

regards, ed.

Re: layout file question

[Edwin Leuven]

On Feb 7, 2014, at 10:49 , Jürgen Spitzmüller sp...@lyx.org wrote:
 Edwin Leuven wrote:
 i was wondering whether it is possible to handle the stuff in the preamble
 like
 
 \signature{My name}
 
 through a layout in the main text?
 
 Yes. Use
 
 InPreamble  1
 
 in the layout definition.

why didn’t i find that?!

thanks!

regards, ed.

layout file question

[Edwin Leuven]

hi guys,

i am putting together a layout file for a local letter class file we use

my latex file should look like this:

\documentclass{ourletter}
\signature{My name}
\begin{document}
\begin{letter}{An \\ Address \\ Here}
\opening{Dear,}
Some text here
\closing{Sincerely,}
\cc{Someone}
\end{letter} 
\end{document}

i was wondering whether it is possible to handle the stuff in the preamble like

\signature{My name}

through a layout in the main text?

thanks!

regards, ed.

Re: layout file question

[Edwin Leuven]

On Feb 7, 2014, at 10:49 , Jürgen Spitzmüller <sp...@lyx.org> wrote:
> Edwin Leuven wrote:
>> i was wondering whether it is possible to handle the stuff in the preamble
>> like
>> 
>> \signature{My name}
>> 
>> through a layout in the main text?
> 
> Yes. Use
> 
> InPreamble  1
> 
> in the layout definition.

why didn’t i find that?!

thanks!

regards, ed.

Re: menu bar lost in OS X

[Edwin Leuven]

On Jan 29, 2014, at 09:06 , Stephan Witt st.w...@gmx.net wrote:
 I've made a new disk image with a hopefully fixed LyX 2.0.7 and put it here:
 
 https://dl.dropboxusercontent.com/u/27842660/LyX-2.0.7-1%2Bqt4-carbon.dmg
 https://dl.dropboxusercontent.com/u/27842660/LyX-2.0.7-1%2Bqt4-carbon.dmg.sig
 
 It's named LyX 2.0.7-1 to be different at first glance.
 
 It would be nice if someone able to test it would do so.

hi stephan,

this fixes the dynamic menus also for me

thanks for doing such an outstanding job on the osx version of lyx, it is 
really appreciated!

regards, ed.

Re: menu bar lost in OS X

[Edwin Leuven]

On Jan 29, 2014, at 09:06 , Stephan Witt  wrote:
> I've made a new disk image with a hopefully fixed LyX 2.0.7 and put it here:
> 
> https://dl.dropboxusercontent.com/u/27842660/LyX-2.0.7-1%2Bqt4-carbon.dmg
> https://dl.dropboxusercontent.com/u/27842660/LyX-2.0.7-1%2Bqt4-carbon.dmg.sig
> 
> It's named LyX 2.0.7-1 to be different at first glance.
> 
> It would be nice if someone able to test it would do so.

hi stephan,

this fixes the dynamic menus also for me

thanks for doing such an outstanding job on the osx version of lyx, it is 
really appreciated!

regards, ed.

Re: Where is insert branch in 2.0.7?

[Edwin Leuven]

am i the only one with a missing insert-table float in the menu?

(i only can insert the wrap floats)

ed.

Re: Where is insert branch in 2.0.7?

[Edwin Leuven]

On Jan 28, 2014, at 11:27 , Jean-Marc Lasgouttes lasgout...@lyx.org wrote:
 28/01/2014 11:24, Edwin Leuven:
 am i the only one with a missing insert-table float in the menu?
 
 (i only can insert the wrap floats)
 
 I see InsertFloatTable in both 2.0.7 and 2.1.0git

how odd! 

btw, did you compile 2.0.7 yourself?

(i use stephan’s installer)

reverting back to 2.0.6 fixes the problem for me.

oh, and i should’ve said that i am on OSX...

ed.

Re: Where is insert branch in 2.0.7?

[Edwin Leuven]

On Jan 28, 2014, at 11:50 , Jean-Marc Lasgouttes lasgout...@lyx.org wrote:
 28/01/2014 11:44, Edwin Leuven:
 (i use stephan’s installer)
 
 reverting back to 2.0.6 fixes the problem for me.
 
 oh, and i should’ve said that i am on OSX...
 
 Wait for the 2.0.7.1 release, then (it contains some fixes wrt Mac OS X 
 menus).

i was under the impression that the installer from Stephan’s email from the 
25th (which i used) contained those fixes:

https://dl.dropboxusercontent.com/u/27842660/LyX-2.0.7-p1%2Bqt4-cocoa.dmg

but i will wait …

thanks, ed.

Re: Where is insert branch in 2.0.7?

[Edwin Leuven]

am i the only one with a missing insert->table float in the menu?

(i only can insert the wrap floats)

ed.

Re: Where is insert branch in 2.0.7?

[Edwin Leuven]

On Jan 28, 2014, at 11:27 , Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote:
> 28/01/2014 11:24, Edwin Leuven:
>> am i the only one with a missing insert->table float in the menu?
>> 
>> (i only can insert the wrap floats)
> 
> I see Insert>Float>Table in both 2.0.7 and 2.1.0git

how odd! 

btw, did you compile 2.0.7 yourself?

(i use stephan’s installer)

reverting back to 2.0.6 fixes the problem for me.

oh, and i should’ve said that i am on OSX...

ed.

Re: Where is insert branch in 2.0.7?

[Edwin Leuven]

On Jan 28, 2014, at 11:50 , Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote:
> 28/01/2014 11:44, Edwin Leuven:
>> (i use stephan’s installer)
>> 
>> reverting back to 2.0.6 fixes the problem for me.
>> 
>> oh, and i should’ve said that i am on OSX...
> 
> Wait for the 2.0.7.1 release, then (it contains some fixes wrt Mac OS X 
> menus).

i was under the impression that the installer from Stephan’s email from the 
25th (which i used) contained those fixes:

https://dl.dropboxusercontent.com/u/27842660/LyX-2.0.7-p1%2Bqt4-cocoa.dmg

but i will wait …

thanks, ed.

regular crashes on OSX

[Edwin Leuven]

hi guys,

i have been experiencing regular crashes on my mac (see below)

they seem to happen when i open or close a document, but not in a systematic 
way (or at least i haven't found a reproducible way to trigger the bug)

am i the only one experiencing these?

i am using lyx 2.0.5 from the official installer

thanks, ed.



Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   QtGui   0x00eac9c9 QAction::isEnabled() const + 
9
1   QtGui   0x00e95bb4 
qt_mac_set_modal_state_helper_recursive(NSMenu*, NSMenu*, bool) + 244
2   QtGui   0x00e95c9c 
qt_mac_set_modal_state_helper_recursive(NSMenu*, NSMenu*, bool) + 476
3   QtGui   0x00e95e1e 
qt_mac_set_modal_state(NSMenu*, bool) + 62
4   QtGui   0x00e993c8 
QMenuBarPrivate::macUpdateMenuBarImmediatly() + 1144
5   libobjc.A.dylib 0x99a82586 -[NSObject performSelector:] 
+ 62
6   QtGui   0x00e677f9 
-[NSApplication(QApplicationIntegration) qt_sendPostedMessage:] + 89
7   QtGui   0x00e676b6 
-[NSApplication(QApplicationIntegration) qt_sendEvent:] + 118
8   QtGui   0x00e67871 -[QNSApplication sendEvent:] 
+ 49
9   com.apple.AppKit0x9273069c -[NSApplication run] + 951
10  QtGui   0x00e71802 
QEventDispatcherMac::processEvents(QFlagsQEventLoop::ProcessEventsFlag) + 1570
11  QtCore  0x00d12a61 
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) + 65
12  QtCore  0x00d12d8a 
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) + 170
13  QtCore  0x00d14120 QCoreApplication::exec() + 
176
14  org.lyx.lyx 0x00103a6f lyx::Lexer::Pimpl::~Pimpl() 
+ 29605
15  org.lyx.lyx 0x00017a17 
boost::exception_detail::copy_boost_exception(boost::exception*, 
boost::exception const*) + 929
16  org.lyx.lyx 0x0001782f 
boost::exception_detail::copy_boost_exception(boost::exception*, 
boost::exception const*) + 441
17  org.lyx.lyx 0x0001775d 
boost::exception_detail::copy_boost_exception(boost::exception*, 
boost::exception const*) + 231

growing menu

[Edwin Leuven]

everytime i close a document, i get a new reconfigure item in the LyX menu on 
my mac

again: am i alone?

thanks, ed.

regular crashes on OSX

[Edwin Leuven]

hi guys,

i have been experiencing regular crashes on my mac (see below)

they seem to happen when i open or close a document, but not in a systematic 
way (or at least i haven't found a reproducible way to trigger the bug)

am i the only one experiencing these?

i am using lyx 2.0.5 from the official installer

thanks, ed.



Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   QtGui   0x00eac9c9 QAction::isEnabled() const + 
9
1   QtGui   0x00e95bb4 
qt_mac_set_modal_state_helper_recursive(NSMenu*, NSMenu*, bool) + 244
2   QtGui   0x00e95c9c 
qt_mac_set_modal_state_helper_recursive(NSMenu*, NSMenu*, bool) + 476
3   QtGui   0x00e95e1e 
qt_mac_set_modal_state(NSMenu*, bool) + 62
4   QtGui   0x00e993c8 
QMenuBarPrivate::macUpdateMenuBarImmediatly() + 1144
5   libobjc.A.dylib 0x99a82586 -[NSObject performSelector:] 
+ 62
6   QtGui   0x00e677f9 
-[NSApplication(QApplicationIntegration) qt_sendPostedMessage:] + 89
7   QtGui   0x00e676b6 
-[NSApplication(QApplicationIntegration) qt_sendEvent:] + 118
8   QtGui   0x00e67871 -[QNSApplication sendEvent:] 
+ 49
9   com.apple.AppKit0x9273069c -[NSApplication run] + 951
10  QtGui   0x00e71802 
QEventDispatcherMac::processEvents(QFlags) + 1570
11  QtCore  0x00d12a61 
QEventLoop::processEvents(QFlags) + 65
12  QtCore  0x00d12d8a 
QEventLoop::exec(QFlags) + 170
13  QtCore  0x00d14120 QCoreApplication::exec() + 
176
14  org.lyx.lyx 0x00103a6f lyx::Lexer::Pimpl::~Pimpl() 
+ 29605
15  org.lyx.lyx 0x00017a17 
boost::exception_detail::copy_boost_exception(boost::exception*, 
boost::exception const*) + 929
16  org.lyx.lyx 0x0001782f 
boost::exception_detail::copy_boost_exception(boost::exception*, 
boost::exception const*) + 441
17  org.lyx.lyx 0x0001775d 
boost::exception_detail::copy_boost_exception(boost::exception*, 
boost::exception const*) + 231

growing menu

[Edwin Leuven]

everytime i close a document, i get a new "reconfigure" item in the LyX menu on 
my mac

again: am i alone?

thanks, ed.

Re: Source view window

[Edwin Leuven]

On May 5, 2013, at 08:22 , Pavel Sanda sa...@lyx.org wrote:
 Pavel Sanda wrote:
 There are still quirks with not enough minimum size.
 
 I finally solved those too, fixed few typos and it's now in.

could also go into branch i suppose… 

ed.

Re: Source view window

[Edwin Leuven]

On 05/05/2013 06:01 AM, Pavel Sanda wrote:
 Edwin Leuven wrote:
 On May 5, 2013, at 08:22 , Pavel Sanda sa...@lyx.org wrote:
 Pavel Sanda wrote:
 There are still quirks with not enough minimum size.
 I finally solved those too, fixed few typos and it's now in.
 could also go into branch i suppose?
 Not so sure, I had to do nasty things in vim in order to push boxlayout back 
 into ui file since my designer (qt 4.8) seem not to provide this layout (you 
 use qt 5?). It may have implications for older qt version we claim to support 
 in 2.0 series.


no i use 4.8.4

in the patch i send, i used QHBoxLayout (which inherits from QBoxLayout) and 
that worked fine for me…

ed.

Re: Source view window

[Edwin Leuven]

On May 5, 2013, at 08:22 , Pavel Sanda  wrote:
> Pavel Sanda wrote:
>> There are still quirks with not enough minimum size.
> 
> I finally solved those too, fixed few typos and it's now in.

could also go into branch i suppose… 

ed.

Re: Source view window

[Edwin Leuven]

On 05/05/2013 06:01 AM, Pavel Sanda wrote:
> Edwin Leuven wrote:
>> On May 5, 2013, at 08:22 , Pavel Sanda <sa...@lyx.org> wrote:
>>> Pavel Sanda wrote:
>>>> There are still quirks with not enough minimum size.
>>> I finally solved those too, fixed few typos and it's now in.
>> could also go into branch i suppose?
> Not so sure, I had to do nasty things in vim in order to push boxlayout back 
> into ui file since my designer (qt 4.8) seem not to provide this layout (you 
> use qt 5?). It may have implications for older qt version we claim to support 
> in 2.0 series.


no i use 4.8.4

in the patch i send, i used QHBoxLayout (which inherits from QBoxLayout) and 
that worked fine for me…

ed.

Re: Source view window

[Edwin Leuven]

On May 3, 2013, at 01:02 , Richard Heck rgh...@lyx.org wrote:
 On 05/02/2013 06:16 PM, Tommaso Cucinotta wrote:
 On 02/05/13 20:52, Howard Rudd wrote:
 I hope you don't mind me making a suggestion for a very small tweak that I 
 think would be an improvement?
 It is very welcome, indeed! And what you say is burdening others as well!
 
 I just dropped this request into a ticket
 
   http://www.lyx.org/trac/ticket/8653
 
 so that we don't forget about it!
 
 This would be easy to do...if we knew how to do it. How can we get these 
 widgets to reflow themselves to the bottom or something? Can we find out how 
 wide and tall, catch a signal when our size changes, and then reset 
 everything? I would guess this had to be done programmatically, rather than 
 in Qt Designer?

like in attached



viewsource.diff
Description: Binary data

Re: Source view window

[Edwin Leuven]

On May 3, 2013, at 01:02 , Richard Heck  wrote:
> On 05/02/2013 06:16 PM, Tommaso Cucinotta wrote:
>> On 02/05/13 20:52, Howard Rudd wrote:
>>> I hope you don't mind me making a suggestion for a very small tweak that I 
>>> think would be an improvement?
>> It is very welcome, indeed! And what you say is burdening others as well!
>> 
>> I just dropped this request into a ticket
>> 
>>   http://www.lyx.org/trac/ticket/8653
>> 
>> so that we don't forget about it!
> 
> This would be easy to do...if we knew how to do it. How can we get these 
> widgets to reflow themselves to the bottom or something? Can we find out how 
> wide and tall, catch a signal when our size changes, and then reset 
> everything? I would guess this had to be done programmatically, rather than 
> in Qt Designer?

like in attached



viewsource.diff
Description: Binary data

Re: Need help doing bisection for scrolling problem on OS X

[Edwin Leuven]

On Jan 8, 2013, at 16:03 , Stephan Witt st.w...@gmx.net wrote:
 Reading your linker error message I'd say you build LyX with 64bit, but you 
 don't have a matching iconv library. That's strange, because your system 
 library (in /usr/lib) should at least provide i386 and x86_64.

i had a similar problem and need to pass 

-DLIBINTL_INCLUDE_DIR=/opt/local/include

to cmake

i now build with

cmake -G Xcode ../lyx  -DLYX_EXTERNAL_LIBINTL=ON 
-DLIBINTL_INCLUDE_DIR=/opt/local/include -DLYX_PROGRAM_SUFFIX=OFF 
-DLYX_PACKAGE_SUFFIX=OFF -DLYX_RELEASE=ON -DLYX_DMG=ON -DLYX_INSTALL=ON 
-DLYX_COCOA=ON

which seems to work fine

edwin

Re: Need help doing bisection for scrolling problem on OS X

[Edwin Leuven]

On Jan 8, 2013, at 16:03 , Stephan Witt  wrote:
> Reading your linker error message I'd say you build LyX with 64bit, but you 
> don't have a matching iconv library. That's strange, because your system 
> library (in /usr/lib) should at least provide i386 and x86_64.

i had a similar problem and need to pass 

-DLIBINTL_INCLUDE_DIR=/opt/local/include

to cmake

i now build with

cmake -G "Xcode" ../lyx  -DLYX_EXTERNAL_LIBINTL=ON 
-DLIBINTL_INCLUDE_DIR=/opt/local/include -DLYX_PROGRAM_SUFFIX=OFF 
-DLYX_PACKAGE_SUFFIX=OFF -DLYX_RELEASE=ON -DLYX_DMG=ON -DLYX_INSTALL=ON 
-DLYX_COCOA=ON

which seems to work fine

edwin

Re: Expected behavior of set bottom line in tabular?

[Edwin Leuven]

On Dec 9, 2012, at 21:24 , Scott Kostyshak skost...@lyx.org wrote:
 The only thing that seems a little inconsistent to me now is that the
 Set bottom line button toggles on and off (and the data member is
 set). But then again it's not clear that this is wrong. If you set the
 bottom line and then unset the top line of the cell below, the line
 stays. So in that sense it does serve some purpose (although I'm not
 sure that purpose is clear to the user). In the end, I have no clear
 opinion and I think things work smoothly as is.

it has been like this since the beginning of (lyx) time

it would be a good to get rid of such latex idiosyncrasies in the lyx ui

at one point i was planning to add a linestyle combo to the table tool bar (and 
dialog) and remove the superfluous line members

this would get rid of the ambiguous toggling of line below and line above of 
the cell below, and that for the whole row, to get a double line

i vaguely remember that i could not decide how to store the line info, in the 
cells or separately, and after that i got sidetracked…

edwin

Re: Expected behavior of "set bottom line" in tabular?

[Edwin Leuven]

On Dec 9, 2012, at 21:24 , Scott Kostyshak  wrote:
> The only thing that seems a little inconsistent to me now is that the
> "Set bottom line" button toggles on and off (and the data member is
> set). But then again it's not clear that this is wrong. If you set the
> bottom line and then unset the top line of the cell below, the line
> stays. So in that sense it does serve some purpose (although I'm not
> sure that purpose is clear to the user). In the end, I have no clear
> opinion and I think things work smoothly as is.

it has been like this since the beginning of (lyx) time

it would be a good to get rid of such latex idiosyncrasies in the lyx ui

at one point i was planning to add a linestyle combo to the table tool bar (and 
dialog) and remove the superfluous line members

this would get rid of the ambiguous toggling of line below and line above of 
the cell below, and that for the whole row, to get a double line

i vaguely remember that i could not decide how to store the line info, in the 
cells or separately, and after that i got sidetracked…

edwin

building lyx on osx

[Edwin Leuven]

hi guys, 

i recently got a mac, and am now trying to build lyx using Xcode  cmake. 

there seems to be some problem with linking iconv though. 

i was wondering whether there are some recent build instructions for osx?

also, did someone manage to make lyx look decent on a retina display?

thanks, edwin

Re: building lyx on osx

[Edwin Leuven]

On Jul 20, 2012, at 12:20 , Kornel Benko wrote:
 Am Freitag, 20. Juli 2012 um 11:05:27, schrieb Edwin Leuven 
 e.leu...@gmail.com
  there seems to be some problem with linking iconv though. 
  
 What problems?

i pasted the error message below. 

looks like iconv is not 64bit

ed.



Ld /Users/edwin/devel/lyx-build/bin/Debug/lyxclient2.1 normal x86_64
cd /Users/edwin/devel/lyx
setenv MACOSX_DEPLOYMENT_TARGET 10.7

/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++
 -arch x86_64 -isysroot 
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.7.sdk
 -L/Users/edwin/devel/lyx-build/bin/Debug 
-L/Users/edwin/devel/lyx-build/lib/Debug/Debug 
-L/Users/edwin/devel/lyx-build/lib/Debug -L/opt/local/lib/Debug 
-L/opt/local/lib -F/Users/edwin/devel/lyx-build/bin/Debug -F/Library/Frameworks 
-filelist 
/Users/edwin/devel/lyx-build/src/client/lyx.build/Debug/lyxclient2.1.build/Objects-normal/x86_64/lyxclient2.1.LinkFileList
 -mmacosx-version-min=10.7 -Wl,-search_paths_first 
-Wl,-headerpad_max_install_names 
/Users/edwin/devel/lyx-build/lib/Debug/libsupport.a 
/Users/edwin/devel/lyx-build/lib/Debug/libboost_signals.a 
/Users/edwin/devel/lyx-build/lib/Debug/libboost_regex.a 
/opt/local/lib/libintl.dylib /opt/local/lib/libiconv.dylib -framework QtCore 
-framework QtGui -framework AppKit /opt/local/lib/libz.dylib -lobjc -framework 
CoreFoundation -framework AppKit -o 
/Users/edwin/devel/lyx-build/bin/Debug/lyxclient2.1

ld: warning: directory not found for option 
'-L/Users/edwin/devel/lyx-build/lib/Debug/Debug'
ld: warning: directory not found for option '-L/opt/local/lib/Debug'
Undefined symbols for architecture x86_64:
  _iconv_open, referenced from:
  lyx::IconvProcessor::init() in libsupport.a(unicode.o)
  _iconv, referenced from:
  lyx::IconvProcessor::convert(char const*, unsigned long, char*, unsigned 
long) in libsupport.a(unicode.o)
 (maybe you meant: __ZN3lyx19from_iconv_encodingERKSsS1_, 
__ZN3lyx17to_iconv_encodingERKSbIwSt11char_traitsIwESaIwEERKSs )
  _iconv_close, referenced from:
  lyx::IconvProcessor::convert(char const*, unsigned long, char*, unsigned 
long) in libsupport.a(unicode.o)
  lyx::IconvProcessor::Impl::~Impl() in libsupport.a(unicode.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

building lyx on osx

[Edwin Leuven]

hi guys, 

i recently got a mac, and am now trying to build lyx using Xcode & cmake. 

there seems to be some problem with linking iconv though. 

i was wondering whether there are some recent build instructions for osx?

also, did someone manage to make lyx look decent on a retina display?

thanks, edwin

Re: building lyx on osx

[Edwin Leuven]

On Jul 20, 2012, at 12:20 , Kornel Benko wrote:
> Am Freitag, 20. Juli 2012 um 11:05:27, schrieb Edwin Leuven 
> <e.leu...@gmail.com>
> > there seems to be some problem with linking iconv though. 
>  
> What problems?

i pasted the error message below. 

looks like iconv is not 64bit

ed.



Ld /Users/edwin/devel/lyx-build/bin/Debug/lyxclient2.1 normal x86_64
cd /Users/edwin/devel/lyx
setenv MACOSX_DEPLOYMENT_TARGET 10.7

/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++
 -arch x86_64 -isysroot 
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.7.sdk
 -L/Users/edwin/devel/lyx-build/bin/Debug 
-L/Users/edwin/devel/lyx-build/lib/Debug/Debug 
-L/Users/edwin/devel/lyx-build/lib/Debug -L/opt/local/lib/Debug 
-L/opt/local/lib -F/Users/edwin/devel/lyx-build/bin/Debug -F/Library/Frameworks 
-filelist 
/Users/edwin/devel/lyx-build/src/client/lyx.build/Debug/lyxclient2.1.build/Objects-normal/x86_64/lyxclient2.1.LinkFileList
 -mmacosx-version-min=10.7 -Wl,-search_paths_first 
-Wl,-headerpad_max_install_names 
/Users/edwin/devel/lyx-build/lib/Debug/libsupport.a 
/Users/edwin/devel/lyx-build/lib/Debug/libboost_signals.a 
/Users/edwin/devel/lyx-build/lib/Debug/libboost_regex.a 
/opt/local/lib/libintl.dylib /opt/local/lib/libiconv.dylib -framework QtCore 
-framework QtGui -framework AppKit /opt/local/lib/libz.dylib -lobjc -framework 
CoreFoundation -framework AppKit -o 
/Users/edwin/devel/lyx-build/bin/Debug/lyxclient2.1

ld: warning: directory not found for option 
'-L/Users/edwin/devel/lyx-build/lib/Debug/Debug'
ld: warning: directory not found for option '-L/opt/local/lib/Debug'
Undefined symbols for architecture x86_64:
  "_iconv_open", referenced from:
  lyx::IconvProcessor::init() in libsupport.a(unicode.o)
  "_iconv", referenced from:
  lyx::IconvProcessor::convert(char const*, unsigned long, char*, unsigned 
long) in libsupport.a(unicode.o)
 (maybe you meant: __ZN3lyx19from_iconv_encodingERKSsS1_, 
__ZN3lyx17to_iconv_encodingERKSbIwSt11char_traitsIwESaIwEERKSs )
  "_iconv_close", referenced from:
  lyx::IconvProcessor::convert(char const*, unsigned long, char*, unsigned 
long) in libsupport.a(unicode.o)
  lyx::IconvProcessor::Impl::~Impl() in libsupport.a(unicode.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

push selection to search dialog

[Edwin Leuven]

hi,

atm our (quick) search shows an empy dialog (or the text from a
previous search) when hitting ctrl+F

it is standard behavior to put selected text (if any) in the search dialog

the attached patch does this

comments/suggestions?

ed.


x.diff
Description: Binary data

push selection to search dialog

[Edwin Leuven]

hi,

atm our (quick) search shows an empy dialog (or the text from a
previous search) when hitting ctrl+F

it is standard behavior to put selected text (if any) in the search dialog

the attached patch does this

comments/suggestions?

ed.


x.diff
Description: Binary data

Re: Image Lifecycle (Create) Patch - Video

[Edwin Leuven]

Tommaso Cucinotta tomm...@lyx.org wrote:
 Comments ?

no offense, but i think this feature is bloat...

best, edwin

Re: Image Lifecycle (Create) Patch - Video

[Edwin Leuven]

Tommaso Cucinotta  wrote:
> Comments ?

no offense, but i think this "feature" is bloat...

best, edwin

Re: Image Lifecycle (Create) Patch - Video

[Edwin Leuven]

Tommaso Cucinotta tomm...@lyx.org wrote:
 actually, in the previous patch on the Trac by Vincent (which I discovered
 later, when I seeked for a place on Trac where to drop my own patch), the
 mouse coordinates are used to decide where to actually drop.

that's how it should be. could you use that code in your patch?

 Even though, I don't know if that patch gives you the usual visual
 feedback (I guess you're referring to a kind of cursor showing in the
 document where the image is being placed while you're dragging it before
 dropping).

yes

ed.

Re: Image Lifecycle (Create) Patch - Video

[Edwin Leuven]

Tommaso Cucinotta  wrote:
> actually, in the previous patch on the Trac by Vincent (which I discovered
> later, when I seeked for a place on Trac where to drop my own patch), the
> mouse coordinates are used to decide where to actually drop.

that's how it should be. could you use that code in your patch?

> Even though, I don't know if that patch gives you the "usual visual
> feedback" (I guess you're referring to a kind of cursor showing in the
> document where the image is being placed while you're dragging it before
> dropping).

yes

ed.

Re: Image Lifecycle (Create) Patch - Video

[Edwin Leuven]

Tommaso Cucinotta tomm...@lyx.org wrote:
  This patch allows one to quickly insert new images
  and other type of external material into a LyX document.

fwiw, i'd rather be able to drag-n-drop

ed.

Re: Image Lifecycle (Create) Patch - Video

[Edwin Leuven]

Tommaso Cucinotta  wrote:
>  This patch allows one to quickly insert new images
>  and other type of external material into a LyX document.

fwiw, i'd rather be able to drag-n-drop

ed.

Re: first step of merging the Win installers

[Edwin Leuven]

On Mon, May 23, 2011 at 06:17, Uwe Stöhr uwesto...@web.de wrote:
 - I replaced the LaTeX check and installation routine with my installer for
 the following reasons:

when i use your installer it gets stuck at the checking stage. i
killed it after 30mins.

using the installer i build myself using the previous installer code i
don't have this problem

i don't have admin rights on my machine btw

ed.

Re: first step of merging the Win installers

[Edwin Leuven]

On Mon, May 23, 2011 at 06:17, Uwe Stöhr  wrote:
> - I replaced the LaTeX check and installation routine with my installer for
> the following reasons:

when i use your installer it gets stuck at the checking stage. i
killed it after 30mins.

using the installer i build myself using the previous installer code i
don't have this problem

i don't have admin rights on my machine btw

ed.

Re: ANNOUNCE: LyX version 2.0.0 (release candidate 3)

[Edwin Leuven]

Jean Kaplan kap...@apc.univ-paris7.fr wrote:
 A benign remark though : Why did you change some icons in the tool bars: many 
 automatisms have to be rebuilt

because not everybody wants to live in the 1990s for the rest of their lives?

in case of nostalgia or hard to shake habits you can change the icons
to classic in the preferences

edwin

Re: ANNOUNCE: LyX version 2.0.0 (release candidate 3)

[Edwin Leuven]

Jean Kaplan  wrote:
> A benign remark though : Why did you change some icons in the tool bars: many 
> automatisms have to be rebuilt

because not everybody wants to live in the 1990s for the rest of their lives?

in case of nostalgia or hard to shake habits you can change the icons
to "classic" in the preferences

edwin

Re: ESC for aborting long Advanced Find/Replace ops

[Edwin Leuven]

Tommaso Cucinotta tomm...@lyx.org wrote:
 For c), it's a
 complete rewrite, so I'm not considering it for now :-).

but this is the only way to go no?

c is also more likely to happen without a and b, so maybe we should
allow only real fixes and not ad-hoc workarounds (enrico would call it
bloat i suspect) for something that should be fixed at the root...

Re: ESC for aborting long Advanced Find/Replace ops

[Edwin Leuven]

Tommaso Cucinotta  wrote:
> For c), it's a
> complete rewrite, so I'm not considering it for now :-).

but this is the only way to go no?

c is also more likely to happen without a and b, so maybe we should
allow only real fixes and not ad-hoc workarounds (enrico would call it
bloat i suspect) for something that should be fixed at the root...

Re: wrong latex output with decimally aligned columns

[Edwin Leuven]

Richard Heck rgh...@comcast.net wrote:
 Anyway, I'll have a look at the patch later. For now, it looks good, and
 of course we'll also need it for branch.

i applied this

http://www.lyx.org/trac/changeset/38655

ok for branch?

edwin

Re: wrong latex output with decimally aligned columns

[Edwin Leuven]

Richard Heck rgh...@bobjweil.com wrote:
 Edwin Leuven wrote:
 ok for branch?

 Yes, please.

done:

http://www.lyx.org/trac/changeset/38658

Re: wrong latex output with decimally aligned columns

[Edwin Leuven]

Richard Heck  wrote:
> Anyway, I'll have a look at the patch later. For now, it looks good, and
> of course we'll also need it for branch.

i applied this

http://www.lyx.org/trac/changeset/38655

ok for branch?

edwin

Re: wrong latex output with decimally aligned columns

[Edwin Leuven]

Richard Heck <rgh...@bobjweil.com> wrote:
> Edwin Leuven wrote:
>> ok for branch?
>>
> Yes, please.

done:

http://www.lyx.org/trac/changeset/38658

wrong latex output with decimally aligned columns

[Edwin Leuven]

hi guys,

the latex output for decimally aligned columns depends on cached
metrics info (the member decimal_width)

this means that we only get the right output if these members are up-to-date

the attached patch corrects this

in the meantime to be sure to get the proper output one needs to 1)
open all insets, 2) scroll from the beginning to the end, 3) generate
output ... ouch! :(

i don't know why i never was not bitten by this bug before

comments (on the patch that is...)?

edwin


y.patch
Description: Binary data

wrong latex output with decimally aligned columns

[Edwin Leuven]

hi guys,

the latex output for decimally aligned columns depends on cached
metrics info (the member decimal_width)

this means that we only get the right output if these members are up-to-date

the attached patch corrects this

in the meantime to be sure to get the proper output one needs to 1)
open all insets, 2) scroll from the beginning to the end, 3) generate
output ... ouch! :(

i don't know why i never was not bitten by this bug before

comments (on the patch that is...)?

edwin


y.patch
Description: Binary data

Re: Goals for 2.1

[Edwin Leuven]

Enrico Forestieri for...@lyx.org wrote:
 And after I do that they will magically disappear? What I can do is
 voting pro or against a particular feature when it is proposed, but
 it is the majority that wins, and the majority like bloat, apparently.

so what do you think are the top 3 bloat features? (just curious, really)

Re: Goals for 2.1

[Edwin Leuven]

Enrico Forestieri  wrote:
> And after I do that they will magically disappear? What I can do is
> voting pro or against a particular feature when it is proposed, but
> it is the majority that wins, and the majority like bloat, apparently.

so what do you think are the top 3 bloat features? (just curious, really)

Re: Development for LyX 2.1

[Edwin Leuven]

Andre Poenitz andre.poen...@mathematik.tu-chemnitz.de wrote:
 Well, the part I don't get is why suddenly using a version control
 system is considered rocket science. It is not.

 [...]

 With svn there's not much choice but to commit
 early, in order to be ready for the next hunk of work. With git one can
 only commit locally and fix commits later if needed, even after other
 local commits. Or just work exactly the same way as with svn...

i have only been casually been reading this thread, but it seems to me
that as a tool git offers only advantages (for those interested in
using them)

then there is the question what model to use (ie the svn or the git way)

so let's decide to move to git (we loose nothing and gain some),
before having the model discussion?

ed.

Re: Release manager for 2.1

[Edwin Leuven]

yes, great job pavel!!

and i am sure vincent will prove to be an excellent successor...

ed.

Re: Release manager for 2.1

[Edwin Leuven]

Jean-Marc Lasgouttes lasgout...@lyx.org wrote:
 Edwin would describe this as a typical french attitude :)

i think that this particular case says more about how the french
perceive the french, than how the dutch perceive the french ;-)

Re: Development for LyX 2.1

[Edwin Leuven]

Andre Poenitz  wrote:
> Well, the part I don't get is why suddenly using a version control
> system is considered rocket science. It is not.
>
> [...]
>
> With svn there's not much choice but to commit
> early, in order to be ready for the next hunk of work. With git one can
> only commit locally and fix commits later if needed, even after other
> local commits. Or just work exactly the same way as with svn...

i have only been casually been reading this thread, but it seems to me
that as a tool git offers only advantages (for those interested in
using them)

then there is the question what model to use (ie the svn or the git way)

so let's decide to move to git (we loose nothing and gain some),
before having the model discussion?

ed.

Re: Release manager for 2.1

[Edwin Leuven]

yes, great job pavel!!

and i am sure vincent will prove to be an excellent successor...

ed.

Re: Release manager for 2.1

[Edwin Leuven]

Jean-Marc Lasgouttes  wrote:
> Edwin would describe this as a typical french attitude :)

i think that this particular case says more about how the french
perceive the french, than how the dutch perceive the french ;-)

Re: Maintenance release management

[Edwin Leuven]

Abdelrazak Younes you...@lyx.org wrote:
 Excellent solution indeed. Thanks for accepting the duty Richard!

 Many thanks to you; you really did an amazing work!

hear, hear!

ed.

Re: Maintenance release management

[Edwin Leuven]

Abdelrazak Younes  wrote:
> Excellent solution indeed. Thanks for accepting the duty Richard!
>
> Many thanks to you; you really did an amazing work!

hear, hear!

ed.

Re: Towards final 2.0 release

[Edwin Leuven]

Diego Queiroz queiroz.di...@gmail.com wrote:
 I've finally found a way to reproduce a SIGSEGV error:
 http://www.lyx.org/trac/ticket/7492

cannot reproduce with trunk (windows, msvc2010)

ed.

Re: Towards final 2.0 release

[Edwin Leuven]

Diego Queiroz  wrote:
> I've finally found a way to reproduce a SIGSEGV error:
> http://www.lyx.org/trac/ticket/7492

cannot reproduce with trunk (windows, msvc2010)

ed.

Re: [DIAGNOSIS] Re: crash in trunk

[Edwin Leuven]

Richard Heck rgh...@comcast.net:
 What the usual calls to updateBuffer() do is always
 make the macro context a ParIterator that points to
 the first paragraph in the current inset. (See e.g.
 the calls at InsetText:682,695.)

ok. makes me wonder though why it is necessary to set the macro
context explicitly.

 So I'm attaching a few patches:

 1. updateBuffer.diff solves the general problem mentioned.
 2. x2a.patch is what seems to be a working version of x2.patch.
 3. x3a.diff, which is a version of x3.patch that fixes the
 problem in the
 old code.

 I'm not sure what I prefer here, but (1) seems necessary no
 matter what. I
 guess (3) is more cautious, and if there aren't other issues
 for which (2)
 is needed, maybe that's what makes sense.

the main difference between (2) and (3) is the label updating in updateBuffer?

i am working on my document with (1) + (3) here, and have encountered
no problems so far

thanks for helping out with the tricky stuff

ed.

Re: [DIAGNOSIS] Re: crash in trunk

[Edwin Leuven]

Richard Heck :
> What the usual calls to updateBuffer() do is always
> make the macro context a ParIterator that points to
> the first paragraph in the current inset. (See e.g.
> the calls at InsetText:682,695.)

ok. makes me wonder though why it is necessary to set the macro
context explicitly.

> So I'm attaching a few patches:
>
> 1. updateBuffer.diff solves the general problem mentioned.
> 2. x2a.patch is what seems to be a working version of x2.patch.
> 3. x3a.diff, which is a version of x3.patch that fixes the
> problem in the
> old code.
>
> I'm not sure what I prefer here, but (1) seems necessary no
> matter what. I
> guess (3) is more cautious, and if there aren't other issues
> for which (2)
> is needed, maybe that's what makes sense.

the main difference between (2) and (3) is the label updating in updateBuffer?

i am working on my document with (1) + (3) here, and have encountered
no problems so far

thanks for helping out with the tricky stuff

ed.

Re: [DIAGNOSIS] Re: crash in trunk

[Edwin Leuven]

Richard Heck rgh...@comcast.net wrote:
 Answer: No, probably not, because it's hard to see
 how to do this without making copies, which would
 just give us the same problem back again.

the attached avoids the crash for me by setting the macrocontext for
nested insets (and only doing the metrics call on the tail; we don't
need the one on head since we did a metrics call before on the whole
cell)

comments welcome (needed)

i thinks this needs to be fixed before 2.0

ed.


x.patch
Description: Binary data

Re: [DIAGNOSIS] Re: crash in trunk

[Edwin Leuven]

Richard Heck rgh...@comcast.net wrote:
 My main comment would be that I suspect, but of course
 couldn't verify, due to the crashes, that the same
 problem exists in the TexRow() output routine,

i checked that previewing the document and having the source view pane
open worked

my guess was that things are ok as long as there is no metrics call
behind texrow()'s back

but i agree that it is better to fix it in every instance

 Is that sufficient?

i thought that insetList() provided a list of all nested insets...

 What about a Note nested within the Footnote?

...but you're right, it doesn't which means that we will need to
traverse all insets :/

 I wonder if we could try:
    ParagraphList::const_iterator pit =
 tail.getText(0)-paragraphs().begin();
    buffer().updateBuffer(pit, OutputUpdate);

i am not sure i completely follow you, but when i use

buffer().updateBuffer(par_iterator_begin(tail), OutputUpdate);

instead of the code above, the crashes are gone (also with nested insets)

but now i get the asserts below

ed.

17:40:02.216: (file-open C:/Users/Edwin
Leuven/Dropbox/newfile1.lyx)..\..\lyx-devel\src\CursorSlice.cpp(187):
can't compare cursor and anchor in different insets
p:
..\..\..\lyx-devel\src\support\lassert.cpp(21): ASSERTION false
VIOLATED IN ..\..\lyx-devel\src\CursorSlice.cpp:188
..\..\lyx-devel\src\CursorSlice.cpp(187): can't compare cursor and
anchor in different insets
p:
..\..\..\lyx-devel\src\support\lassert.cpp(21): ASSERTION false
VIOLATED IN ..\..\lyx-devel\src\CursorSlice.cpp:188
..\..\lyx-devel\src\CursorSlice.cpp(187): can't compare cursor and
anchor in different insets
p:
..\..\..\lyx-devel\src\support\lassert.cpp(21): ASSERTION false
VIOLATED IN ..\..\lyx-devel\src\CursorSlice.cpp:188
..\..\lyx-devel\src\CursorSlice.cpp(187): can't compare cursor and
anchor in different insets
p:
..\..\..\lyx-devel\src\support\lassert.cpp(21): ASSERTION false
VIOLATED IN ..\..\lyx-devel\src\CursorSlice.cpp:188
..\..\lyx-devel\src\CursorSlice.cpp(187): can't compare cursor and
anchor in different insets
p:
..\..\..\lyx-devel\src\support\lassert.cpp(21): ASSERTION false
VIOLATED IN ..\..\lyx-devel\src\CursorSlice.cpp:188
..\..\lyx-devel\src\CursorSlice.cpp(187): can't compare cursor and
anchor in different insets
p:
..\..\..\lyx-devel\src\support\lassert.cpp(21): ASSERTION false
VIOLATED IN ..\..\lyx-devel\src\CursorSlice.cpp:188
..\..\lyx-devel\src\CursorSlice.cpp(187): can't compare cursor and
anchor in different insets
p:
..\..\..\lyx-devel\src\support\lassert.cpp(21): ASSERTION false
VIOLATED IN ..\..\lyx-devel\src\CursorSlice.cpp:188
..\..\lyx-devel\src\CursorSlice.cpp(187): can't compare cursor and
anchor in different insets
p:
..\..\..\lyx-devel\src\support\lassert.cpp(21): ASSERTION false
VIOLATED IN ..\..\lyx-devel\src\CursorSlice.cpp:188
..\..\lyx-devel\src\CursorSlice.cpp(187): can't compare cursor and
anchor in different insets
p:
..\..\..\lyx-devel\src\support\lassert.cpp(21): ASSERTION false
VIOLATED IN ..\..\lyx-devel\src\CursorSlice.cpp:188
..\..\lyx-devel\src\CursorSlice.cpp(187): can't compare cursor and
anchor in different insets
p:
..\..\..\lyx-devel\src\support\lassert.cpp(21): ASSERTION false
VIOLATED IN ..\..\lyx-devel\src\CursorSlice.cpp:188
..\..\lyx-devel\src\CursorSlice.cpp(187): can't compare cursor and
anchor in different insets
p:
..\..\..\lyx-devel\src\support\lassert.cpp(21): ASSERTION false
VIOLATED IN ..\..\lyx-devel\src\CursorSlice.cpp:188
..\..\lyx-devel\src\CursorSlice.cpp(187): can't compare cursor and
anchor in different insets
p:
..\..\..\lyx-devel\src\support\lassert.cpp(21): ASSERTION false
VIOLATED IN ..\..\lyx-devel\src\CursorSlice.cpp:188
..\..\lyx-devel\src\CursorSlice.cpp(187): can't compare cursor and
anchor in different insets
p:
..\..\..\lyx-devel\src\support\lassert.cpp(21): ASSERTION false
VIOLATED IN ..\..\lyx-devel\src\CursorSlice.cpp:188
..\..\lyx-devel\src\CursorSlice.cpp(187): can't compare cursor and
anchor in different insets
p:
..\..\..\lyx-devel\src\support\lassert.cpp(21): ASSERTION false
VIOLATED IN ..\..\lyx-devel\src\CursorSlice.cpp:188
..\..\lyx-devel\src\CursorSlice.cpp(187): can't compare cursor and
anchor in different insets
p:
..\..\..\lyx-devel\src\support\lassert.cpp(21): ASSERTION false
VIOLATED IN ..\..\lyx-devel\src\CursorSlice.cpp:188
..\..\lyx-devel\src\CursorSlice.cpp(187): can't compare cursor and
anchor in different insets
p:
..\..\..\lyx-devel\src\support\lassert.cpp(21): ASSERTION false
VIOLATED IN ..\..\lyx-devel\src\CursorSlice.cpp:188
..\..\lyx-devel\src\CursorSlice.cpp(187): can't compare cursor and
anchor in different insets
p:
..\..\..\lyx-devel\src\support\lassert.cpp(21): ASSERTION false
VIOLATED IN ..\..\lyx-devel\src\CursorSlice.cpp:188
..\..\lyx-devel\src\CursorSlice.cpp(187): can't compare cursor and
anchor in different insets
p:
..\..\..\lyx-devel\src\support\lassert.cpp(21): ASSERTION false
VIOLATED IN ..\..\lyx-devel\src\CursorSlice.cpp:188
..\..\lyx-devel\src\CursorSlice.cpp(187): can't