Re: Language change within Flex inset exports wrong babel construct

[Jürgen Spitzmüller]

Guenter Milde wrote:
  This white space disappears by properly escaping
  the line breaks in \addto\extrasfrench{...}.
 
 So I hope it is easily fixed for 2.1 (or 2.0.1).

Sure. Just add the % to languages and be done with it.

There are still other whitespace issues, though, with language changes at the 
beginning of quotations and macros. These were already present in 1.6.

Jürgen

Re: #7613: bug in the sweave module with french language

[Guillaume Avenin]

sample file attached
regards
Le 6 juin 2011 à 03:26, LyX Ticket Tracker a écrit :

 #7613: bug in the sweave module with french language
 --+-
 Reporter:  gavenin   |   Owner:  lasgouttes
 Type:  defect|  Status:  new   
 Priority:  normal|   Milestone:
 Component:  literate  | Version:  2.0.0 
 Severity:  normal|Keywords:  infoneeded
 --+-
 Changes (by lasgouttes):
 
  * keywords:  = infoneeded
  * version:  = 2.0.0
  * component:  general = literate
  * severity:  blocker = normal
 
 
 Comment:
 
 Please provide an example document. I do not see this problem.
 
 -- 
 Ticket URL: http://www.lyx.org/trac/ticket/7613#comment:1
 The LyX Project http://www.lyx.org/
 LyX -- The Document Processor

trunk not compilable

[Kornel]

I get this while linking lyx
...
Linking CXX executable ../bin/lyx
cd /usr/BUILD/BuildLyx/src  /usr/bin/cmake -E cmake_link_script 
CMakeFiles/lyx.dir/link.txt --verbose=1 
  
/usr/bin/c++   -Wall -Wunused-parameter -fno-strict-aliasing  -Wall 
-Wunused-parameter -O3 -DNDEBUG   CMakeFiles/lyx.dir/PersonalWordList.cpp.o 
CMakeFiles/lyx.dir/Buffer.cpp.o 
CMakeFiles/lyx.dir/FontInfo.cpp.o CMakeFiles/lyx.dir/ParIterator.cpp.o 
CMakeFiles/lyx.dir/FontList.cpp.o CMakeFiles/lyx.dir/TextMetrics.cpp.o 
CMakeFiles/lyx.dir/HunspellChecker.cpp.o 
CMakeFiles/lyx.dir/ParagraphMetrics.cpp.o CMakeFiles/lyx.dir/TexStream.cpp.o 
CMakeFiles/lyx.dir/EnchantChecker.cpp.o CMakeFiles/lyx.dir/ServerSocket.cpp.o 
CMakeFiles/lyx.dir/main.cpp.o 
CMakeFiles/lyx.dir/CmdDef.cpp.o CMakeFiles/lyx.dir/sgml.cpp.o 
CMakeFiles/lyx.dir/KeyMap.cpp.o CMakeFiles/lyx.dir/Length.cpp.o 
CMakeFiles/lyx.dir/MetricsInfo.cpp.o CMakeFiles/lyx.dir/LyXRC.cpp.o 
CMakeFiles/lyx.dir/ErrorList.cpp.o CMakeFiles/lyx.dir/Spacing.cpp.o 
CMakeFiles/lyx.dir/HSpace.cpp.o CMakeFiles/lyx.dir/InsetIterator.cpp.o 
CMakeFiles/lyx.dir/Floating.cpp.o 
CMakeFiles/lyx.dir/lengthcommon.cpp.o CMakeFiles/lyx.dir/VSpace.cpp.o 
CMakeFiles/lyx.dir/Text.cpp.o CMakeFiles/lyx.dir/output_plaintext.cpp.o 
CMakeFiles/lyx.dir/Compare.cpp.o 
CMakeFiles/lyx.dir/DepTable.cpp.o CMakeFiles/lyx.dir/OutputParams.cpp.o 
CMakeFiles/lyx.dir/Cursor.cpp.o CMakeFiles/lyx.dir/BufferView.cpp.o 
CMakeFiles/lyx.dir/Text2.cpp.o 
CMakeFiles/lyx.dir/LyXAction.cpp.o CMakeFiles/lyx.dir/FuncRequest.cpp.o 
CMakeFiles/lyx.dir/Row.cpp.o CMakeFiles/lyx.dir/WordList.cpp.o 
CMakeFiles/lyx.dir/Author.cpp.o CMakeFiles/lyx.dir/Chktex.cpp.o 
CMakeFiles/lyx.dir/Mover.cpp.o CMakeFiles/lyx.dir/Bidi.cpp.o 
CMakeFiles/lyx.dir/Session.cpp.o CMakeFiles/lyx.dir/Server.cpp.o 
CMakeFiles/lyx.dir/TocBackend.cpp.o CMakeFiles/lyx.dir/CutAndPaste.cpp.o 
CMakeFiles/lyx.dir/BranchList.cpp.o CMakeFiles/lyx.dir/CoordCache.cpp.o 
CMakeFiles/lyx.dir/Thesaurus.cpp.o CMakeFiles/lyx.dir/Text3.cpp.o 
CMakeFiles/lyx.dir/Converter.cpp.o 
CMakeFiles/lyx.dir/ModuleList.cpp.o CMakeFiles/lyx.dir/output_xhtml.cpp.o 
CMakeFiles/lyx.dir/Counters.cpp.o CMakeFiles/lyx.dir/Lexer.cpp.o 
CMakeFiles/lyx.dir/ConverterCache.cpp.o 
CMakeFiles/lyx.dir/output.cpp.o CMakeFiles/lyx.dir/ParagraphParameters.cpp.o 
CMakeFiles/lyx.dir/Box.cpp.o CMakeFiles/lyx.dir/output_latex.cpp.o 
CMakeFiles/lyx.dir/LaTeX.cpp.o 
CMakeFiles/lyx.dir/Exporter.cpp.o CMakeFiles/lyx.dir/boost.cpp.o 
CMakeFiles/lyx.dir/Language.cpp.o CMakeFiles/lyx.dir/Bullet.cpp.o 
CMakeFiles/lyx.dir/factory.cpp.o 
CMakeFiles/lyx.dir/BufferParams.cpp.o CMakeFiles/lyx.dir/Encoding.cpp.o 
CMakeFiles/lyx.dir/version.cpp.o CMakeFiles/lyx.dir/Undo.cpp.o 
CMakeFiles/lyx.dir/rowpainter.cpp.o 
CMakeFiles/lyx.dir/LayoutModuleList.cpp.o CMakeFiles/lyx.dir/lyxfind.cpp.o 
CMakeFiles/lyx.dir/LyX.cpp.o CMakeFiles/lyx.dir/VCBackend.cpp.o 
CMakeFiles/lyx.dir/Paragraph.cpp.o 
CMakeFiles/lyx.dir/Font.cpp.o CMakeFiles/lyx.dir/Graph.cpp.o 
CMakeFiles/lyx.dir/PDFOptions.cpp.o CMakeFiles/lyx.dir/Intl.cpp.o 
CMakeFiles/lyx.dir/KeySequence.cpp.o CMakeFiles/lyx.dir/InsetList.cpp.o 
CMakeFiles/lyx.dir/Color.cpp.o CMakeFiles/lyx.dir/LyXVC.cpp.o 
CMakeFiles/lyx.dir/TexRow.cpp.o CMakeFiles/lyx.dir/BiblioInfo.cpp.o 
CMakeFiles/lyx.dir/buffer_funcs.cpp.o 
CMakeFiles/lyx.dir/FloatList.cpp.o CMakeFiles/lyx.dir/PrinterParams.cpp.o 
CMakeFiles/lyx.dir/IndicesList.cpp.o CMakeFiles/lyx.dir/LayoutFile.cpp.o 
CMakeFiles/lyx.dir/DocIterator.cpp.o 
CMakeFiles/lyx.dir/LaTeXFeatures.cpp.o CMakeFiles/lyx.dir/FuncStatus.cpp.o 
CMakeFiles/lyx.dir/Dimension.cpp.o CMakeFiles/lyx.dir/Trans.cpp.o 
CMakeFiles/lyx.dir/CursorSlice.cpp.o 
CMakeFiles/lyx.dir/Changes.cpp.o CMakeFiles/lyx.dir/output_docbook.cpp.o 
CMakeFiles/lyx.dir/TextClass.cpp.o CMakeFiles/lyx.dir/Format.cpp.o 
CMakeFiles/lyx.dir/BufferList.cpp.o 
CMakeFiles/lyx.dir/Layout.cpp.o  -o ../bin/lyx -rdynamic ../lib/libmathed.a 
../lib/libinsets.a ../lib/libfrontends.a ../lib/libfrontend_qt4.a 
../lib/libgraphics.a ../lib/libsupport.a ../lib/libintl.a 
-lhunspell -lenchant ../lib/libfrontends.a -lQtGui ../lib/libboost_signals.a 
../lib/libboost_regex.a -lQtCore -lz 
../lib/libfrontend_qt4.a(FancyLineEdit.cpp.o): In function 
`lyx::frontend::FancyLineEditPrivate::FancyLineEditPrivate(lyx::frontend::FancyLineEdit*)':
FancyLineEdit.cpp:(.text+0x383): undefined reference to `vtable for 
lyx::frontend::IconButton'
FancyLineEdit.cpp:(.text+0x38b): undefined reference to `vtable for 
lyx::frontend::IconButton'
FancyLineEdit.cpp:(.text+0x415): undefined reference to `vtable for 
lyx::frontend::IconButton'
FancyLineEdit.cpp:(.text+0x41d): undefined reference to `vtable for 
lyx::frontend::IconButton'
../lib/libfrontend_qt4.a(FancyLineEdit.cpp.o): In function 
`lyx::frontend::FancyLineEdit::iconClicked()':
FancyLineEdit.cpp:(.text+0x54c): undefined reference to 
`lyx::frontend::IconButton::staticMetaObject'

Re: trunk not compilable

[Stephan Witt]

Am 06.06.2011 um 13:12 schrieb Kornel:

 I get this while linking lyx
 ...
 Linking CXX executable ../bin/lyx
 cd /usr/BUILD/BuildLyx/src  /usr/bin/cmake -E cmake_link_script 
 CMakeFiles/lyx.dir/link.txt --verbose=1   
 
 /usr/bin/c++   -Wall -Wunused-parameter -fno-strict-aliasing  -Wall 
 -Wunused-parameter -O3 -DNDEBUG   CMakeFiles/lyx.dir/PersonalWordList.cpp.o
 ...
 CMakeFiles/lyx.dir/CursorSlice.cpp.o CMakeFiles/lyx.dir/Changes.cpp.o 
 CMakeFiles/lyx.dir/output_docbook.cpp.o CMakeFiles/lyx.dir/TextClass.cpp.o 
 CMakeFiles/lyx.dir/Format.cpp.o CMakeFiles/lyx.dir/BufferList.cpp.o 
 CMakeFiles/lyx.dir/Layout.cpp.o  -o ../bin/lyx -rdynamic ../lib/libmathed.a 
 ../lib/libinsets.a ../lib/libfrontends.a ../lib/libfrontend_qt4.a 
 ../lib/libgraphics.a ../lib/libsupport.a ../lib/libintl.a -lhunspell 
 -lenchant ../lib/libfrontends.a -lQtGui ../lib/libboost_signals.a 
 ../lib/libboost_regex.a -lQtCore -lz 
 ../lib/libfrontend_qt4.a(FancyLineEdit.cpp.o): In function 
 `lyx::frontend::FancyLineEditPrivate::FancyLineEditPrivate(lyx::frontend::FancyLineEdit*)':
 FancyLineEdit.cpp:(.text+0x383): undefined reference to `vtable for 
 lyx::frontend::IconButton'
 FancyLineEdit.cpp:(.text+0x38b): undefined reference to `vtable for 
 lyx::frontend::IconButton'
 FancyLineEdit.cpp:(.text+0x415): undefined reference to `vtable for 
 lyx::frontend::IconButton'
 FancyLineEdit.cpp:(.text+0x41d): undefined reference to `vtable for 
 lyx::frontend::IconButton'
 ../lib/libfrontend_qt4.a(FancyLineEdit.cpp.o): In function 
 `lyx::frontend::FancyLineEdit::iconClicked()':
 FancyLineEdit.cpp:(.text+0x54c): undefined reference to 
 `lyx::frontend::IconButton::staticMetaObject'
 ../lib/libfrontend_qt4.a(FancyLineEdit.cpp.o): In function 
 `lyx::frontend::IconButton::IconButton(QWidget*)':
 FancyLineEdit.cpp:(.text+0xd25): undefined reference to `vtable for 
 lyx::frontend::IconButton'
 FancyLineEdit.cpp:(.text+0xd2d): undefined reference to `vtable for 
 lyx::frontend::IconButton'
 collect2: ld returned 1 exit status
 ...
 
 The qt-version is 4:4.7.2-0ubuntu6.1 if that matters. Yesterday it was 
 compilable (revision 38960).

I had the same problem. IMHO, you have to recreate your cmake project.

Stephan

Re: Language change within Flex inset exports wrong babel construct

[Guenter Milde]

On 2011-06-06, Jürgen Spitzmüller wrote:
 Guenter Milde wrote:
  This white space disappears by properly escaping
  the line breaks in \addto\extrasfrench{...}.

 So I hope it is easily fixed for 2.1 (or 2.0.1).

 Sure. Just add the % to languages and be done with it.

Here is the patch for lib/languages:

@@ -360,8 +360,8 @@ Language french
LangCode fr_FR
PostBabelPreamble
\addto\extrasfrench{%
-  \providecommand{\og}{\leavevmode\flqq~}
-  \providecommand{\fg}{\ifdim\lastskip\z@\unskip\fi~\frqq}
+  \providecommand{\og}{\leavevmode\flqq~}%
+  \providecommand{\fg}{\ifdim\lastskip\z@\unskip\fi~\frqq}%
}
EndPostBabelPreamble
 End

Please apply to 2.0 and devel.

 There are still other whitespace issues, though, with language changes
 at the beginning of quotations and macros. These were already present
 in 1.6.

Could you be more specific? I could not find more missing line-break
escapes in lib/languages, but there might be more somewhere in the C code.

Thanks,

Günter

Re: trunk not compilable

[Kornel]

Am pondelok 06 Jún 2011 schrieb Stephan Witt:
 Am 06.06.2011 um 13:12 schrieb Kornel:
  I get this while linking lyx
  ...
  Linking CXX executable ../bin/lyx
  cd /usr/BUILD/BuildLyx/src  /usr/bin/cmake -E cmake_link_script
  CMakeFiles/lyx.dir/link.txt --verbose=1 /usr/bin/c++   -Wall
  -Wunused-parameter -fno-strict-aliasing  -Wall -Wunused-parameter -O3
  -DNDEBUG   CMakeFiles/lyx.dir/PersonalWordList.cpp.o ...
  CMakeFiles/lyx.dir/CursorSlice.cpp.o CMakeFiles/lyx.dir/Changes.cpp.o
  CMakeFiles/lyx.dir/output_docbook.cpp.o
  CMakeFiles/lyx.dir/TextClass.cpp.o CMakeFiles/lyx.dir/Format.cpp.o
  CMakeFiles/lyx.dir/BufferList.cpp.o CMakeFiles/lyx.dir/Layout.cpp.o  -o
  ../bin/lyx -rdynamic ../lib/libmathed.a ../lib/libinsets.a
  ../lib/libfrontends.a ../lib/libfrontend_qt4.a ../lib/libgraphics.a
  ../lib/libsupport.a ../lib/libintl.a -lhunspell -lenchant
  ../lib/libfrontends.a -lQtGui ../lib/libboost_signals.a
  ../lib/libboost_regex.a -lQtCore -lz
  ../lib/libfrontend_qt4.a(FancyLineEdit.cpp.o): In function
  `lyx::frontend::FancyLineEditPrivate::FancyLineEditPrivate(lyx::frontend
  ::FancyLineEdit*)': FancyLineEdit.cpp:(.text+0x383): undefined reference
  to `vtable for lyx::frontend::IconButton'
  FancyLineEdit.cpp:(.text+0x38b): undefined reference to `vtable for
  lyx::frontend::IconButton' FancyLineEdit.cpp:(.text+0x415): undefined
  reference to `vtable for lyx::frontend::IconButton'
  FancyLineEdit.cpp:(.text+0x41d): undefined reference to `vtable for
  lyx::frontend::IconButton'
  ../lib/libfrontend_qt4.a(FancyLineEdit.cpp.o): In function
  `lyx::frontend::FancyLineEdit::iconClicked()':
  FancyLineEdit.cpp:(.text+0x54c): undefined reference to
  `lyx::frontend::IconButton::staticMetaObject'
  ../lib/libfrontend_qt4.a(FancyLineEdit.cpp.o): In function
  `lyx::frontend::IconButton::IconButton(QWidget*)':
  FancyLineEdit.cpp:(.text+0xd25): undefined reference to `vtable for
  lyx::frontend::IconButton' FancyLineEdit.cpp:(.text+0xd2d): undefined
  reference to `vtable for lyx::frontend::IconButton' collect2: ld
  returned 1 exit status
  ...
  
  The qt-version is 4:4.7.2-0ubuntu6.1 if that matters. Yesterday it was
  compilable (revision 38960).
 
 I had the same problem. IMHO, you have to recreate your cmake project.
 
 Stephan

I did already with make clean. Tried now to recreate everything, but same 
error.

Kornel


signature.asc
Description: This is a digitally signed message part.

Re: Language change within Flex inset exports wrong babel construct

[Richard Heck]

On 06/06/2011 07:45 AM, Guenter Milde wrote:
 On 2011-06-06, Jürgen Spitzmüller wrote:
 Guenter Milde wrote:
 This white space disappears by properly escaping
 the line breaks in \addto\extrasfrench{...}.
 So I hope it is easily fixed for 2.1 (or 2.0.1).
 Sure. Just add the % to languages and be done with it.
 Here is the patch for lib/languages:

 @@ -360,8 +360,8 @@ Language french
   LangCode fr_FR
   PostBabelPreamble
   \addto\extrasfrench{%
 -\providecommand{\og}{\leavevmode\flqq~}
 -\providecommand{\fg}{\ifdim\lastskip\z@\unskip\fi~\frqq}
 +\providecommand{\og}{\leavevmode\flqq~}%
 +\providecommand{\fg}{\ifdim\lastskip\z@\unskip\fi~\frqq}%
   }
   EndPostBabelPreamble
  End

 Please apply to 2.0 and devel.

Done, thank you.

rh

mathcal vs. mathscr in unicodesymbols

[Guenter Milde]

Dear List,

currently, the lib/unicodesymbols file in the devel branch (because of my
patch at http://www.lyx.org/trac/ticket/7600) uses a mix of \mathscr vs.
\mathcal to represent SCRIPT ... vs. MATHEMATICAL SCRIPT ... unicode
characters.

We have to take a decision:

a) treat the default LaTeX math alphabet \mathcal as a valid 
   MATHEMATICAL SCRIPT alphabet, or
  
b) consider Calligraphic and Script alphabets as distinct entities
   (because \mathscr look more like SCRIPT and the mathrsfs glyphs look
   more like the sample glyphs of the Unicode ... SCRIPT ... characters.
  

I prefer a), because:

* Unicode and MathML define just one mathematical script alphabet.
  (The XITS OpenType math fonts provide the calligraphic letters as a
  stylistic variant - see unicode-math documentation
  http://mirror.ctan.org/macros/latex/contrib/unicode-math/unicode-math.pdf
  .)

* This way capital 'SCRIPT' letters can be mapped without the need of an
  external package - avoids the LyX autoselected packages
  problems.
  
  And without a new math alphabet (also important because of the
  TeX limit of just 16 math alphabets easily hit with advanced math
  typesetting).
  
* The user can select different fonts for \mathcal with one of the packages
  
  eucal  Euler Script font, part of amsmath,
 
  calrsfsRalph Smith's Formal Script via \mathcal instead of 
 \mathscr,
 
  rsfso  Ralph Smith's Formal Script with the slant substantially
 reduced. The output is quite similar to that from the Adobe
 Mathematical Pi script font. 
  
  urwchancal Zapf chancery (also providing small script letters),
  
  as well as with a generic math-font package like fourier (which,
  however, changes all math fonts and the text font).

If there is a consensus, I can provide a patch.
  
Günter

  

Re: mathcal vs. mathscr in unicodesymbols

[Richard Heck]

On 06/06/2011 08:37 AM, Guenter Milde wrote:
 Dear List,

 currently, the lib/unicodesymbols file in the devel branch (because of my
 patch at http://www.lyx.org/trac/ticket/7600) uses a mix of \mathscr vs.
 \mathcal to represent SCRIPT ... vs. MATHEMATICAL SCRIPT ... unicode
 characters.

 We have to take a decision:

 a) treat the default LaTeX math alphabet \mathcal as a valid 
MATHEMATICAL SCRIPT alphabet, or
   
 b) consider Calligraphic and Script alphabets as distinct entities
(because \mathscr look more like SCRIPT and the mathrsfs glyphs look
more like the sample glyphs of the Unicode ... SCRIPT ... characters.
   

 I prefer a), because:
 ...

I do not have a strong preference here, but your reasoning sounds good
to me.

rh

Re: Language change within Flex inset exports wrong babel construct

[Jürgen Spitzmüller]

Guenter Milde wrote:
 Could you be more specific? I could not find more missing line-break
 escapes in lib/languages, but there might be more somewhere in the C code.

I'll try to make a test case when I find time (too busy currently). The issue 
often arises when I use a foreign language for a complete quote or a heading. 
This gives vertical or horizontal unwanted whitespace. Adding an empty ERT 
works around this.

Jürgen

Re: Link Error in Trunk

[Jean-Marc Lasgouttes]

Le 06/06/2011 14:30, Richard Heck a écrit :


CXXLD  lyx
frontends/qt4/liblyxqt4.a(FancyLineEdit.o): In function `IconButton':
/cvs/lyx/src/frontends/qt4/FancyLineEdit.cpp:267: undefined reference to
`vtable for lyx::frontend::IconButton'
/cvs/lyx/src/frontends/qt4/FancyLineEdit.cpp:267: undefined reference to
`vtable for lyx::frontend::IconButton'
frontends/qt4/liblyxqt4.a(FancyLineEdit.o): In function
`qobject_castlyx::frontend::IconButton*':
/usr/include/QtCore/qobject.h:366: undefined reference to
`lyx::frontend::IconButton::staticMetaObject'
collect2: ld returned 1 exit status



What Qt version? Could the problem be r38963? I could not compile with 4.5.

JMarc

trunk not compilable

[Uwe Stöhr]

Due to this change in FancyLineEdit.h:
http://www.lyx.org/trac/changeset/38963
I cannot compile LyX with Qt 4.7 anymore:

release\src\PersonalWordList.obj : warning LNK4042: object specified more than 
once; extras ignored
   Creating library release\lyx.lib and object release\lyx.exp
FancyLineEdit.obj : error LNK2001: unresolved external symbol public: virtual struct QMetaObject 
const * __thiscall lyx::frontend::IconButton::metaObject(void)

const  (?metaObject@IconButton@frontend@lyx@@UBEPBUQMetaObject@@XZ)
FancyLineEdit.obj : error LNK2001: unresolved external symbol public: virtual void * __thiscall 
lyx::frontend::IconButton::qt_metacast(char const *) (?qt_meta 
cast@IconButton@frontend@lyx@@UAEPAXPBD@Z)
FancyLineEdit.obj : error LNK2001: unresolved external symbol public: virtual int __thiscall 
lyx::frontend::IconButton::qt_metacall(enum QMetaObject::Call,int,void * *) 
(?qt_metacall@IconButton@frontend@lyx@@UAEHW4Call@QMetaObject@@HPAPAX@Z)
FancyLineEdit.obj : error LNK2019: unresolved external symbol public: static struct QMetaObject 
const lyx::frontend::IconButton::staticMetaObject 
(?staticMetaObject@IconButton@frontend@lyx@@2UQMetaObject@@B) referenced in function class
lyx::frontend::IconButton * __cdecl qobject_castclass lyx::frontend::IconButton *(class QObject 
*) (??$qobject_cast@PAVIconButton@frontend@lyxYAPAVIconButton@frontend@lyx@@PAVQObject@@@Z)

release\lyx.exe : fatal error LNK1120: 4 unresolved externals
scons: *** [release\lyx.exe] Error 1120
scons: building terminated because of errors.

Without the new #if QT_VERSION = 0x040600 it compiles.

regards Uwe

Re: Link Error in Trunk

[Uwe Stöhr]

Am 06.06.2011 16:28, schrieb Jean-Marc Lasgouttes:


What Qt version? Could the problem be r38963? I could not compile with 4.5.


Sorry, read it too late.

However, I'm using Qt 4.7.3.

regards Uwe

Re: Link Error in Trunk

[Jean-Marc Lasgouttes]

Le 06/06/2011 17:39, Uwe Stöhr a écrit :

Am 06.06.2011 16:28, schrieb Jean-Marc Lasgouttes:


What Qt version? Could the problem be r38963? I could not compile with
4.5.


Sorry, read it too late.

However, I'm using Qt 4.7.3.


Better now?

JMarc

Re: Lyx 2.0.0 OSX Coca version cursor problems (was OSX crashes)

[Murat Yildizoglu]

Just to refresh this thread, I have reinstalled the standard Lyx 2 OSX build
and the cursor problem has been corrected.
So it seems that this problem comes from the Cocoa QT version. Has anybody
else observed this problem with the experimental version proposed by
Stephan?

Murat

2011/6/1 Murat Yildizoglu murat.yildizo...@univ-cezanne.fr

 Hello Stephan,

 I have been using the new OSX binary and I see some strange things going on
 with the cursor: it does not correctly indicate its position (it is always a
 little bit on the right of its actual position), and when I insert or delete
 characters, the operations do not take place at the correct place. The
 problem does not seem to depend on the font  I choose for the screen.

  Do you observe this problem?

 Murat

 2011/5/22 Stephan Witt st.w...@gmx.net

 Am 22.05.2011 um 12:20 schrieb Murat Yildizoglu:

  Hi again,
 
  I see a strange thing with this new build: I can see several
 Reconfigure items in the Lyx menu. Their number even increases : I had two
 of them and I can see three now. Not a big problem, but i prefer to signal
 it.

 Yes, I can it see too. :( Weird...

  2011/5/22 Murat Yildizoglu murat.yildizo...@univ-cezanne.fr
  A very big Woaw and Hurrah! Stephan ;-)

 You're welcome.

  This build solves both my problems:
 
  - I can use Divvy to resize the Lyx window;
  - ForeverSave can now backup Lyx documents.

 Very good.

  Moreover, I have the impression that the launch of Lyx is much quicker
 now.
 
  This is definitely a very nice trick and thank you very much for having
 spent time to solve these small problems.
 
  If we do not find any other problems with this Qt build, I hope that it
 will become the default one to use, since it looks better integrated into
 OSX.

 Yes, we should switch to cocoa based Qt. I think this the root cause why
 Qt 4.7 worked better - it's simply based on cocoa per default.

 Stephan




 --
 Prof. Murat Yildizoglu
 Université Paul Cézanne (Aix-Marseille 3)
 GREQAM (UMR CNRS 6579)
 Centre de la Vieille Charité
 2, rue de la Charité
 13236 Marseille cedex 02

 Bureau 320
 Tel : +33 4 91 14 07 27 (standard)
 Tel : +33 4 91 14 07 70 (secrétariat)
 Tel : +33 4 91 14 07 47 (bureau)
 Fax : +33 4 91 90 02 27

 e-mail: murat.yildizo...@univ-cezanne.fr
 www : http:/yildizoglu.co.cc
 http://www.twitter.com/yildizoglu
 __




-- 
Prof. Murat Yildizoglu
Université Paul Cézanne (Aix-Marseille 3)
GREQAM (UMR CNRS 6579)
Centre de la Vieille Charité
2, rue de la Charité
13236 Marseille cedex 02

Bureau 320
Tel : +33 4 91 14 07 27 (standard)
Tel : +33 4 91 14 07 70 (secrétariat)
Tel : +33 4 91 14 07 47 (bureau)
Fax : +33 4 91 90 02 27

e-mail: murat.yildizo...@univ-cezanne.fr
www : http:/yildizoglu.co.cc
http://www.twitter.com/yildizoglu
__

Re: Link Error in Trunk

[Uwe Stöhr]

Am 06.06.2011 17:53, schrieb Jean-Marc Lasgouttes:


However, I'm using Qt 4.7.3.


Better now?


Sure. But reverting the change in the .h file would have been enough.

regards Uwe

Re: Link Error in Trunk

[Jean-Marc Lasgouttes]

Le 06/06/2011 17:56, Uwe Stöhr a écrit :

Am 06.06.2011 17:53, schrieb Jean-Marc Lasgouttes:


However, I'm using Qt 4.7.3.


Better now?


Sure. But reverting the change in the .h file would have been enough.


It would not link for me anyway...

JMarc

Re: r38969 - lyx-devel/trunk/src/frontends/qt4

[Vincent van Ravesteijn]

On 6-6-2011 17:53, lasgout...@lyx.org wrote:
 Author: lasgouttes
 Date: Mon Jun  6 17:53:43 2011
 New Revision: 38969
 URL: http://www.lyx.org/trac/changeset/38969
 
 Log:
 Revert r38963. Compilation is now broken with qt 4.5, but I do not know Qt 
 moc business and do not have time to investigate.
 


Moc doesn't work if the class is within #if's (a bit strange, but this
seems to be the case). This means you can't put the whole class inside
the #if because compilation with the newest Qt does not work. That's
also the reason I moved the Q_SIGNAL definitions out of the #if clause.

The change in FancyLineEdit.cpp was ok, because one should not #include
QtCore/QPropertyAnimation. I fixed this in 38970.

Why did you also put the #ifs around the IconButton class. I can't see
why this class would not compile on older Qt's.

Vincent

Re: Lyx 2.0.0 OSX Coca version cursor problems (was OSX crashes)

[Stephan Witt]

Am 06.06.2011 um 17:54 schrieb Murat Yildizoglu:

 Just to refresh this thread, I have reinstalled the standard Lyx 2 OSX build 
 and the cursor problem has been corrected.
 So it seems that this problem comes from the Cocoa QT version. Has anybody 
 else observed this problem with the experimental version proposed by Stephan?

I'm almost sure it's Cocoa based Qt that makes the problem. Until your report I 
thought it's the Qt-version what matters.
See the ticket http://www.lyx.org/trac/ticket/6920 and the discussion here 
http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg164633.html

Unfortunately we have a real Scylla versus Charybdis scenario here.

Stephan

 Murat
 
 2011/6/1 Murat Yildizoglu murat.yildizo...@univ-cezanne.fr
 Hello Stephan,
 
 I have been using the new OSX binary and I see some strange things going on 
 with the cursor: it does not correctly indicate its position (it is always a 
 little bit on the right of its actual position), and when I insert or delete 
 characters, the operations do not take place at the correct place. The 
 problem does not seem to depend on the font  I choose for the screen.
 
  Do you observe this problem? 
 
 Murat
 
 2011/5/22 Stephan Witt st.w...@gmx.net
 Am 22.05.2011 um 12:20 schrieb Murat Yildizoglu:
 
  Hi again,
 
  I see a strange thing with this new build: I can see several Reconfigure 
  items in the Lyx menu. Their number even increases : I had two of them and 
  I can see three now. Not a big problem, but i prefer to signal it.
 
 Yes, I can it see too. :( Weird...
 
  2011/5/22 Murat Yildizoglu murat.yildizo...@univ-cezanne.fr
  A very big Woaw and Hurrah! Stephan ;-)
 
 You're welcome.
 
  This build solves both my problems:
 
  - I can use Divvy to resize the Lyx window;
  - ForeverSave can now backup Lyx documents.
 
 Very good.
 
  Moreover, I have the impression that the launch of Lyx is much quicker now.
 
  This is definitely a very nice trick and thank you very much for having 
  spent time to solve these small problems.
 
  If we do not find any other problems with this Qt build, I hope that it 
  will become the default one to use, since it looks better integrated into 
  OSX.
 
 Yes, we should switch to cocoa based Qt. I think this the root cause why Qt 
 4.7 worked better - it's simply based on cocoa per default.
 
 Stephan
 
 
 
 -- 
 Prof. Murat Yildizoglu
 Université Paul Cézanne (Aix-Marseille 3) 
 GREQAM (UMR CNRS 6579)
 Centre de la Vieille Charité
 2, rue de la Charité
 13236 Marseille cedex 02
 
 Bureau 320
 Tel : +33 4 91 14 07 27 (standard)
 Tel : +33 4 91 14 07 70 (secrétariat) 
 Tel : +33 4 91 14 07 47 (bureau)
 Fax : +33 4 91 90 02 27 
 
 e-mail: murat.yildizo...@univ-cezanne.fr
 www : http:/yildizoglu.co.cc
 http://www.twitter.com/yildizoglu
 __
 
 
 
 -- 
 Prof. Murat Yildizoglu
 Université Paul Cézanne (Aix-Marseille 3) 
 GREQAM (UMR CNRS 6579)
 Centre de la Vieille Charité
 2, rue de la Charité
 13236 Marseille cedex 02
 
 Bureau 320
 Tel : +33 4 91 14 07 27 (standard)
 Tel : +33 4 91 14 07 70 (secrétariat) 
 Tel : +33 4 91 14 07 47 (bureau)
 Fax : +33 4 91 90 02 27 
 
 e-mail: murat.yildizo...@univ-cezanne.fr
 www : http:/yildizoglu.co.cc
 http://www.twitter.com/yildizoglu
 __

Re: Lyx 2.0.0 OSX Coca version cursor problems (was OSX crashes)

[Murat Yildizoglu]

Well, if the only problems with the official Lyx release concern Divvy and
ForeverSave, we can get away with the QT version used by it. We can hold
from using Divvy to resize the Lyx window (in my case it does not crash Lyx,
the windows just ignores Divvy) and a functionality similar to ForeverSave
(saving and versioning) will be included in Lion, at the system level, if I
understand well the discussion on the net. I just hope that this will be
compatible with QT and Lyx.

2011/6/6 Stephan Witt st.w...@gmx.net

 Am 06.06.2011 um 17:54 schrieb Murat Yildizoglu:

  Just to refresh this thread, I have reinstalled the standard Lyx 2 OSX
 build and the cursor problem has been corrected.
  So it seems that this problem comes from the Cocoa QT version. Has
 anybody else observed this problem with the experimental version proposed by
 Stephan?

 I'm almost sure it's Cocoa based Qt that makes the problem. Until your
 report I thought it's the Qt-version what matters.
 See the ticket http://www.lyx.org/trac/ticket/6920 and the discussion here
 http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg164633.html

 Unfortunately we have a real Scylla versus Charybdis scenario here.

 Stephan

  Murat
 
  2011/6/1 Murat Yildizoglu murat.yildizo...@univ-cezanne.fr
  Hello Stephan,
 
  I have been using the new OSX binary and I see some strange things going
 on with the cursor: it does not correctly indicate its position (it is
 always a little bit on the right of its actual position), and when I insert
 or delete characters, the operations do not take place at the correct place.
 The problem does not seem to depend on the font  I choose for the screen.
 
   Do you observe this problem?
 
  Murat
 
  2011/5/22 Stephan Witt st.w...@gmx.net
  Am 22.05.2011 um 12:20 schrieb Murat Yildizoglu:
 
   Hi again,
  
   I see a strange thing with this new build: I can see several
 Reconfigure items in the Lyx menu. Their number even increases : I had two
 of them and I can see three now. Not a big problem, but i prefer to signal
 it.
 
  Yes, I can it see too. :( Weird...
 
   2011/5/22 Murat Yildizoglu murat.yildizo...@univ-cezanne.fr
   A very big Woaw and Hurrah! Stephan ;-)
 
  You're welcome.
 
   This build solves both my problems:
  
   - I can use Divvy to resize the Lyx window;
   - ForeverSave can now backup Lyx documents.
 
  Very good.
 
   Moreover, I have the impression that the launch of Lyx is much quicker
 now.
  
   This is definitely a very nice trick and thank you very much for having
 spent time to solve these small problems.
  
   If we do not find any other problems with this Qt build, I hope that it
 will become the default one to use, since it looks better integrated into
 OSX.
 
  Yes, we should switch to cocoa based Qt. I think this the root cause why
 Qt 4.7 worked better - it's simply based on cocoa per default.
 
  Stephan
 
 
 
  --
  Prof. Murat Yildizoglu
  Université Paul Cézanne (Aix-Marseille 3)
  GREQAM (UMR CNRS 6579)
  Centre de la Vieille Charité
  2, rue de la Charité
  13236 Marseille cedex 02
 
  Bureau 320
  Tel : +33 4 91 14 07 27 (standard)
  Tel : +33 4 91 14 07 70 (secrétariat)
  Tel : +33 4 91 14 07 47 (bureau)
  Fax : +33 4 91 90 02 27
 
  e-mail: murat.yildizo...@univ-cezanne.fr
  www : http:/yildizoglu.co.cc
  http://www.twitter.com/yildizoglu
  __
 
 
 
  --
  Prof. Murat Yildizoglu
  Université Paul Cézanne (Aix-Marseille 3)
  GREQAM (UMR CNRS 6579)
  Centre de la Vieille Charité
  2, rue de la Charité
  13236 Marseille cedex 02
 
  Bureau 320
  Tel : +33 4 91 14 07 27 (standard)
  Tel : +33 4 91 14 07 70 (secrétariat)
  Tel : +33 4 91 14 07 47 (bureau)
  Fax : +33 4 91 90 02 27
 
  e-mail: murat.yildizo...@univ-cezanne.fr
  www : http:/yildizoglu.co.cc
  http://www.twitter.com/yildizoglu
  __




-- 
Prof. Murat Yildizoglu
Université Paul Cézanne (Aix-Marseille 3)
GREQAM (UMR CNRS 6579)
Centre de la Vieille Charité
2, rue de la Charité
13236 Marseille cedex 02

Bureau 320
Tel : +33 4 91 14 07 27 (standard)
Tel : +33 4 91 14 07 70 (secrétariat)
Tel : +33 4 91 14 07 47 (bureau)
Fax : +33 4 91 90 02 27

e-mail: murat.yildizo...@univ-cezanne.fr
www : http:/yildizoglu.co.cc
http://www.twitter.com/yildizoglu
__

Re: r38969 - lyx-devel/trunk/src/frontends/qt4

[Jean-Marc Lasgouttes]

Le 06/06/11 20:20, Vincent van Ravesteijn a écrit :

Moc doesn't work if the class is within #if's (a bit strange, but this
seems to be the case). This means you can't put the whole class inside
the #if because compilation with the newest Qt does not work. That's
also the reason I moved the Q_SIGNAL definitions out of the #if clause.


OK.


Why did you also put the #ifs around the IconButton class. I can't see
why this class would not compile on older Qt's.


I get with current trunk

make[4]: entrant dans le répertoire « /home/local/lasgoutt/devbuild/src »
  CXXLD  lyx
frontends/qt4/liblyxqt4.a(FancyLineEdit.o):(.rodata._ZTVN3lyx8frontend10IconButtonE[vtable 
for lyx::frontend::IconButton]+0xf8): undefined reference to 
`lyx::frontend::IconButton::paintEvent(QPaintEvent*)'

collect2: ld returned 1 exit status

JMarc

Re: advice on how to implement my dream LyX feature

[Xu Wang]

On Sun, May 29, 2011 at 6:32 PM, Cyrille Artho c.ar...@aist.go.jp wrote:


I think this is a useful addition for the cropping of images. The
way I now have to crop an image is to guess some numbers, press
Apply, check in the main LyX window whether it is correct, adjust
the numbers, check.. and so forth.
It might be useful to select the region to crop to just by using the
mouse.
Vincent


 This is exactly what motivated me. And even after a lot of practice, it
 still always takes a few tries to get it right.

  The preview of figures in LyX is rather small by default, which is
 usually good because it saves space. However, I think that would make it a
 bit difficult to select the desired image region easily, because another
 pixel or two makes a big difference at a small zoom factor.

 So I think I would favor a pop-up window in a first implementation. This
 would also be consistent with similar dialogs (such as Browse...). The
 pop-up window could be activated by a Crop... button and have a couple of
 controls to make a precise selection of the image region easier:

 (1) +/- to zoom in and out.
 (2) Two half-rectangles (corner markers) to mark the top left and bottom
 right corners? Like ┌ and ┘ (Unicode characters), or in ASCII:

  ___
 |
 |
 |  (image)  |
|
 ___|

 This design (unlike clicking and dragging to draw a rectangle) has the
 advantage that an existing selection can be easily adjusted.

(a) Dragging each corner changes the size of the selected region.
(b) A finer line marks the entire selection (maybe the corners are shown
 in bold red, the finer line as a hair line).
(c) With this control, panning could perhaps be implemented (in addition
 to scrolling). Panning would be activated by clicking in the center of the
 image (or just more than a certain number of pixels away from the corner
 markers). Maybe this extra function confuses users, though, who may be more
 used to using scroll bars.

 An alternative to 2.a) would be to make a selection by drawing a
 rectangle: click on the top left, and then drag the mouse to the bottom
 right. That's faster but it's not obvious how to adjust the selection.
 Obviously panning cannot be implemented in this version, as clicking and
 dragging is already used for marking the rectangle.

 Using two markers for corners would also allow keeping the default
 selection; in existing documents, some users may already have defined a
 bounding box. In the drawing approach, the existing selection is lost each
 time the Crop... button is used.

 Other opinions? For a first version, zooming is optional; panning is
 definitely something that can be added at the end. So a first version would
 implement 2.a) and 2.b), or the alternative to 2.a) in addition to 2.b).

 --
 Regards,
 Cyrille Artho - http://artho.com/
 We are all like soldiers,
 crouching behind the fortifications we have raised.
-- Steven Erikson, Midnight Tides


I like your preferred option as well. However, I'm starting to realize that
such a feature is well over my head, even if I'm willing to spend a lot of
time programming. I need to learn more C++ and Qt4 until I tackle such a
feature so I will have to put it on hold unless anyone else would like to
take the lead.

Thank you very much Cyrille for your suggestions!

Qt books

[Xu Wang]

Hi, I would like to learn Qt. I learn much better from physical books than
online resources, although I've heard the Qt manual is very good.

Does anyone have suggestions for me?

How much does Qt change from year to year? I am trying to figure out how new
the book that I look for should be.

Is there any chance that LyX will stop using Qt in the recent future?

I've only studied Accelerated C++ but am thinking of also ordering C++
Primer.

Thank you,

Xu

Re: Language change within Flex inset exports wrong babel construct

[Jürgen Spitzmüller]

Guenter Milde wrote:
> > This white space disappears by properly escaping
> > the line breaks in \addto\extrasfrench{...}.
> 
> So I hope it is easily fixed for 2.1 (or 2.0.1).

Sure. Just add the % to languages and be done with it.

There are still other whitespace issues, though, with language changes at the 
beginning of quotations and macros. These were already present in 1.6.

Jürgen

Re: #7613: bug in the sweave module with french language

[Guillaume Avenin]

sample file attached
regards
Le 6 juin 2011 à 03:26, LyX Ticket Tracker a écrit :

> #7613: bug in the sweave module with french language
> --+-
> Reporter:  gavenin   |   Owner:  lasgouttes
> Type:  defect|  Status:  new   
> Priority:  normal|   Milestone:
> Component:  literate  | Version:  2.0.0 
> Severity:  normal|Keywords:  infoneeded
> --+-
> Changes (by lasgouttes):
> 
>  * keywords:  => infoneeded
>  * version:  => 2.0.0
>  * component:  general => literate
>  * severity:  blocker => normal
> 
> 
> Comment:
> 
> Please provide an example document. I do not see this problem.
> 
> -- 
> Ticket URL: 
> The LyX Project 
> LyX -- The Document Processor

trunk not compilable

[Kornel]

I get this while linking lyx
...
Linking CXX executable ../bin/lyx
cd /usr/BUILD/BuildLyx/src && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/lyx.dir/link.txt --verbose=1 
  
/usr/bin/c++   -Wall -Wunused-parameter -fno-strict-aliasing  -Wall 
-Wunused-parameter -O3 -DNDEBUG   CMakeFiles/lyx.dir/PersonalWordList.cpp.o 
CMakeFiles/lyx.dir/Buffer.cpp.o 
CMakeFiles/lyx.dir/FontInfo.cpp.o CMakeFiles/lyx.dir/ParIterator.cpp.o 
CMakeFiles/lyx.dir/FontList.cpp.o CMakeFiles/lyx.dir/TextMetrics.cpp.o 
CMakeFiles/lyx.dir/HunspellChecker.cpp.o 
CMakeFiles/lyx.dir/ParagraphMetrics.cpp.o CMakeFiles/lyx.dir/TexStream.cpp.o 
CMakeFiles/lyx.dir/EnchantChecker.cpp.o CMakeFiles/lyx.dir/ServerSocket.cpp.o 
CMakeFiles/lyx.dir/main.cpp.o 
CMakeFiles/lyx.dir/CmdDef.cpp.o CMakeFiles/lyx.dir/sgml.cpp.o 
CMakeFiles/lyx.dir/KeyMap.cpp.o CMakeFiles/lyx.dir/Length.cpp.o 
CMakeFiles/lyx.dir/MetricsInfo.cpp.o CMakeFiles/lyx.dir/LyXRC.cpp.o 
CMakeFiles/lyx.dir/ErrorList.cpp.o CMakeFiles/lyx.dir/Spacing.cpp.o 
CMakeFiles/lyx.dir/HSpace.cpp.o CMakeFiles/lyx.dir/InsetIterator.cpp.o 
CMakeFiles/lyx.dir/Floating.cpp.o 
CMakeFiles/lyx.dir/lengthcommon.cpp.o CMakeFiles/lyx.dir/VSpace.cpp.o 
CMakeFiles/lyx.dir/Text.cpp.o CMakeFiles/lyx.dir/output_plaintext.cpp.o 
CMakeFiles/lyx.dir/Compare.cpp.o 
CMakeFiles/lyx.dir/DepTable.cpp.o CMakeFiles/lyx.dir/OutputParams.cpp.o 
CMakeFiles/lyx.dir/Cursor.cpp.o CMakeFiles/lyx.dir/BufferView.cpp.o 
CMakeFiles/lyx.dir/Text2.cpp.o 
CMakeFiles/lyx.dir/LyXAction.cpp.o CMakeFiles/lyx.dir/FuncRequest.cpp.o 
CMakeFiles/lyx.dir/Row.cpp.o CMakeFiles/lyx.dir/WordList.cpp.o 
CMakeFiles/lyx.dir/Author.cpp.o CMakeFiles/lyx.dir/Chktex.cpp.o 
CMakeFiles/lyx.dir/Mover.cpp.o CMakeFiles/lyx.dir/Bidi.cpp.o 
CMakeFiles/lyx.dir/Session.cpp.o CMakeFiles/lyx.dir/Server.cpp.o 
CMakeFiles/lyx.dir/TocBackend.cpp.o CMakeFiles/lyx.dir/CutAndPaste.cpp.o 
CMakeFiles/lyx.dir/BranchList.cpp.o CMakeFiles/lyx.dir/CoordCache.cpp.o 
CMakeFiles/lyx.dir/Thesaurus.cpp.o CMakeFiles/lyx.dir/Text3.cpp.o 
CMakeFiles/lyx.dir/Converter.cpp.o 
CMakeFiles/lyx.dir/ModuleList.cpp.o CMakeFiles/lyx.dir/output_xhtml.cpp.o 
CMakeFiles/lyx.dir/Counters.cpp.o CMakeFiles/lyx.dir/Lexer.cpp.o 
CMakeFiles/lyx.dir/ConverterCache.cpp.o 
CMakeFiles/lyx.dir/output.cpp.o CMakeFiles/lyx.dir/ParagraphParameters.cpp.o 
CMakeFiles/lyx.dir/Box.cpp.o CMakeFiles/lyx.dir/output_latex.cpp.o 
CMakeFiles/lyx.dir/LaTeX.cpp.o 
CMakeFiles/lyx.dir/Exporter.cpp.o CMakeFiles/lyx.dir/boost.cpp.o 
CMakeFiles/lyx.dir/Language.cpp.o CMakeFiles/lyx.dir/Bullet.cpp.o 
CMakeFiles/lyx.dir/factory.cpp.o 
CMakeFiles/lyx.dir/BufferParams.cpp.o CMakeFiles/lyx.dir/Encoding.cpp.o 
CMakeFiles/lyx.dir/version.cpp.o CMakeFiles/lyx.dir/Undo.cpp.o 
CMakeFiles/lyx.dir/rowpainter.cpp.o 
CMakeFiles/lyx.dir/LayoutModuleList.cpp.o CMakeFiles/lyx.dir/lyxfind.cpp.o 
CMakeFiles/lyx.dir/LyX.cpp.o CMakeFiles/lyx.dir/VCBackend.cpp.o 
CMakeFiles/lyx.dir/Paragraph.cpp.o 
CMakeFiles/lyx.dir/Font.cpp.o CMakeFiles/lyx.dir/Graph.cpp.o 
CMakeFiles/lyx.dir/PDFOptions.cpp.o CMakeFiles/lyx.dir/Intl.cpp.o 
CMakeFiles/lyx.dir/KeySequence.cpp.o CMakeFiles/lyx.dir/InsetList.cpp.o 
CMakeFiles/lyx.dir/Color.cpp.o CMakeFiles/lyx.dir/LyXVC.cpp.o 
CMakeFiles/lyx.dir/TexRow.cpp.o CMakeFiles/lyx.dir/BiblioInfo.cpp.o 
CMakeFiles/lyx.dir/buffer_funcs.cpp.o 
CMakeFiles/lyx.dir/FloatList.cpp.o CMakeFiles/lyx.dir/PrinterParams.cpp.o 
CMakeFiles/lyx.dir/IndicesList.cpp.o CMakeFiles/lyx.dir/LayoutFile.cpp.o 
CMakeFiles/lyx.dir/DocIterator.cpp.o 
CMakeFiles/lyx.dir/LaTeXFeatures.cpp.o CMakeFiles/lyx.dir/FuncStatus.cpp.o 
CMakeFiles/lyx.dir/Dimension.cpp.o CMakeFiles/lyx.dir/Trans.cpp.o 
CMakeFiles/lyx.dir/CursorSlice.cpp.o 
CMakeFiles/lyx.dir/Changes.cpp.o CMakeFiles/lyx.dir/output_docbook.cpp.o 
CMakeFiles/lyx.dir/TextClass.cpp.o CMakeFiles/lyx.dir/Format.cpp.o 
CMakeFiles/lyx.dir/BufferList.cpp.o 
CMakeFiles/lyx.dir/Layout.cpp.o  -o ../bin/lyx -rdynamic ../lib/libmathed.a 
../lib/libinsets.a ../lib/libfrontends.a ../lib/libfrontend_qt4.a 
../lib/libgraphics.a ../lib/libsupport.a ../lib/libintl.a 
-lhunspell -lenchant ../lib/libfrontends.a -lQtGui ../lib/libboost_signals.a 
../lib/libboost_regex.a -lQtCore -lz 
../lib/libfrontend_qt4.a(FancyLineEdit.cpp.o): In function 
`lyx::frontend::FancyLineEditPrivate::FancyLineEditPrivate(lyx::frontend::FancyLineEdit*)':
FancyLineEdit.cpp:(.text+0x383): undefined reference to `vtable for 
lyx::frontend::IconButton'
FancyLineEdit.cpp:(.text+0x38b): undefined reference to `vtable for 
lyx::frontend::IconButton'
FancyLineEdit.cpp:(.text+0x415): undefined reference to `vtable for 
lyx::frontend::IconButton'
FancyLineEdit.cpp:(.text+0x41d): undefined reference to `vtable for 
lyx::frontend::IconButton'
../lib/libfrontend_qt4.a(FancyLineEdit.cpp.o): In function 
`lyx::frontend::FancyLineEdit::iconClicked()':
FancyLineEdit.cpp:(.text+0x54c): undefined reference to 
`lyx::frontend::IconButton::staticMetaObject'

Re: trunk not compilable

[Stephan Witt]

Am 06.06.2011 um 13:12 schrieb Kornel:

> I get this while linking lyx
> ...
> Linking CXX executable ../bin/lyx
> cd /usr/BUILD/BuildLyx/src && /usr/bin/cmake -E cmake_link_script 
> CMakeFiles/lyx.dir/link.txt --verbose=1   
> 
> /usr/bin/c++   -Wall -Wunused-parameter -fno-strict-aliasing  -Wall 
> -Wunused-parameter -O3 -DNDEBUG   CMakeFiles/lyx.dir/PersonalWordList.cpp.o
> ...
> CMakeFiles/lyx.dir/CursorSlice.cpp.o CMakeFiles/lyx.dir/Changes.cpp.o 
> CMakeFiles/lyx.dir/output_docbook.cpp.o CMakeFiles/lyx.dir/TextClass.cpp.o 
> CMakeFiles/lyx.dir/Format.cpp.o CMakeFiles/lyx.dir/BufferList.cpp.o 
> CMakeFiles/lyx.dir/Layout.cpp.o  -o ../bin/lyx -rdynamic ../lib/libmathed.a 
> ../lib/libinsets.a ../lib/libfrontends.a ../lib/libfrontend_qt4.a 
> ../lib/libgraphics.a ../lib/libsupport.a ../lib/libintl.a -lhunspell 
> -lenchant ../lib/libfrontends.a -lQtGui ../lib/libboost_signals.a 
> ../lib/libboost_regex.a -lQtCore -lz 
> ../lib/libfrontend_qt4.a(FancyLineEdit.cpp.o): In function 
> `lyx::frontend::FancyLineEditPrivate::FancyLineEditPrivate(lyx::frontend::FancyLineEdit*)':
> FancyLineEdit.cpp:(.text+0x383): undefined reference to `vtable for 
> lyx::frontend::IconButton'
> FancyLineEdit.cpp:(.text+0x38b): undefined reference to `vtable for 
> lyx::frontend::IconButton'
> FancyLineEdit.cpp:(.text+0x415): undefined reference to `vtable for 
> lyx::frontend::IconButton'
> FancyLineEdit.cpp:(.text+0x41d): undefined reference to `vtable for 
> lyx::frontend::IconButton'
> ../lib/libfrontend_qt4.a(FancyLineEdit.cpp.o): In function 
> `lyx::frontend::FancyLineEdit::iconClicked()':
> FancyLineEdit.cpp:(.text+0x54c): undefined reference to 
> `lyx::frontend::IconButton::staticMetaObject'
> ../lib/libfrontend_qt4.a(FancyLineEdit.cpp.o): In function 
> `lyx::frontend::IconButton::IconButton(QWidget*)':
> FancyLineEdit.cpp:(.text+0xd25): undefined reference to `vtable for 
> lyx::frontend::IconButton'
> FancyLineEdit.cpp:(.text+0xd2d): undefined reference to `vtable for 
> lyx::frontend::IconButton'
> collect2: ld returned 1 exit status
> ...
> 
> The qt-version is "4:4.7.2-0ubuntu6.1" if that matters. Yesterday it was 
> compilable (revision 38960).

I had the same problem. IMHO, you have to recreate your cmake project.

Stephan

Re: Language change within Flex inset exports wrong babel construct

[Guenter Milde]

On 2011-06-06, Jürgen Spitzmüller wrote:
> Guenter Milde wrote:
>> > This white space disappears by properly escaping
>> > the line breaks in \addto\extrasfrench{...}.

>> So I hope it is easily fixed for 2.1 (or 2.0.1).

> Sure. Just add the % to languages and be done with it.

Here is the patch for lib/languages:

@@ -360,8 +360,8 @@ Language french
LangCode fr_FR
PostBabelPreamble
\addto\extrasfrench{%
-  \providecommand{\og}{\leavevmode\flqq~}
-  \providecommand{\fg}{\ifdim\lastskip>\z@\unskip\fi~\frqq}
+  \providecommand{\og}{\leavevmode\flqq~}%
+  \providecommand{\fg}{\ifdim\lastskip>\z@\unskip\fi~\frqq}%
}
EndPostBabelPreamble
 End

Please apply to 2.0 and devel.

> There are still other whitespace issues, though, with language changes
> at the beginning of quotations and macros. These were already present
> in 1.6.

Could you be more specific? I could not find more missing line-break
escapes in lib/languages, but there might be more somewhere in the C code.

Thanks,

Günter

Re: trunk not compilable

[Kornel]

Am pondelok 06 Jún 2011 schrieb Stephan Witt:
> Am 06.06.2011 um 13:12 schrieb Kornel:
> > I get this while linking lyx
> > ...
> > Linking CXX executable ../bin/lyx
> > cd /usr/BUILD/BuildLyx/src && /usr/bin/cmake -E cmake_link_script
> > CMakeFiles/lyx.dir/link.txt --verbose=1 /usr/bin/c++   -Wall
> > -Wunused-parameter -fno-strict-aliasing  -Wall -Wunused-parameter -O3
> > -DNDEBUG   CMakeFiles/lyx.dir/PersonalWordList.cpp.o ...
> > CMakeFiles/lyx.dir/CursorSlice.cpp.o CMakeFiles/lyx.dir/Changes.cpp.o
> > CMakeFiles/lyx.dir/output_docbook.cpp.o
> > CMakeFiles/lyx.dir/TextClass.cpp.o CMakeFiles/lyx.dir/Format.cpp.o
> > CMakeFiles/lyx.dir/BufferList.cpp.o CMakeFiles/lyx.dir/Layout.cpp.o  -o
> > ../bin/lyx -rdynamic ../lib/libmathed.a ../lib/libinsets.a
> > ../lib/libfrontends.a ../lib/libfrontend_qt4.a ../lib/libgraphics.a
> > ../lib/libsupport.a ../lib/libintl.a -lhunspell -lenchant
> > ../lib/libfrontends.a -lQtGui ../lib/libboost_signals.a
> > ../lib/libboost_regex.a -lQtCore -lz
> > ../lib/libfrontend_qt4.a(FancyLineEdit.cpp.o): In function
> > `lyx::frontend::FancyLineEditPrivate::FancyLineEditPrivate(lyx::frontend
> > ::FancyLineEdit*)': FancyLineEdit.cpp:(.text+0x383): undefined reference
> > to `vtable for lyx::frontend::IconButton'
> > FancyLineEdit.cpp:(.text+0x38b): undefined reference to `vtable for
> > lyx::frontend::IconButton' FancyLineEdit.cpp:(.text+0x415): undefined
> > reference to `vtable for lyx::frontend::IconButton'
> > FancyLineEdit.cpp:(.text+0x41d): undefined reference to `vtable for
> > lyx::frontend::IconButton'
> > ../lib/libfrontend_qt4.a(FancyLineEdit.cpp.o): In function
> > `lyx::frontend::FancyLineEdit::iconClicked()':
> > FancyLineEdit.cpp:(.text+0x54c): undefined reference to
> > `lyx::frontend::IconButton::staticMetaObject'
> > ../lib/libfrontend_qt4.a(FancyLineEdit.cpp.o): In function
> > `lyx::frontend::IconButton::IconButton(QWidget*)':
> > FancyLineEdit.cpp:(.text+0xd25): undefined reference to `vtable for
> > lyx::frontend::IconButton' FancyLineEdit.cpp:(.text+0xd2d): undefined
> > reference to `vtable for lyx::frontend::IconButton' collect2: ld
> > returned 1 exit status
> > ...
> > 
> > The qt-version is "4:4.7.2-0ubuntu6.1" if that matters. Yesterday it was
> > compilable (revision 38960).
> 
> I had the same problem. IMHO, you have to recreate your cmake project.
> 
> Stephan

I did already with "make clean". Tried now to recreate everything, but same 
error.

Kornel


signature.asc
Description: This is a digitally signed message part.

Re: Language change within Flex inset exports wrong babel construct

[Richard Heck]

On 06/06/2011 07:45 AM, Guenter Milde wrote:
> On 2011-06-06, Jürgen Spitzmüller wrote:
>> Guenter Milde wrote:
 This white space disappears by properly escaping
 the line breaks in \addto\extrasfrench{...}.
>>> So I hope it is easily fixed for 2.1 (or 2.0.1).
>> Sure. Just add the % to languages and be done with it.
> Here is the patch for lib/languages:
>
> @@ -360,8 +360,8 @@ Language french
>   LangCode fr_FR
>   PostBabelPreamble
>   \addto\extrasfrench{%
> -\providecommand{\og}{\leavevmode\flqq~}
> -\providecommand{\fg}{\ifdim\lastskip>\z@\unskip\fi~\frqq}
> +\providecommand{\og}{\leavevmode\flqq~}%
> +\providecommand{\fg}{\ifdim\lastskip>\z@\unskip\fi~\frqq}%
>   }
>   EndPostBabelPreamble
>  End
>
> Please apply to 2.0 and devel.
>
Done, thank you.

rh

mathcal vs. mathscr in unicodesymbols

[Guenter Milde]

Dear List,

currently, the lib/unicodesymbols file in the devel branch (because of my
patch at http://www.lyx.org/trac/ticket/7600) uses a mix of \mathscr vs.
\mathcal to represent "SCRIPT ..." vs. "MATHEMATICAL SCRIPT ..." unicode
characters.

We have to take a decision:

a) treat the default LaTeX math alphabet \mathcal as a valid 
   MATHEMATICAL SCRIPT alphabet, or
  
b) consider Calligraphic and Script alphabets as distinct entities
   (because \mathscr look more like "SCRIPT" and the mathrsfs glyphs look
   more like the sample glyphs of the Unicode "... SCRIPT ..." characters.
  

I prefer a), because:

* Unicode and MathML define just one mathematical script alphabet.
  (The XITS OpenType math fonts provide the "calligraphic" letters as a
  stylistic variant - see unicode-math documentation
  http://mirror.ctan.org/macros/latex/contrib/unicode-math/unicode-math.pdf
  .)

* This way capital 'SCRIPT' letters can be mapped without the need of an
  external package -> avoids the "LyX autoselected packages"
  problems.
  
  And without a new math alphabet (also important because of the
  TeX limit of just 16 math alphabets easily hit with advanced math
  typesetting).
  
* The user can select different fonts for \mathcal with one of the packages
  
  eucal  Euler Script font, part of amsmath,
 
  calrsfsRalph Smith's Formal Script via \mathcal instead of 
 \mathscr,
 
  rsfso  Ralph Smith's Formal Script with the slant substantially
 reduced. The output is quite similar to that from the Adobe
 Mathematical Pi script font. 
  
  urwchancal Zapf chancery (also providing small script letters),
  
  as well as with a "generic" math-font package like "fourier" (which,
  however, changes all math fonts and the text font).

If there is a consensus, I can provide a patch.
  
Günter

  

Re: mathcal vs. mathscr in unicodesymbols

[Richard Heck]

On 06/06/2011 08:37 AM, Guenter Milde wrote:
> Dear List,
>
> currently, the lib/unicodesymbols file in the devel branch (because of my
> patch at http://www.lyx.org/trac/ticket/7600) uses a mix of \mathscr vs.
> \mathcal to represent "SCRIPT ..." vs. "MATHEMATICAL SCRIPT ..." unicode
> characters.
>
> We have to take a decision:
>
> a) treat the default LaTeX math alphabet \mathcal as a valid 
>MATHEMATICAL SCRIPT alphabet, or
>   
> b) consider Calligraphic and Script alphabets as distinct entities
>(because \mathscr look more like "SCRIPT" and the mathrsfs glyphs look
>more like the sample glyphs of the Unicode "... SCRIPT ..." characters.
>   
>
> I prefer a), because:
> ...
>
I do not have a strong preference here, but your reasoning sounds good
to me.

rh

Re: Language change within Flex inset exports wrong babel construct

[Jürgen Spitzmüller]

Guenter Milde wrote:
> Could you be more specific? I could not find more missing line-break
> escapes in lib/languages, but there might be more somewhere in the C code.

I'll try to make a test case when I find time (too busy currently). The issue 
often arises when I use a foreign language for a complete quote or a heading. 
This gives vertical or horizontal unwanted whitespace. Adding an empty ERT 
works around this.

Jürgen

Re: Link Error in Trunk

[Jean-Marc Lasgouttes]

Le 06/06/2011 14:30, Richard Heck a écrit :


CXXLD  lyx
frontends/qt4/liblyxqt4.a(FancyLineEdit.o): In function `IconButton':
/cvs/lyx/src/frontends/qt4/FancyLineEdit.cpp:267: undefined reference to
`vtable for lyx::frontend::IconButton'
/cvs/lyx/src/frontends/qt4/FancyLineEdit.cpp:267: undefined reference to
`vtable for lyx::frontend::IconButton'
frontends/qt4/liblyxqt4.a(FancyLineEdit.o): In function
`qobject_cast':
/usr/include/QtCore/qobject.h:366: undefined reference to
`lyx::frontend::IconButton::staticMetaObject'
collect2: ld returned 1 exit status



What Qt version? Could the problem be r38963? I could not compile with 4.5.

JMarc

trunk not compilable

[Uwe Stöhr]

Due to this change in FancyLineEdit.h:
http://www.lyx.org/trac/changeset/38963
I cannot compile LyX with Qt 4.7 anymore:

release\src\PersonalWordList.obj : warning LNK4042: object specified more than 
once; extras ignored
   Creating library release\lyx.lib and object release\lyx.exp
FancyLineEdit.obj : error LNK2001: unresolved external symbol "public: virtual struct QMetaObject 
const * __thiscall lyx::frontend::IconButton::metaObject(void)

const " (?metaObject@IconButton@frontend@lyx@@UBEPBUQMetaObject@@XZ)
FancyLineEdit.obj : error LNK2001: unresolved external symbol "public: virtual void * __thiscall 
lyx::frontend::IconButton::qt_metacast(char const *)" (?qt_meta 
cast@IconButton@frontend@lyx@@UAEPAXPBD@Z)
FancyLineEdit.obj : error LNK2001: unresolved external symbol "public: virtual int __thiscall 
lyx::frontend::IconButton::qt_metacall(enum QMetaObject::Call,int,void * *)" 
(?qt_metacall@IconButton@frontend@lyx@@UAEHW4Call@QMetaObject@@HPAPAX@Z)
FancyLineEdit.obj : error LNK2019: unresolved external symbol "public: static struct QMetaObject 
const lyx::frontend::IconButton::staticMetaObject" 
(?staticMetaObject@IconButton@frontend@lyx@@2UQMetaObject@@B) referenced in function "class
lyx::frontend::IconButton * __cdecl qobject_cast(class QObject 
*)" (??$qobject_cast@PAVIconButton@frontend@lyxYAPAVIconButton@frontend@lyx@@PAVQObject@@@Z)

release\lyx.exe : fatal error LNK1120: 4 unresolved externals
scons: *** [release\lyx.exe] Error 1120
scons: building terminated because of errors.

Without the new #if QT_VERSION >= 0x040600 it compiles.

regards Uwe

Re: Link Error in Trunk

[Uwe Stöhr]

Am 06.06.2011 16:28, schrieb Jean-Marc Lasgouttes:


What Qt version? Could the problem be r38963? I could not compile with 4.5.


Sorry, read it too late.

However, I'm using Qt 4.7.3.

regards Uwe

Re: Link Error in Trunk

[Jean-Marc Lasgouttes]

Le 06/06/2011 17:39, Uwe Stöhr a écrit :

Am 06.06.2011 16:28, schrieb Jean-Marc Lasgouttes:


What Qt version? Could the problem be r38963? I could not compile with
4.5.


Sorry, read it too late.

However, I'm using Qt 4.7.3.


Better now?

JMarc

Re: Lyx 2.0.0 OSX Coca version cursor problems (was OSX crashes)

[Murat Yildizoglu]

Just to refresh this thread, I have reinstalled the standard Lyx 2 OSX build
and the cursor problem has been corrected.
So it seems that this problem comes from the Cocoa QT version. Has anybody
else observed this problem with the experimental version proposed by
Stephan?

Murat

2011/6/1 Murat Yildizoglu 

> Hello Stephan,
>
> I have been using the new OSX binary and I see some strange things going on
> with the cursor: it does not correctly indicate its position (it is always a
> little bit on the right of its actual position), and when I insert or delete
> characters, the operations do not take place at the correct place. The
> problem does not seem to depend on the font  I choose for the screen.
>
>  Do you observe this problem?
>
> Murat
>
> 2011/5/22 Stephan Witt 
>
>> Am 22.05.2011 um 12:20 schrieb Murat Yildizoglu:
>>
>> > Hi again,
>> >
>> > I see a strange thing with this new build: I can see several
>> "Reconfigure" items in the Lyx menu. Their number even increases : I had two
>> of them and I can see three now. Not a big problem, but i prefer to signal
>> it.
>>
>> Yes, I can it see too. :( Weird...
>>
>> > 2011/5/22 Murat Yildizoglu 
>> > A very big Woaw and Hurrah! Stephan ;-)
>>
>> You're welcome.
>>
>> > This build solves both my problems:
>> >
>> > - I can use Divvy to resize the Lyx window;
>> > - ForeverSave can now backup Lyx documents.
>>
>> Very good.
>>
>> > Moreover, I have the impression that the launch of Lyx is much quicker
>> now.
>> >
>> > This is definitely a very nice trick and thank you very much for having
>> spent time to solve these small problems.
>> >
>> > If we do not find any other problems with this Qt build, I hope that it
>> will become the default one to use, since it looks better integrated into
>> OSX.
>>
>> Yes, we should switch to cocoa based Qt. I think this the root cause why
>> Qt 4.7 worked better - it's simply based on cocoa per default.
>>
>> Stephan
>
>
>
>
> --
> Prof. Murat Yildizoglu
> Université Paul Cézanne (Aix-Marseille 3)
> GREQAM (UMR CNRS 6579)
> Centre de la Vieille Charité
> 2, rue de la Charité
> 13236 Marseille cedex 02
>
> Bureau 320
> Tel : +33 4 91 14 07 27 (standard)
> Tel : +33 4 91 14 07 70 (secrétariat)
> Tel : +33 4 91 14 07 47 (bureau)
> Fax : +33 4 91 90 02 27
>
> e-mail: murat.yildizo...@univ-cezanne.fr
> www : http:/yildizoglu.co.cc
> http://www.twitter.com/yildizoglu
> __
>



-- 
Prof. Murat Yildizoglu
Université Paul Cézanne (Aix-Marseille 3)
GREQAM (UMR CNRS 6579)
Centre de la Vieille Charité
2, rue de la Charité
13236 Marseille cedex 02

Bureau 320
Tel : +33 4 91 14 07 27 (standard)
Tel : +33 4 91 14 07 70 (secrétariat)
Tel : +33 4 91 14 07 47 (bureau)
Fax : +33 4 91 90 02 27

e-mail: murat.yildizo...@univ-cezanne.fr
www : http:/yildizoglu.co.cc
http://www.twitter.com/yildizoglu
__

Re: Link Error in Trunk

[Uwe Stöhr]

Am 06.06.2011 17:53, schrieb Jean-Marc Lasgouttes:


However, I'm using Qt 4.7.3.


Better now?


Sure. But reverting the change in the .h file would have been enough.

regards Uwe

Re: Link Error in Trunk

[Jean-Marc Lasgouttes]

Le 06/06/2011 17:56, Uwe Stöhr a écrit :

Am 06.06.2011 17:53, schrieb Jean-Marc Lasgouttes:


However, I'm using Qt 4.7.3.


Better now?


Sure. But reverting the change in the .h file would have been enough.


It would not link for me anyway...

JMarc

Re: r38969 - lyx-devel/trunk/src/frontends/qt4

[Vincent van Ravesteijn]

On 6-6-2011 17:53, lasgout...@lyx.org wrote:
> Author: lasgouttes
> Date: Mon Jun  6 17:53:43 2011
> New Revision: 38969
> URL: http://www.lyx.org/trac/changeset/38969
> 
> Log:
> Revert r38963. Compilation is now broken with qt 4.5, but I do not know Qt 
> moc business and do not have time to investigate.
> 


Moc doesn't work if the class is within #if's (a bit strange, but this
seems to be the case). This means you can't put the whole class inside
the #if because compilation with the newest Qt does not work. That's
also the reason I moved the Q_SIGNAL definitions out of the #if clause.

The change in FancyLineEdit.cpp was ok, because one should not #include
. I fixed this in 38970.

Why did you also put the #ifs around the IconButton class. I can't see
why this class would not compile on older Qt's.

Vincent

Re: Lyx 2.0.0 OSX Coca version cursor problems (was OSX crashes)

[Stephan Witt]

Am 06.06.2011 um 17:54 schrieb Murat Yildizoglu:

> Just to refresh this thread, I have reinstalled the standard Lyx 2 OSX build 
> and the cursor problem has been corrected.
> So it seems that this problem comes from the Cocoa QT version. Has anybody 
> else observed this problem with the experimental version proposed by Stephan?

I'm almost sure it's Cocoa based Qt that makes the problem. Until your report I 
thought it's the Qt-version what matters.
See the ticket http://www.lyx.org/trac/ticket/6920 and the discussion here 
http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg164633.html

Unfortunately we have a real Scylla versus Charybdis scenario here.

Stephan

> Murat
> 
> 2011/6/1 Murat Yildizoglu 
> Hello Stephan,
> 
> I have been using the new OSX binary and I see some strange things going on 
> with the cursor: it does not correctly indicate its position (it is always a 
> little bit on the right of its actual position), and when I insert or delete 
> characters, the operations do not take place at the correct place. The 
> problem does not seem to depend on the font  I choose for the screen.
> 
>  Do you observe this problem? 
> 
> Murat
> 
> 2011/5/22 Stephan Witt 
> Am 22.05.2011 um 12:20 schrieb Murat Yildizoglu:
> 
> > Hi again,
> >
> > I see a strange thing with this new build: I can see several "Reconfigure" 
> > items in the Lyx menu. Their number even increases : I had two of them and 
> > I can see three now. Not a big problem, but i prefer to signal it.
> 
> Yes, I can it see too. :( Weird...
> 
> > 2011/5/22 Murat Yildizoglu 
> > A very big Woaw and Hurrah! Stephan ;-)
> 
> You're welcome.
> 
> > This build solves both my problems:
> >
> > - I can use Divvy to resize the Lyx window;
> > - ForeverSave can now backup Lyx documents.
> 
> Very good.
> 
> > Moreover, I have the impression that the launch of Lyx is much quicker now.
> >
> > This is definitely a very nice trick and thank you very much for having 
> > spent time to solve these small problems.
> >
> > If we do not find any other problems with this Qt build, I hope that it 
> > will become the default one to use, since it looks better integrated into 
> > OSX.
> 
> Yes, we should switch to cocoa based Qt. I think this the root cause why Qt 
> 4.7 worked better - it's simply based on cocoa per default.
> 
> Stephan
> 
> 
> 
> -- 
> Prof. Murat Yildizoglu
> Université Paul Cézanne (Aix-Marseille 3) 
> GREQAM (UMR CNRS 6579)
> Centre de la Vieille Charité
> 2, rue de la Charité
> 13236 Marseille cedex 02
> 
> Bureau 320
> Tel : +33 4 91 14 07 27 (standard)
> Tel : +33 4 91 14 07 70 (secrétariat) 
> Tel : +33 4 91 14 07 47 (bureau)
> Fax : +33 4 91 90 02 27 
> 
> e-mail: murat.yildizo...@univ-cezanne.fr
> www : http:/yildizoglu.co.cc
> http://www.twitter.com/yildizoglu
> __
> 
> 
> 
> -- 
> Prof. Murat Yildizoglu
> Université Paul Cézanne (Aix-Marseille 3) 
> GREQAM (UMR CNRS 6579)
> Centre de la Vieille Charité
> 2, rue de la Charité
> 13236 Marseille cedex 02
> 
> Bureau 320
> Tel : +33 4 91 14 07 27 (standard)
> Tel : +33 4 91 14 07 70 (secrétariat) 
> Tel : +33 4 91 14 07 47 (bureau)
> Fax : +33 4 91 90 02 27 
> 
> e-mail: murat.yildizo...@univ-cezanne.fr
> www : http:/yildizoglu.co.cc
> http://www.twitter.com/yildizoglu
> __

Re: Lyx 2.0.0 OSX Coca version cursor problems (was OSX crashes)

[Murat Yildizoglu]

Well, if the only problems with the "official" Lyx release concern Divvy and
ForeverSave, we can get away with the QT version used by it. We can hold
from using Divvy to resize the Lyx window (in my case it does not crash Lyx,
the windows just ignores Divvy) and a functionality similar to ForeverSave
(saving and versioning) will be included in Lion, at the system level, if I
understand well the discussion on the net. I just hope that this will be
compatible with QT and Lyx.

2011/6/6 Stephan Witt 

> Am 06.06.2011 um 17:54 schrieb Murat Yildizoglu:
>
> > Just to refresh this thread, I have reinstalled the standard Lyx 2 OSX
> build and the cursor problem has been corrected.
> > So it seems that this problem comes from the Cocoa QT version. Has
> anybody else observed this problem with the experimental version proposed by
> Stephan?
>
> I'm almost sure it's Cocoa based Qt that makes the problem. Until your
> report I thought it's the Qt-version what matters.
> See the ticket http://www.lyx.org/trac/ticket/6920 and the discussion here
> http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg164633.html
>
> Unfortunately we have a real Scylla versus Charybdis scenario here.
>
> Stephan
>
> > Murat
> >
> > 2011/6/1 Murat Yildizoglu 
> > Hello Stephan,
> >
> > I have been using the new OSX binary and I see some strange things going
> on with the cursor: it does not correctly indicate its position (it is
> always a little bit on the right of its actual position), and when I insert
> or delete characters, the operations do not take place at the correct place.
> The problem does not seem to depend on the font  I choose for the screen.
> >
> >  Do you observe this problem?
> >
> > Murat
> >
> > 2011/5/22 Stephan Witt 
> > Am 22.05.2011 um 12:20 schrieb Murat Yildizoglu:
> >
> > > Hi again,
> > >
> > > I see a strange thing with this new build: I can see several
> "Reconfigure" items in the Lyx menu. Their number even increases : I had two
> of them and I can see three now. Not a big problem, but i prefer to signal
> it.
> >
> > Yes, I can it see too. :( Weird...
> >
> > > 2011/5/22 Murat Yildizoglu 
> > > A very big Woaw and Hurrah! Stephan ;-)
> >
> > You're welcome.
> >
> > > This build solves both my problems:
> > >
> > > - I can use Divvy to resize the Lyx window;
> > > - ForeverSave can now backup Lyx documents.
> >
> > Very good.
> >
> > > Moreover, I have the impression that the launch of Lyx is much quicker
> now.
> > >
> > > This is definitely a very nice trick and thank you very much for having
> spent time to solve these small problems.
> > >
> > > If we do not find any other problems with this Qt build, I hope that it
> will become the default one to use, since it looks better integrated into
> OSX.
> >
> > Yes, we should switch to cocoa based Qt. I think this the root cause why
> Qt 4.7 worked better - it's simply based on cocoa per default.
> >
> > Stephan
> >
> >
> >
> > --
> > Prof. Murat Yildizoglu
> > Université Paul Cézanne (Aix-Marseille 3)
> > GREQAM (UMR CNRS 6579)
> > Centre de la Vieille Charité
> > 2, rue de la Charité
> > 13236 Marseille cedex 02
> >
> > Bureau 320
> > Tel : +33 4 91 14 07 27 (standard)
> > Tel : +33 4 91 14 07 70 (secrétariat)
> > Tel : +33 4 91 14 07 47 (bureau)
> > Fax : +33 4 91 90 02 27
> >
> > e-mail: murat.yildizo...@univ-cezanne.fr
> > www : http:/yildizoglu.co.cc
> > http://www.twitter.com/yildizoglu
> > __
> >
> >
> >
> > --
> > Prof. Murat Yildizoglu
> > Université Paul Cézanne (Aix-Marseille 3)
> > GREQAM (UMR CNRS 6579)
> > Centre de la Vieille Charité
> > 2, rue de la Charité
> > 13236 Marseille cedex 02
> >
> > Bureau 320
> > Tel : +33 4 91 14 07 27 (standard)
> > Tel : +33 4 91 14 07 70 (secrétariat)
> > Tel : +33 4 91 14 07 47 (bureau)
> > Fax : +33 4 91 90 02 27
> >
> > e-mail: murat.yildizo...@univ-cezanne.fr
> > www : http:/yildizoglu.co.cc
> > http://www.twitter.com/yildizoglu
> > __
>
>


-- 
Prof. Murat Yildizoglu
Université Paul Cézanne (Aix-Marseille 3)
GREQAM (UMR CNRS 6579)
Centre de la Vieille Charité
2, rue de la Charité
13236 Marseille cedex 02

Bureau 320
Tel : +33 4 91 14 07 27 (standard)
Tel : +33 4 91 14 07 70 (secrétariat)
Tel : +33 4 91 14 07 47 (bureau)
Fax : +33 4 91 90 02 27

e-mail: murat.yildizo...@univ-cezanne.fr
www : http:/yildizoglu.co.cc
http://www.twitter.com/yildizoglu
__

Re: r38969 - lyx-devel/trunk/src/frontends/qt4

[Jean-Marc Lasgouttes]

Le 06/06/11 20:20, Vincent van Ravesteijn a écrit :

Moc doesn't work if the class is within #if's (a bit strange, but this
seems to be the case). This means you can't put the whole class inside
the #if because compilation with the newest Qt does not work. That's
also the reason I moved the Q_SIGNAL definitions out of the #if clause.


OK.


Why did you also put the #ifs around the IconButton class. I can't see
why this class would not compile on older Qt's.


I get with current trunk

make[4]: entrant dans le répertoire « /home/local/lasgoutt/devbuild/src »
  CXXLD  lyx
frontends/qt4/liblyxqt4.a(FancyLineEdit.o):(.rodata._ZTVN3lyx8frontend10IconButtonE[vtable 
for lyx::frontend::IconButton]+0xf8): undefined reference to 
`lyx::frontend::IconButton::paintEvent(QPaintEvent*)'

collect2: ld returned 1 exit status

JMarc

Re: advice on how to implement my dream LyX feature

[Xu Wang]

On Sun, May 29, 2011 at 6:32 PM, Cyrille Artho  wrote:

>
>>I think this is a useful addition for the cropping of images. The
>>way I now have to crop an image is to guess some numbers, press
>>Apply, check in the main LyX window whether it is correct, adjust
>>the numbers, check.. and so forth.
>>It might be useful to select the region to crop to just by using the
>>mouse.
>>Vincent
>>
>>
>> This is exactly what motivated me. And even after a lot of practice, it
>> still always takes a few tries to get it right.
>>
>>  The preview of figures in LyX is rather small by default, which is
> usually good because it saves space. However, I think that would make it a
> bit difficult to select the desired image region easily, because another
> pixel or two makes a big difference at a small zoom factor.
>
> So I think I would favor a pop-up window in a first implementation. This
> would also be consistent with similar dialogs (such as "Browse..."). The
> pop-up window could be activated by a "Crop..." button and have a couple of
> controls to make a precise selection of the image region easier:
>
> (1) "+"/"-" to zoom in and out.
> (2) Two half-rectangles ("corner markers") to mark the top left and bottom
> right corners? Like ┌ and ┘ (Unicode characters), or in ASCII:
>
>  ___
> |
> |
> |  (image)  |
>|
> ___|
>
> This design (unlike clicking and dragging to "draw" a rectangle) has the
> advantage that an existing selection can be easily adjusted.
>
>(a) Dragging each corner changes the size of the selected region.
>(b) A finer line marks the entire selection (maybe the corners are shown
> in bold red, the finer line as a hair line).
>(c) With this control, panning could perhaps be implemented (in addition
> to scrolling). Panning would be activated by clicking in the center of the
> image (or just more than a certain number of pixels away from the corner
> markers). Maybe this extra function confuses users, though, who may be more
> used to using scroll bars.
>
> An alternative to 2.a) would be to make a selection by "drawing" a
> rectangle: click on the top left, and then drag the mouse to the bottom
> right. That's faster but it's not obvious how to adjust the selection.
> Obviously panning cannot be implemented in this version, as clicking and
> dragging is already used for marking the rectangle.
>
> Using two markers for corners would also allow keeping the default
> selection; in existing documents, some users may already have defined a
> bounding box. In the "drawing" approach, the existing selection is lost each
> time the "Crop..." button is used.
>
> Other opinions? For a first version, zooming is optional; panning is
> definitely something that can be added at the end. So a first version would
> implement 2.a) and 2.b), or the alternative to 2.a) in addition to 2.b).
>
> --
> Regards,
> Cyrille Artho - http://artho.com/
> We are all like soldiers,
> crouching behind the fortifications we have raised.
>-- Steven Erikson, "Midnight Tides"
>

I like your preferred option as well. However, I'm starting to realize that
such a feature is well over my head, even if I'm willing to spend a lot of
time programming. I need to learn more C++ and Qt4 until I tackle such a
feature so I will have to put it on hold unless anyone else would like to
take the lead.

Thank you very much Cyrille for your suggestions!

Qt books

[Xu Wang]

Hi, I would like to learn Qt. I learn much better from physical books than
online resources, although I've heard the Qt manual is very good.

Does anyone have suggestions for me?

How much does Qt change from year to year? I am trying to figure out how new
the book that I look for should be.

Is there any chance that LyX will stop using Qt in the recent future?

I've only studied Accelerated C++ but am thinking of also ordering C++
Primer.

Thank you,

Xu