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: growing menu

[Pavel Sanda]

Edwin Leuven wrote:
 everytime i close a document, i get a new reconfigure item in the LyX menu 
 on my mac
 
 again: am i alone?

IIRC more times reported and nothing new, try bugzilla or archives.
I even thought that it was already fixed.
Pavel

Re: growing menu

[Stephan Witt]

Am 07.05.2013 um 15:47 schrieb Edwin Leuven e.leu...@gmail.com:

 everytime i close a document, i get a new reconfigure item in the LyX menu 
 on my mac
 
 again: am i alone?

No. This and the crashes are caused by using the Cocoa framework and the code 
moving the menu items from the Tools to the LyX menu. The LyX 2.0.6 release is 
build with Carbon because of these problems. But, yes, I know Carbon is a dead 
end. It has to be corrected for Cocoa too. On my 10.8.3 system Qt-4.8.4 even 
refuses to compile the Carbon API. They have disabled it totally for x86_64 and 
for i386 one gets a compile error.

Another effect is the behavior regarding bug #8538 
(http://www.lyx.org/trac/ticket/8538). The build with Qt-4.8.4-Carbon is not 
affected by this bug. The \Omega is now rendered again.

Regards,
Stephan

Re: growing menu

[Jean-Marc Lasgouttes]

Le 07/05/13 21:46, Stephan Witt a écrit :

Am 07.05.2013 um 15:47 schrieb Edwin Leuven e.leu...@gmail.com:


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

again: am i alone?


No. This and the crashes are caused by using the Cocoa framework and
the code moving the menu items from the Tools to the LyX menu. The
LyX 2.0.6 release is build with Carbon because of these problems.
But, yes, I know Carbon is a dead end. It has to be corrected for
Cocoa too. On my 10.8.3 system Qt-4.8.4 even refuses to compile the
Carbon API. They have disabled it totally for x86_64 and for i386 one
gets a compile error.


I'll try to see if I can handle the double menus thing. Did you try already?


Another effect is the behavior regarding bug #8538
(http://www.lyx.org/trac/ticket/8538). The build with Qt-4.8.4-Carbon
is not affected by this bug. The \Omega is now rendered again.


I remember that we shared some ideas abot fixing Qt for this \omega
problem. Did you find time to try it?

JMarc

Re: growing menu

[Stephan Witt]

Am 07.05.2013 um 21:50 schrieb Jean-Marc Lasgouttes lasgout...@lyx.org:

 Le 07/05/13 21:46, Stephan Witt a écrit :
 Am 07.05.2013 um 15:47 schrieb Edwin Leuven e.leu...@gmail.com:
 
 everytime i close a document, i get a new reconfigure item in the
 LyX menu on my mac
 
 again: am i alone?
 
 No. This and the crashes are caused by using the Cocoa framework and
 the code moving the menu items from the Tools to the LyX menu. The
 LyX 2.0.6 release is build with Carbon because of these problems.
 But, yes, I know Carbon is a dead end. It has to be corrected for
 Cocoa too. On my 10.8.3 system Qt-4.8.4 even refuses to compile the
 Carbon API. They have disabled it totally for x86_64 and for i386 one
 gets a compile error.
 
 I'll try to see if I can handle the double menus thing. Did you try already?

Not really. I think it's simply a bug. It should work.
The Reconfigure menu item has the MenuRole QAction::ApplicationSpecificRole.

 
 Another effect is the behavior regarding bug #8538
 (http://www.lyx.org/trac/ticket/8538). The build with Qt-4.8.4-Carbon
 is not affected by this bug. The \Omega is now rendered again.
 
 I remember that we shared some ideas abot fixing Qt for this \omega
 problem. Did you find time to try it?

Yes, but it was neither funny nor successful. After learning how to debug the
Qt frameworks I thought I can fix it. But
1. I cannot find the location where the font property symbolFont ever gets
assigned a true value. It seems like it's done by comparing some names.
2. Even if I force symbolFont = true where you've spotted it's use it makes no
difference. Obviously, this not the right place or not the only place to fix it.

I'll try to address that again later.

Stephan 

Re: growing menu

[Jean-Marc Lasgouttes]

Le 07/05/13 22:13, Stephan Witt a écrit :

I remember that we shared some ideas abot fixing Qt for this \omega
problem. Did you find time to try it?


Yes, but it was neither funny nor successful. After learning how to debug the
Qt frameworks I thought I can fix it. But
1. I cannot find the location where the font property symbolFont ever gets
assigned a true value. It seems like it's done by comparing some names.
2. Even if I force symbolFont = true where you've spotted it's use it makes no
difference. Obviously, this not the right place or not the only place to fix it.

I'll try to address that again later.


Is there abug report against qt? Shall we file one?

JMarc

Re: growing menu

[Stephan Witt]

Am 07.05.2013 um 23:13 schrieb Jean-Marc Lasgouttes lasgout...@lyx.org:

 Le 07/05/13 22:13, Stephan Witt a écrit :
 I remember that we shared some ideas abot fixing Qt for this \omega
 problem. Did you find time to try it?
 
 Yes, but it was neither funny nor successful. After learning how to debug the
 Qt frameworks I thought I can fix it. But
 1. I cannot find the location where the font property symbolFont ever gets
 assigned a true value. It seems like it's done by comparing some names.
 2. Even if I force symbolFont = true where you've spotted it's use it makes 
 no
 difference. Obviously, this not the right place or not the only place to fix 
 it.
 
 I'll try to address that again later.
 
 Is there abug report against qt? Shall we file one?

I have not searched but this is one possible outcome.

Stephan

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: growing menu

[Pavel Sanda]

Edwin Leuven wrote:
> everytime i close a document, i get a new "reconfigure" item in the LyX menu 
> on my mac
> 
> again: am i alone?

IIRC more times reported and nothing new, try bugzilla or archives.
I even thought that it was already fixed.
Pavel

Re: growing menu

[Stephan Witt]

Am 07.05.2013 um 15:47 schrieb Edwin Leuven :

> everytime i close a document, i get a new "reconfigure" item in the LyX menu 
> on my mac
> 
> again: am i alone?

No. This and the crashes are caused by using the Cocoa framework and the code 
moving the menu items from the Tools to the LyX menu. The LyX 2.0.6 release is 
build with Carbon because of these problems. But, yes, I know Carbon is a dead 
end. It has to be corrected for Cocoa too. On my 10.8.3 system Qt-4.8.4 even 
refuses to compile the Carbon API. They have disabled it totally for x86_64 and 
for i386 one gets a compile error.

Another effect is the behavior regarding bug #8538 
(http://www.lyx.org/trac/ticket/8538). The build with Qt-4.8.4-Carbon is not 
affected by this bug. The \Omega is now rendered again.

Regards,
Stephan

Re: growing menu

[Jean-Marc Lasgouttes]

Le 07/05/13 21:46, Stephan Witt a écrit :

Am 07.05.2013 um 15:47 schrieb Edwin Leuven :


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

again: am i alone?


No. This and the crashes are caused by using the Cocoa framework and
the code moving the menu items from the Tools to the LyX menu. The
LyX 2.0.6 release is build with Carbon because of these problems.
But, yes, I know Carbon is a dead end. It has to be corrected for
Cocoa too. On my 10.8.3 system Qt-4.8.4 even refuses to compile the
Carbon API. They have disabled it totally for x86_64 and for i386 one
gets a compile error.


I'll try to see if I can handle the double menus thing. Did you try already?


Another effect is the behavior regarding bug #8538
(http://www.lyx.org/trac/ticket/8538). The build with Qt-4.8.4-Carbon
is not affected by this bug. The \Omega is now rendered again.


I remember that we shared some ideas abot fixing Qt for this \omega
problem. Did you find time to try it?

JMarc

Re: growing menu

[Stephan Witt]

Am 07.05.2013 um 21:50 schrieb Jean-Marc Lasgouttes :

> Le 07/05/13 21:46, Stephan Witt a écrit :
>> Am 07.05.2013 um 15:47 schrieb Edwin Leuven :
>> 
>>> everytime i close a document, i get a new "reconfigure" item in the
>>> LyX menu on my mac
>>> 
>>> again: am i alone?
>> 
>> No. This and the crashes are caused by using the Cocoa framework and
>> the code moving the menu items from the Tools to the LyX menu. The
>> LyX 2.0.6 release is build with Carbon because of these problems.
>> But, yes, I know Carbon is a dead end. It has to be corrected for
>> Cocoa too. On my 10.8.3 system Qt-4.8.4 even refuses to compile the
>> Carbon API. They have disabled it totally for x86_64 and for i386 one
>> gets a compile error.
> 
> I'll try to see if I can handle the double menus thing. Did you try already?

Not really. I think it's simply a bug. It should work.
The Reconfigure menu item has the MenuRole QAction::ApplicationSpecificRole.

> 
>> Another effect is the behavior regarding bug #8538
>> (http://www.lyx.org/trac/ticket/8538). The build with Qt-4.8.4-Carbon
>> is not affected by this bug. The \Omega is now rendered again.
> 
> I remember that we shared some ideas abot fixing Qt for this \omega
> problem. Did you find time to try it?

Yes, but it was neither funny nor successful. After learning how to debug the
Qt frameworks I thought I can fix it. But
1. I cannot find the location where the font property "symbolFont" ever gets
assigned a true value. It seems like it's done by comparing some names.
2. Even if I force symbolFont = true where you've spotted it's use it makes no
difference. Obviously, this not the right place or not the only place to fix it.

I'll try to address that again later.

Stephan 

Re: growing menu

[Jean-Marc Lasgouttes]

Le 07/05/13 22:13, Stephan Witt a écrit :

I remember that we shared some ideas abot fixing Qt for this \omega
problem. Did you find time to try it?


Yes, but it was neither funny nor successful. After learning how to debug the
Qt frameworks I thought I can fix it. But
1. I cannot find the location where the font property "symbolFont" ever gets
assigned a true value. It seems like it's done by comparing some names.
2. Even if I force symbolFont = true where you've spotted it's use it makes no
difference. Obviously, this not the right place or not the only place to fix it.

I'll try to address that again later.


Is there abug report against qt? Shall we file one?

JMarc

Re: growing menu

[Stephan Witt]

Am 07.05.2013 um 23:13 schrieb Jean-Marc Lasgouttes :

> Le 07/05/13 22:13, Stephan Witt a écrit :
>>> I remember that we shared some ideas abot fixing Qt for this \omega
>>> problem. Did you find time to try it?
>> 
>> Yes, but it was neither funny nor successful. After learning how to debug the
>> Qt frameworks I thought I can fix it. But
>> 1. I cannot find the location where the font property "symbolFont" ever gets
>> assigned a true value. It seems like it's done by comparing some names.
>> 2. Even if I force symbolFont = true where you've spotted it's use it makes 
>> no
>> difference. Obviously, this not the right place or not the only place to fix 
>> it.
>> 
>> I'll try to address that again later.
> 
> Is there abug report against qt? Shall we file one?

I have not searched but this is one possible outcome.

Stephan