Re: Question on Multiple Render Passes

On 12/01/2022 06:44, Joel Kulesza wrote: LyX Developers, A colleague asked me a question the other day on how LyX operates that I was unsure of, which I hope you can help me with.  He'd read that an approach to "speeding up" multiple render-pass LaTeX compilations is to use draft-mode compile

Re: Question about trac search

On 1/4/21 4:47 AM, Yu Jin wrote: > Am Mo., 4. Jan. 2021 um 10:39 Uhr schrieb Yu Jin >: > > I am trying to search for bugs in Trac. I have chosen only "new" > status in the filters, but the result also shows fixedinstable, > reopened and even closed bugs in some c

Re: Question about trac search

Am Mo., 4. Jan. 2021 um 10:39 Uhr schrieb Yu Jin : > I am trying to search for bugs in Trac. I have chosen only "new" status in > the filters, but the result also shows fixedinstable, reopened and even > closed bugs in some cases. See attached. > What am I doing wrong? > Ah found, it was (status A

Re: Question on undo: Remove a finishUndo() after a recordUndo() ?

On Sat, Feb 01, 2020 at 08:41:12PM +0100, Jean-Marc Lasgouttes wrote: > Le 01/02/2020 à 18:39, Scott Kostyshak a écrit : > > What would the consequences be of the attached patch? > > > > From what I understand, finishUndo() is meant for when there have been > > som undos of type INSERT or DELETE

Re: Question on undo: Remove a finishUndo() after a recordUndo() ?

Le 01/02/2020 à 18:39, Scott Kostyshak a écrit : What would the consequences be of the attached patch? From what I understand, finishUndo() is meant for when there have been som undos of type INSERT or DELETE recorded, but PARAGRAPH_MOVE_DOWN itself does not record any INSERTs or DELETEs. What

Re: Question on osuosl.org hosting service(s)

Thanks, Pavel, to taking this responsiblity. On 09/06/2018 10:37 AM, Pavel Sanda wrote: > Hi OSU Open Source Lab, > > I'm one of developers of LyX, open source document processor (www.lyx.org). > Our services (web/bug tracker system/git server/wiki site) used to be kindly > hosted for the past d

Re: Question for Guillaume about b30f8d3c and GuiFontMetrics::countExpanders

Le 27/07/2017 à 16:11, Guillaume MM a écrit : The reasoning was that how many expanders there are in a string is toolkit-specific. This implementation was by testing and reading the docs and source code of Qt, and does not correspond to my knowledge to any Unicode standard (say). So, using the fr

Re: Question for Guillaume about b30f8d3c and GuiFontMetrics::countExpanders

Le 25/07/2017 à 14:36, Jean-Marc Lasgouttes a écrit : Hi Guillaume, The commit log for b30f8d3c says: " CountExpanders() is moved to FontMetrics to fix a discrepancy with the duplicate implementation from 598f7e4a." I interpret that to mean that countExpanders() should be available in GuiP

Re: Question on installation of Lyx from distro and/or over internet

On 07/14/2016 11:56 PM, Jean-Pierre Chrétien wrote: Le 14/07/2016 07:13, Buenas Noticias a écrit : Hi Michael: TeXlive can work because each is in a different folder and you are the one you decide on your route which you work (/usr/local/texlive/2013 or 2016). I think that if you have inst

Re: Question on installation of Lyx from distro and/or over internet

Le 14/07/2016 07:13, Buenas Noticias a écrit : Hi Michael: TeXlive can work because each is in a different folder and you are the one you decide on your route which you work (/usr/local/texlive/2013 or 2016). I think that if you have installed an earlier version of lyx and install later, the ly

Re: Question on installation of Lyx from distro and/or over internet

Hi Michael: TeXlive can work because each is in a different folder and you are the one you decide on your route which you work (/usr/local/texlive/2013 or 2016). I think that if you have installed an earlier version of lyx and install later, the lyx executable will be overwritten and the cur

Re: Question for Richard

Le 15/04/15 18:20, Richard Heck a écrit : -docstring const TextClass::emptylayout_ = from_ascii(N_("Plain Layout")); +// This string cannot be translated, because it is a layout identifier. +docstring const TextClass::emptylayout_ = from_ascii("Plain Layout"); If you look at TextClass.cpp from

Re: Question for Richard

On 04/15/2015 05:57 AM, Jean-Marc Lasgouttes wrote: Hi Richard, I have a question about an old commit (see bleow). Basically, what you do here causes the message machinery to be invoked before the locale is properly set up. It is not a big problem per se, but the patch looks very dubious to m

Re: Question about Translations for 2.1.3

Richard Heck wrote: > Can anyone explain to me exactly I need to do to incorporate new po > files into 2.1.x? Uwe usually does this, but it appears he is busy right > now. The last time I did it, I messed something up. I think it had to do > with not regenerating gmo files, but I'm not sure. IIRC

Re: QUESTION: How to enable Qt5 for LyX master

Am 25.08.2014 um 19:58 schrieb Enrico Forestieri : > On Mon, Aug 25, 2014 at 05:54:08PM +0200, Enrico Forestieri wrote: > >> On Mon, Aug 25, 2014 at 04:18:02PM +0200, Stephan Witt wrote: >> >>> >>> Am 25.08.2014 um 16:12 schrieb Kornel Benko : >>> Am Montag, 25. August 2014 um 16:08:27, s

Re: QUESTION: How to enable Qt5 for LyX master

On Mon, Aug 25, 2014 at 05:54:08PM +0200, Enrico Forestieri wrote: > On Mon, Aug 25, 2014 at 04:18:02PM +0200, Stephan Witt wrote: > > > > > Am 25.08.2014 um 16:12 schrieb Kornel Benko : > > > > > Am Montag, 25. August 2014 um 16:08:27, schrieb Kornel Benko > > > > > >> At least on QT4 there

Re: QUESTION: How to enable Qt5 for LyX master

Am 25.08.2014 um 17:54 schrieb Enrico Forestieri : > On Mon, Aug 25, 2014 at 04:18:02PM +0200, Stephan Witt wrote: > >> >> Am 25.08.2014 um 16:12 schrieb Kornel Benko : >> >>> Am Montag, 25. August 2014 um 16:08:27, schrieb Kornel Benko >>> At least on QT4 there is no symbol Q_OS_X11. So

Re: QUESTION: How to enable Qt5 for LyX master

On Mon, Aug 25, 2014 at 04:18:02PM +0200, Stephan Witt wrote: > > Am 25.08.2014 um 16:12 schrieb Kornel Benko : > > > Am Montag, 25. August 2014 um 16:08:27, schrieb Kornel Benko > > > >> At least on QT4 there is no symbol Q_OS_X11. So this patch would break QT4 > >> compilation. > >> > > >

Re: QUESTION: How to enable Qt5 for LyX master

Am 25.08.2014 um 16:12 schrieb Kornel Benko : > Am Montag, 25. August 2014 um 16:08:27, schrieb Kornel Benko >> Am Montag, 25. August 2014 um 15:53:14, schrieb Stephan Witt >> >>> Since Qt5 the Qt developers decided to not define the Q_WS_ macros anymore. >>> The reasoning is to disable all pl

Re: QUESTION: How to enable Qt5 for LyX master

Am Montag, 25. August 2014 um 15:53:14, schrieb Stephan Witt > Since Qt5 the Qt developers decided to not define the Q_WS_ macros anymore. > The reasoning is to disable all platform specific code and force the Qt users > like us to review all code guarded by Q_WS_ macros. This means all code in Ly

Re: QUESTION: How to enable Qt5 for LyX master

Am Montag, 25. August 2014 um 16:08:27, schrieb Kornel Benko > Am Montag, 25. August 2014 um 15:53:14, schrieb Stephan Witt > > Since Qt5 the Qt developers decided to not define the Q_WS_ macros anymore. > > The reasoning is to disable all platform specific code and force the Qt > > users > > li

Re: QUESTION: How to enable Qt5 for LyX master

Am 25.08.2014 um 15:53 schrieb Stephan Witt : > Since Qt5 the Qt developers decided to not define the Q_WS_ macros anymore. > The reasoning is to disable all platform specific code and force the Qt users > like us to review all code guarded by Q_WS_ macros. This means all code in LyX > inside thes

Re: Question about project organzation

On 04/16/2014 01:40 AM, Min Ding@ANU wrote: Hi, I have some questions about our project organzation and structure. I'm not sure who "we" is here, but * Do we have project team leader? Not in any official sense, I do not think. There's a kind of informal hierarchy, largely based upon

Re: Question, small TYPO

On 05/22/2013 04:19 PM, Gordon Watson wrote: 1. Question: No names on the SUPPORTERS list? Any significance in that? I'm not sure what is supposed to be there. 2. Small typo Contributors list: http://www.lyx.org/Credits#toc1 "Carmen Kauffmann Original name that is now two characterS shorter"

Re: Question about Advanced Find and Replace project

On 30/04/13 20:28, Ayrat Khalitov wrote: > Hello! Hi, > I update my proposal and I have three questions about Advanced Find and > Replace module: > 1) Which are most important problems in this module available? Describe them > in more detail, please (slowness, non-working corner cases... ) . T

Re: Question about tex2lyx Parser::deparse()

Jean-Marc Lasgouttes wrote: > Le 26/02/2013 22:23, Georg Baum a écrit : >> Jean-Marc, >> >> many thanks for your noweb improvements! While investigating how your >> test document could be added to the test suite I stumbled over some >> encoding warnings that are currently output for CJK.tex. I add

Re: Question about tex2lyx Parser::deparse()

Le 26/02/2013 22:23, Georg Baum a écrit : Jean-Marc, many thanks for your noweb improvements! While investigating how your test document could be added to the test suite I stumbled over some encoding warnings that are currently output for CJK.tex. I added this warning (in iparserdocstream::setEn

Re: question about Inset-Info

Le 04/01/2012 08:36, Jürgen Spitzmüller a écrit : BTW the drawback of your approach might be that some binding files (at least aqua.bind, AFAICS) do not use the command-alternatives and will thus not display the shortcut. We could specialize the inset-info code for the case of command-alternat

Re: question about Inset-Info

Uwe Stöhr wrote: >> I think it is not a good idea to visualize nobreakspace that way. > > I want to print the shortcut "Ctrl+Space" , not \textvisiblespace. And this > works now. I was referring to how LyX visualizes nobreakspace. I think this should be changed to something more informative. BT

Re: question about Inset-Info

Am 03.01.2012 09:04, schrieb Jürgen Spitzmüller: if you enter the whole command-alternatives space-insert protected ; math-space it works. Thanks! That was was I needed. I suppose in your case, you do not get an empty shortcut, but a nobreakspace character, since this is what "space-insert

Re: question about Inset-Info

Uwe Stöhr wrote: > I want to reference in the UserGuide the shortcut for a protected space > "Ctrl+Space". Its definition is > > command-alternatives space-insert protected > > But when I use this in an Inset-Info I get an empty shortcut. What can I do > or is this a bug? if you enter the whole

Re: Question about the new lyxpipe feature

Am 02.11.2011 00:47, schrieb Vincent van Ravesteijn: Look in the link I sent you. Enter this in tools,preferences,paths. It now works for me too: - the pipe path must be \\.\pipe\lyxpipe (nothing else works) - then the Single instance checkbox can be set - finally LyX must be restarted I

Re: Question about the new lyxpipe feature

On Wed, Nov 2, 2011 at 12:00 AM, Uwe Stöhr wrote: > Am 01.11.2011 23:53, schrieb Vincent van Ravesteijn: > >> Set the lyxpipe > > I cannot set it. In the UserGuide, sec. C.3 Paths, Hartmut wrote an example > for me. I have JabRef installed and could test it, but don't know what to > insert in the

Re: Question about the new lyxpipe feature

Op 2 nov. 2011 00:01 schreef "Uwe Stöhr" het volgende: > > Am 01.11.2011 23:53, schrieb Vincent van Ravesteijn: > >> Set the lyxpipe > > > I cannot set it. In the UserGuide, sec. C.3 Paths, Hartmut wrote an example for me. I have JabRef installed and could test it, but don't know what to insert in

Re: Question about the new lyxpipe feature

Am 01.11.2011 23:53, schrieb Vincent van Ravesteijn: Set the lyxpipe I cannot set it. In the UserGuide, sec. C.3 Paths, Hartmut wrote an example for me. I have JabRef installed and could test it, but don't know what to insert in the LyX Server-pipe field. Check single instance This optio

Re: Question about the new lyxpipe feature

Set the lyxpipe Check single instance Restart lyx Doubleclick lyx file ... it should open in the already open lyx instance. Vincent Op 1 nov. 2011 19:57 schreef "Uwe Stöhr" het volgende: > Am 01.11.2011 08:54, schrieb Vincent van Ravesteijn: > > lyxpipe also works on Windows: >> >> http://www.m

Re: Question about the new lyxpipe feature

Am 01.11.2011 08:54, schrieb Vincent van Ravesteijn: lyxpipe also works on Windows: http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg154614.html Not for me, but perhaps another problem with my SCons build -> definitively time to switch to CMake. But do you have a quick recipe to test

Re: Question about the new lyxpipe feature

Op 1-11-2011 1:54, Uwe Stöhr schreef: Am 31.10.2011 04:02, schrieb PhilipPirrip: Tools > Preferences > Look & Feel > User Interface > second from below "Single instance" checkbox Thanks! I have overseen it as it is permanently greyed out. But clear, lyxpipe doesn't work on Windows. I will up

Re: Question about the new lyxpipe feature

Am 31.10.2011 04:02, schrieb PhilipPirrip: Tools > Preferences > Look & Feel > User Interface > second from below "Single instance" checkbox Thanks! I have overseen it as it is permanently greyed out. But clear, lyxpipe doesn't work on Windows. I will update the UserGuide accordingly now.

Re: Question about the new lyxpipe feature

On 10/31/2011 03:15 AM, Uwe Stöhr wrote: But I cannot find a checkbox named "Single instance". Can you please point me to it? Tools > Preferences > Look & Feel > User Interface > second from below "Single instance" checkbox (at least in my LyX v2.0.1)

Re: question about roff command in LyX's preferences

Am 30.10.2011 23:08, schrieb Vincent van Ravesteijn: Can anybody please point me to it? http://www.lyx.org/trac/search?q=roff&noquickjump=1&changeset=on Thank you! regards Uwe

Re: question about roff command in LyX's preferences

Op 30-10-2011 4:09, Uwe Stöhr schreef: In LyX 1.6.x we had in the preferences under Output->Plain text a field for the "roff command". Where is this gone in LyX 2.0? I cannot find anything about it in the preferences and also not in the document settings. The description of this feature was:

Re: question about the description of TEXINPUTS

On Sun, Oct 16, 2011 at 11:55:51PM +0200, Uwe Stöhr wrote: > Am 16.10.2011 19:29, schrieb Enrico Forestieri: > > >>When replaced by If. > > > >And, according to you, that's the grammar error? > > Our docs were during the last year kindly reviewed by Mr. Hudson - a > lector in a publishing compan

Re: question about the description of TEXINPUTS

Am 16.10.2011 19:29, schrieb Enrico Forestieri: When replaced by If. And, according to you, that's the grammar error? Our docs were during the last year kindly reviewed by Mr. Hudson - a lector in a publishing company. He corrected almost all my when to if for the case that when was to refe

Re: question about the description of TEXINPUTS

On Sun, Oct 16, 2011 at 04:54:11PM +0200, Uwe Stöhr wrote: > Am 16.10.2011 11:18, schrieb Enrico Forestieri: > > >>What is so difficult to have a look at my initial post of this thread. > > > >Yes, I saw it, but I still don't know what grammar errors you are > >referring to. > > When replaced by

Re: question about the description of TEXINPUTS

Am 16.10.2011 11:18, schrieb Enrico Forestieri: What is so difficult to have a look at my initial post of this thread. Yes, I saw it, but I still don't know what grammar errors you are referring to. When replaced by If.

Re: question about the description of TEXINPUTS

On Sun, Oct 16, 2011 at 04:25:26AM +0200, Uwe Stöhr wrote: > Am 15.10.2011 23:46, schrieb Enrico Forestieri: > > >I don't know what grammar errors you are referring to, > > What is so difficult to have a look at my initial post of this thread. Yes, I saw it, but I still don't know what grammar

Re: question about the description of TEXINPUTS

Am 15.10.2011 23:46, schrieb Enrico Forestieri: I'm giving up, but you should try yourself to answer the following question. What happens if TEXINPUTS is already set in the environment when LyX is launched? Then it would be a prefix. But this is not the case except I add this variable manuall

Re: question about the description of TEXINPUTS

On Sat, Oct 15, 2011 at 10:46:00PM +0200, Uwe Stöhr wrote: > Am 15.10.2011 22:41, schrieb Enrico Forestieri: > > >http://en.wikipedia.org/wiki/Environment_variable#Local_to_process > > So it is only available while LyX is executed (as if I use the > command "set" in a batch file). But then it is

Re: question about the description of TEXINPUTS

Am 15.10.2011 22:41, schrieb Enrico Forestieri: http://en.wikipedia.org/wiki/Environment_variable#Local_to_process So it is only available while LyX is executed (as if I use the command "set" in a batch file). But then it is no prefix to an existing variable, but the variable itself. That was

Re: question about the description of TEXINPUTS

On Sat, Oct 15, 2011 at 10:13:34PM +0200, Uwe Stöhr wrote: > Am 15.10.2011 19:31, schrieb Enrico Forestieri: > > >>As I understand the explanation TEXINPUTS is an _environment > >>variable_ consisting of a list of paths. So why is it then also a > >>_prefix_? > > > >Because TEXINPUTS may already

Re: question about the description of TEXINPUTS

Am 15.10.2011 19:31, schrieb Enrico Forestieri: As I understand the explanation TEXINPUTS is an _environment variable_ consisting of a list of paths. So why is it then also a _prefix_? Because TEXINPUTS may already be set in the environment, I must admit that I then did not yet understand th

Re: question about the description of TEXINPUTS

On Sat, Oct 15, 2011 at 04:18:39AM +0200, Uwe Stöhr wrote: > As I understand the explanation TEXINPUTS is an _environment > variable_ consisting of a list of paths. So why is it then also a > _prefix_? Because TEXINPUTS may already be set in the environment, in which case its content should be ap

Re: question to update to docs

Am 14.10.2011 10:28, schrieb Jean-Marc Lasgouttes: what does the preferences option Use Mac-style for cursor moving between words do? Is this platform-specific? I cannot see a difference but I never had a Mac. IIRC, the difference is whether your cursor ends up at the end of current word or

Re: question to update to docs

Le 14/10/2011 06:05, Uwe Stöhr a écrit : Another question: what does the preferences option Use Mac-style for cursor moving between words do? Is this platform-specific? I cannot see a difference but I never had a Mac. IIRC, the difference is whether your cursor ends up at the end of current

Re: Question regarding Cursor::normalize()

Am 06.01.2011 um 11:47 schrieb Vincent van Ravesteijn: >> normalize() is called only from the LFUN_CUT case of >> InsetMathNest::doDispatch(). >> It corrects only the pos of the top cursor slice (if needed), AFAICS. >> >>> Fact is, we should apparently not call normalize() from a non-math >>> in

Re: Question regarding Cursor::normalize()

> normalize() is called only from the LFUN_CUT case of > InsetMathNest::doDispatch(). > It corrects only the pos of the top cursor slice (if needed), AFAICS. > >> Fact is, we should apparently not call normalize() from a non-math >> inset, so there is something wrong there if it happens. > > Is an

Re: Question regarding Cursor::normalize()

Am 06.01.2011 um 10:49 schrieb Stephan Witt: > Am 06.01.2011 um 10:08 schrieb Vincent van Ravesteijn: > >> Second, we should not have a broken cursor. > > You mean one should call Cursor::fixIfBroken() if a broken cursor is possible? > It gets broken after a replace operation of last word in par

Re: Question regarding Cursor::normalize()

Am 06.01.2011 um 10:08 schrieb Vincent van Ravesteijn: > On Thu, Jan 6, 2011 at 8:20 AM, Stephan Witt wrote: >> While looking at #7209 I stumbled over Cursor::normalize(). >> Is it really a good idea to use the cursor inset as math whithout >> any check to write it to debug output? >> > > No. I

Re: Question regarding Cursor::normalize()

On Thu, Jan 6, 2011 at 8:20 AM, Stephan Witt wrote: > While looking at #7209 I stumbled over Cursor::normalize(). > Is it really a good idea to use the cursor inset as math whithout > any check to write it to debug output? > No. It's not, but it's a relic of the path. Besides, it really shouldn't

Re: Question regarding Session management and toolbar state (ticket 7099)

> I see. Another possibility: toggle fullscreen. > > Stephan No I don't think so. GuIView::resetDialogs() call "constructToolbars();". So, only in this case it is absolutely necessary that we have saved the toolbar settings, otherwise they are lost during the construction of the toolbars. Vincen

Re: Question regarding Session management and toolbar state (ticket 7099)

Am 03.01.2011 um 17:10 schrieb Vincent van Ravesteijn: In GuiApplication::readUIFile() the settings for views gets removed if the ui file is newer than the saved timestamp in the settings. Later the non existing settings will be used to initialize the visibility. The default va

Re: Question regarding Session management and toolbar state (ticket 7099)

>>> In GuiApplication::readUIFile() the settings for views gets removed if the >>> ui file is newer than the saved timestamp in the settings. >>> Later the non existing settings will be used to initialize the visibility. >>> The default value for a non existing setting is 0. >>> > I say yes. But w

Re: Question regarding Session management and toolbar state (ticket 7099)

Am 03.01.2011 um 15:25 schrieb Vincent van Ravesteijn: >> Ha! That's it. >> >> The combination of changed ui file and already stored settings is the >> culprit. Thanks! >> >> In GuiApplication::readUIFile() the settings for views gets removed if the >> ui file is newer than the saved timestamp

Re: Question regarding Session management and toolbar state (ticket 7099)

> Ha! That's it. > > The combination of changed ui file and already stored settings is the > culprit. Thanks! > > In GuiApplication::readUIFile() the settings for views gets removed if the > ui file is newer than the saved timestamp in the settings. > Later the non existing settings will be used t

Re: Question regarding Session management and toolbar state (ticket 7099)

Am 03.01.2011 um 13:56 schrieb Abdelrazak Younes: > On 01/03/2011 09:26 AM, Vincent van Ravesteijn wrote: >> Furthermore, I'm not sure yet what causes the bug, because it seems >> that if the user sets the toolbar visibility from within LyX, this >> setting is lost again on the new start-up of LyX

Re: Question regarding Session management and toolbar state (ticket 7099)

On 01/03/2011 02:03 PM, Vincent van Ravesteijn wrote: Furthermore, I'm not sure yet what causes the bug, because it seems that if the user sets the toolbar visibility from within LyX, this setting is lost again on the new start-up of LyX. Why are the settings not stored properly when exiting LyX

Re: Question regarding Session management and toolbar state (ticket 7099)

>> Furthermore, I'm not sure yet what causes the bug, because it seems >> that if the user sets the toolbar visibility from within LyX, this >> setting is lost again on the new start-up of LyX. Why are the settings >> not stored properly when exiting LyX ? > > AFAIR LyX checks the time tag of "ui/d

Re: Question regarding Session management and toolbar state (ticket 7099)

On 01/03/2011 09:26 AM, Vincent van Ravesteijn wrote: Furthermore, I'm not sure yet what causes the bug, because it seems that if the user sets the toolbar visibility from within LyX, this setting is lost again on the new start-up of LyX. Why are the settings not stored properly when exiting LyX

Re: Question regarding Session management and toolbar state (ticket 7099)

> > I would add the name of the toolbar to the error message. Ok. > And if the settings were written with the default value for visibility_ (0) > then restoreSession() happily will restore that nonsense value. > You are right. But we should never write a value of 0. Do you already have an idea

Re: Question regarding Session management and toolbar state (ticket 7099)

Am 03.01.2011 um 13:13 schrieb Vincent van Ravesteijn: > Hmm.. gmail sent the mail to early: > > >> void GuiToolbar::restoreSession() >> { >>QSettings settings; >> >>setVisibility(settings.value(sessionKey() + "/visibility").toInt()); >> } >> >> > > void GuiToolbar::restoreSe

Re: Question regarding Session management and toolbar state (ticket 7099)

Hmm.. gmail sent the mail to early: > void GuiToolbar::restoreSession() > { >        QSettings settings; > >        setVisibility(settings.value(sessionKey() + "/visibility").toInt()); > } > > void GuiToolbar::restoreSession() { QSettings settings; int const error_val = -1;

Re: Question regarding Session management and toolbar state (ticket 7099)

On Mon, Jan 3, 2011 at 12:52 PM, Stephan Witt wrote: > Am 03.01.2011 um 11:28 schrieb Vincent van Ravesteijn: > >>> >>> But somehow there is a connection between visibility flags and the >>> toolbar type, isn't it? The allowauto_ flag depends on visibility. >>> This looks a little bit weird. >> >>

Re: Question regarding Session management and toolbar state (ticket 7099)

Am 03.01.2011 um 11:28 schrieb Vincent van Ravesteijn: >> >> But somehow there is a connection between visibility flags and the >> toolbar type, isn't it? The allowauto_ flag depends on visibility. >> This looks a little bit weird. > > > Yes, this is just an example of bad programming practice.

Re: Question regarding Session management and toolbar state (ticket 7099)

> > But somehow there is a connection between visibility flags and the > toolbar type, isn't it? The allowauto_ flag depends on visibility. > This looks a little bit weird. Yes, this is just an example of bad programming practice. In the Visibility enum, we are now mixing up flags indicating whe

Re: Question regarding Session management and toolbar state (ticket 7099)

Am 03.01.2011 um 09:26 schrieb Vincent van Ravesteijn: >> I encountered the problem yesterday too after recompile and restart without >> updating the resources. >> So I tried to understand the cause and I don't understand the code in >> GuiView::restoreLayout(). >> >> As I read the code the cal

Re: Question regarding Session management and toolbar state (ticket 7099)

On 03/01/2011 09:43, Vincent van Ravesteijn wrote: What I forgot to say is: Why don't we implement saveState() and restoreState() in GuiToolbar which overrides QToolbar::saveState() and restoreState(). Then restoring the visibility of the toolbars is done by QMainWindow::restoreState. (At least,

Re: Question regarding Session management and toolbar state (ticket 7099)

> I said "simplest solution" :-) > I didn't say this is the _right_ solution. > Ok, I'll try to remember this lesson. I often fail to see the simplest solution to problems. Now I know why. Vincent

Re: Question regarding Session management and toolbar state (ticket 7099)

>> What I forgot to say is: Why don't we implement saveState() and >> restoreState() in GuiToolbar which overrides QToolbar::saveState() and >> restoreState(). Then restoring the visibility of the toolbars is done >> by QMainWindow::restoreState. (At least, that is what I would think). > > Yes, tha

Re: Question regarding Session management and toolbar state (ticket 7099)

On 03/01/2011 09:31, Vincent van Ravesteijn wrote: First, there are two different types of settings of toolbars: the location of the toolbars, and the visibility of the toolbars. The former is managed by Qt in QMainWindow::saveState()/restoreState(). The latter is done by LyX in GuiToolbar::saveS

Re: Question regarding Session management and toolbar state (ticket 7099)

On 03/01/2011 09:33, Vincent van Ravesteijn wrote: I think the simplest solution would be to always call restore the toolbars following the toolbars.ui settings and disregard the session management. This would have the side effect that any moved toolbars state will be lost as the toolbars will be

Re: Question regarding Session management and toolbar state (ticket 7099)

> > I think the simplest solution would be to always call restore the toolbars > following the toolbars.ui settings and disregard the session management. > This would have the side effect that any moved toolbars state will be lost > as the toolbars will be restored in their default state. > Why wo

Re: Question regarding Session management and toolbar state (ticket 7099)

> First, there are two different types of settings of toolbars: the > location of the toolbars, and the visibility of the toolbars. The > former is managed by Qt in QMainWindow::saveState()/restoreState(). > The latter is done by LyX in > GuiToolbar::saveSession()/restoreSession(). The reason for t

Re: Question regarding Session management and toolbar state (ticket 7099)

On 03/01/2011 07:49, Stephan Witt wrote: See http://www.lyx.org/trac/ticket/7099 I encountered the problem yesterday too after recompile and restart without updating the resources. So I tried to understand the cause and I don't understand the code in GuiView::restoreLayout(). As I read the co

Re: Question regarding Session management and toolbar state (ticket 7099)

> I encountered the problem yesterday too after recompile and restart without > updating the resources. > So I tried to understand the cause and I don't understand the code in > GuiView::restoreLayout(). > > As I read the code the call of initToolbars() depends on the success of the > restoreSta

Re: Question about hexToInt()

Am 22.12.2010 um 21:44 schrieb Bernhard Roider: > But if you want to avoid the warning you can use an unsigned for scanf and do > a type cast to int Yes, one can do that. The problem I have with it isn't the warning. The compiler warning was a hint to think about that piece of code. The only

Re: Question about hexToInt()

But if you want to avoid the warning you can use an unsigned for scanf and do a type cast to int

Re: Question about hexToInt()

Am 22.12.2010 um 01:59 schrieb Pavel Sanda: > Stephan Witt wrote: >> When in pedantic mode the compiler issues a warning for hexToInt() in >> src/support/lstrings.cpp. >> It doesn't like passing an integer to sscanf when format is "%x" - this is >> for conversion of a pointer. > > unless it fix

Re: Question about hexToInt()

Stephan Witt wrote: > When in pedantic mode the compiler issues a warning for hexToInt() in > src/support/lstrings.cpp. > It doesn't like passing an integer to sscanf when format is "%x" - this is > for conversion of a pointer. unless it fixes some particular bug, another 2.1 candidate... > The

Re: Question about hexToInt()

Am 21.12.2010 um 18:00 schrieb Bernhard Roider: > Just a guess: Does unsignd int work with scanf? Yes, of course. % man sscanf ... The following conversions are available: ... x, X Matches an optionally signed hexadecimal integer; the next pointer must be a pointer to unsigned int. .

Re: Question about hexToInt()

Just a guess: Does unsignd int work with scanf?

Re: Question for ticket 7026 + PATCH

Stephan Witt wrote: > Anfang der weitergeleiteten E-Mail: > >> Von: Enrico Forestieri >> Datum: 5. Dezember 2010 01:49:25 MEZ >> An: lyx-devel@lists.lyx.org >> Betreff: Re: PATCH for ticket 7026 >> >> On Sat, Dec 04, 2010 at 09:37:09PM +0100, Stephan Witt wrote: >> >>> I made another patch for

Re: Question about InsetParamsDialog::checkWidget (abdel?)

On 12/06/2010 12:39 PM, Jean-Marc Lasgouttes wrote: In the aforementioned function, I read: bool const lfun_ok = lyx::getStatus(FuncRequest(code, argument)).enabled(); bool const read_only = buffer().isReadonly(); okPB->setEnabled(!synchronized_view && widget_ok && !read_only &&

Re: Question about citation string

Richard Heck wrote: > I'll just make it untranslatable. It's just a default, and it can be > overridden in layout files. If people object, > then we can make it translatable again, and I'll put in some long comment > about how it can be done. ok pavel

Re: Question about citation string

On 11/30/2010 11:37 AM, Pavel Sanda wrote: Richard Heck wrote: On 11/29/10 7:41 PM, Pavel Sanda wrote: Richard, you introduced this string: "{%author%[[%author%, ]][[{%editor%[[%editor%, ed., ]]}]]}\"%title%\"{%journal" "%[[, {!!}%journal%{!!}]][[{%publisher%[[, %publisher%]][[{%institution" "

Re: Question about citation string

Richard Heck wrote: > On 11/29/10 7:41 PM, Pavel Sanda wrote: >> Richard, >> >> you introduced this string: >> "{%author%[[%author%, ]][[{%editor%[[%editor%, ed., >> ]]}]]}\"%title%\"{%journal" >> "%[[, {!!}%journal%{!!}]][[{%publisher%[[, >> %publisher%]][[{%institution" >> "%[[, %institution%]]

Re: Question about citation string

On 11/29/10 7:41 PM, Pavel Sanda wrote: Richard, you introduced this string: "{%author%[[%author%, ]][[{%editor%[[%editor%, ed., ]]}]]}\"%title%\"{%journal" "%[[, {!!}%journal%{!!}]][[{%publisher%[[, %publisher%]][[{%institution" "%[[, %institution%]]}]]}]]}{%year%[[ (%year%)]]}{%pages%[[, %page

Re: question regarding check for hyperref

> you are looking for somthing like BufferParams.pdfoptions().use_hyperref, Yes, thanks. I used this to fix http://www.lyx.org/trac/ticket/6470. regards Uwe

Re: question regarding check for hyperref

Uwe Stöhr wrote: > I'm looking for a way to check in InsetBibtex.ccp in InsetBibtex::latex > that the user has checked the "use hyperref" checkbox in the PDF section of > the document settings. How can this be done? you are looking for somthing like BufferParams.pdfoptions().use_hyperref, this s

Re: Question regarding "New from template..."

On Mon, Oct 4, 2010 at 9:40 AM, Pavel Sanda wrote: > BH wrote: >> > The "copy solution" was rejected by Pavel in the thread "Re: Beta plans >> > (again, again)" >> > on 17th of September. But I see no other easy and fast solution, currently. >> >> It should perhaps be noted that copying templates

  1   2   3   4   5   6   7   >