On Fri, May 23, 2014 at 6:01 PM, Richard Heck wrote:
> On 05/23/2014 05:49 PM, Scott Kostyshak wrote:
>>>
>>> Which it should as a result of
>>> resetting the
>>> cursor since e.g. the TOC needs updating to reflect the new position.
>>> Indeed, not all dialogs
>>> need updating, but we don't have
On 05/23/2014 05:49 PM, Scott Kostyshak wrote:
Which it should as a result of
resetting the
cursor since e.g. the TOC needs updating to reflect the new position.
Indeed, not all dialogs
need updating, but we don't have such fine-grained information.
Is there an example of a dialog that needs to
On Fri, May 23, 2014 at 5:24 PM, Richard Heck wrote:
>> Inside of ViewSourceWidget::updateView is it possible to tell whether
>> it was called because of a cursor movement or because of an
>> insertion/edit?
>
>
> I don't think so. You'd need to get this information during the dispatch, I
> think
On 05/23/2014 05:11 PM, Scott Kostyshak wrote:
When "Automatic update" is checked, the source view updates whenever I
move the cursor. I think it would be nice if this did not happen when
moving the cursor within the same paragraph (when "Current paragraph"
is selected), unless we plan on trackin
On 10/29/2011 03:57 PM, Vincent van Ravesteijn wrote:
> Op 29-10-2011 21:54, Richard Heck schreef:
>> On 10/29/2011 03:48 PM, Vincent van Ravesteijn wrote:
>>> Op 29-10-2011 21:11, Richard Heck schreef:
I'm seeing PNG and EPS as output format options in the source view
window. That seems
Op 29-10-2011 21:54, Richard Heck schreef:
On 10/29/2011 03:48 PM, Vincent van Ravesteijn wrote:
Op 29-10-2011 21:11, Richard Heck schreef:
I'm seeing PNG and EPS as output format options in the source view
window. That seems wrong. Would it be better here just to list the
possible backends? i.
On 10/29/2011 03:48 PM, Vincent van Ravesteijn wrote:
> Op 29-10-2011 21:11, Richard Heck schreef:
>> I'm seeing PNG and EPS as output format options in the source view
>> window. That seems wrong. Would it be better here just to list the
>> possible backends? i.e., the formats LyX can output direc
Op 29-10-2011 21:11, Richard Heck schreef:
I'm seeing PNG and EPS as output format options in the source view
window. That seems wrong. Would it be better here just to list the
possible backends? i.e., the formats LyX can output directly?
Richard
I don't see PNG and EPS.
By the way, the whol
Pavel Sanda wrote:
> what about putting update button next to automatic update?
> we spend quite some time to make this dialog resizable to
> as small vertizal size as possible.
Personally, I find horizontal space much more valuable. The dialog still is
pretty narrow (vertically) with the new wid
Jürgen Spitzmüller wrote:
> Opinions?
what about putting update button next to automatic update?
we spend quite some time to make this dialog resizable to
as small vertizal size as possible.
pavel
Jürgen Spitzmüller wrote:
> I come back to this. Attached is a reworked version of the view source
> part. I have added a cache for the default flavor, since it is overkill to
> recheck for the flavor on each key stroke.
And here comes a further addition: this adds a combo with the available outpu
On 12/04/2010 11:03 AM, Jürgen Spitzmüller wrote:
Richard Heck wrote:
My only question is one I think JMarc asked earlier, namely, whether we
want to provide some
mechanism for indicating flavor in some config file, rather than trying
to guess it.
We do not guess it. I introduced a converter fl
Richard Heck wrote:
> My only question is one I think JMarc asked earlier, namely, whether we
> want to provide some
> mechanism for indicating flavor in some config file, rather than trying
> to guess it.
We do not guess it. I introduced a converter flag that defines the (latex)
flavor, and we
On 12/04/2010 09:54 AM, Jürgen Spitzmüller wrote:
Jürgen Spitzmüller wrote:
Jürgen Spitzmüller wrote:
A patch along this line is attached. We still have to hardcode xhtml,
since there's no dedicated converter where we could derive a xhtml flag
from.
I committed the backend=flavor part, since
Jürgen Spitzmüller wrote:
> Jürgen Spitzmüller wrote:
> > A patch along this line is attached. We still have to hardcode xhtml,
> > since there's no dedicated converter where we could derive a xhtml flag
> > from.
>
> I committed the backend=flavor part, since this is a step forward anyway
> and
Le 30/11/2010 10:50, Jürgen Spitzmüller a écrit :
Jürgen Spitzmüller wrote:
A patch along this line is attached. We still have to hardcode xhtml,
since there's no dedicated converter where we could derive a xhtml flag
from.
I committed the backend=flavor part, since this is a step forward any
Jürgen Spitzmüller wrote:
> A patch along this line is attached. We still have to hardcode xhtml,
> since there's no dedicated converter where we could derive a xhtml flag
> from.
I committed the backend=flavor part, since this is a step forward anyway and
removes some bad hardcoding.
Jürgen
Jean-Marc Lasgouttes wrote:
> Second try, now that I read the code: change the converter flag "latex" to
> take the form "latex=xetex" or whatever to indicate the latex flavor that
> we want. "latex" will be equivalent to "latex=latex".
>
> With this, the information does not need to be hardcoded
> this is interesting idea even for other backends like docbook
>
> pavel
>
AFAIK this already works for docbook.
Vincent
Le 24 nov. 2010 à 22:01, Jürgen Spitzmüller a écrit :
>> I do not understand why we need to do that since latex export requires
>> this information anyway. We just have to look at the first intermediate
>> step of the lyx->...->output converter chain.
>
> I cannot follow you.
Second try, now that
Jean-Marc Lasgouttes wrote:
> I do not understand why we need to do that since latex export requires
> this information anyway. We just have to look at the first intermediate
> step of the lyx->...->output converter chain.
I cannot follow you.
Jürgen
Le 24 nov. 2010 à 17:04, Jürgen Spitzmüller a écrit :
> Actually, I was just working on a patch that would take the default output
> format instead of just LaTeX or XeTeX for the source view. It would roughly
> look as follows (without XHTML and DocBook so far, but the direction should
> be clea
On 11/24/2010 11:04 AM, Jürgen Spitzmüller wrote:
Pavel Sanda wrote:
this is interesting idea even for other backends like docbook
Actually, I was just working on a patch that would take the default output
format instead of just LaTeX or XeTeX for the source view. It would roughly
look as foll
Pavel Sanda wrote:
> this is interesting idea even for other backends like docbook
Actually, I was just working on a patch that would take the default output
format instead of just LaTeX or XeTeX for the source view. It would roughly
look as follows (without XHTML and DocBook so far, but the di
Richard Heck wrote:
>
> How hard would it be to have View>Source output, say, HTML, if that is the
> default view format for the document?
this is interesting idea even for other backends like docbook
pavel
On Sun, Jan 11, 2009 at 09:07:54AM +0100, Jürgen Spitzmüller wrote:
> Enrico Forestieri wrote:
> > > Enrico Forestieri wrote:
> > > > Please try the attached patch. It works for me even with Qt 4.2.
> > > > The Source View window always opens at its minimum height.
> > >
> > > yes, that works here
Enrico Forestieri wrote:
> > Enrico Forestieri wrote:
> > > Please try the attached patch. It works for me even with Qt 4.2.
> > > The Source View window always opens at its minimum height.
> >
> > yes, that works here.
>
> Jürgen?
go ahead.
Jürgen
On Sat, Jan 10, 2009 at 07:38:56PM +0100, Pavel Sanda wrote:
> Enrico Forestieri wrote:
> > Please try the attached patch. It works for me even with Qt 4.2.
> > The Source View window always opens at its minimum height.
>
> yes, that works here.
Jürgen?
--
Enrico
Enrico Forestieri wrote:
> Please try the attached patch. It works for me even with Qt 4.2.
> The Source View window always opens at its minimum height.
yes, that works here.
pavel
On Sat, Jan 10, 2009 at 06:31:42PM +0100, Pavel Sanda wrote:
> Enrico Forestieri wrote:
> > With Qt 4.4 I am still able to reduce the height such that only about
> > four lines of source are shown. With Qt 4.2 the height cannot be reduced
> > below about a dozen lines, but this happens with or wit
On Sat, Jan 10, 2009 at 06:15:56PM +0100, Pavel Sanda wrote:
> Jürgen Spitzmüller wrote:
> > Enrico Forestieri wrote:
> > > Using Qt 4.2, the View Source window is split such that only about 1/3
> > > of the full width is used for displaying the source (see the attached
>
> :( its nightmare to ge
Enrico Forestieri wrote:
> With Qt 4.4 I am still able to reduce the height such that only about
> four lines of source are shown. With Qt 4.2 the height cannot be reduced
> below about a dozen lines, but this happens with or without my patch.
which exactly version of qt? the recipy in the other m
Pavel Sanda wrote:
> Pavel Sanda wrote:
> > didn't fix the
>
> initialization
>
> > outliner/source w. bug and some code didn't get initialized after
> > launch. it also means that removing some code inside
> > ViewSourceWidget::ViewSourceWidget()
>
> i not sure now ViewSourceWidget::ViewS
Pavel Sanda wrote:
> didn't fix the
initialization
> outliner/source w. bug and some code didn't get initialized after
> launch. it also means that removing some code inside
> ViewSourceWidget::ViewSourceWidget()
i not sure now ViewSourceWidget::ViewSourceWidget() was the routine skipped.
Jürgen Spitzmüller wrote:
> Enrico Forestieri wrote:
> > Using Qt 4.2, the View Source window is split such that only about 1/3
> > of the full width is used for displaying the source (see the attached
:( its nightmare to get this dialog right.
> > without-patch.png). The attached patch corrects
On Sat, Jan 10, 2009 at 05:19:45PM +0100, Jürgen Spitzmüller wrote:
> Enrico Forestieri wrote:
> > Using Qt 4.2, the View Source window is split such that only about 1/3
> > of the full width is used for displaying the source (see the attached
> > without-patch.png). The attached patch corrects th
Enrico Forestieri wrote:
> Using Qt 4.2, the View Source window is split such that only about 1/3
> of the full width is used for displaying the source (see the attached
> without-patch.png). The attached patch corrects this (with-patch.png).
> I verified that later versions of Qt are not affected
Abdelrazak Younes wrote:
Dov Feldstern wrote:
Hi!
Starting quite recently (within the last two weeks?) the view source
and outliner widgets are open when LyX starts;
Only the first time. Afterwards, if session handling is enabled, LyX
will memorize the last window state, including toolbars
Dov Feldstern wrote:
Hi!
Starting quite recently (within the last two weeks?) the view source
and outliner widgets are open when LyX starts;
Only the first time. Afterwards, if session handling is enabled, LyX
will memorize the last window state, including toolbars and dock widgets
visibil
On Sunday 25 March 2007 9:36:56 pm Jean-Marc Lasgouttes wrote:
> Is docbook source working now?
It has been for some time. :-)
> JMarc
--
José Abílio
> "Jürgen" == Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
Jürgen> Jean-Marc Lasgouttes wrote:
>> Is docbook source working now?
Jürgen> At least I can see something that looks like XML with the
Jürgen> docbook example.
So we really need to support it :)
JMarc
Jean-Marc Lasgouttes wrote:
> Is docbook source working now?
At least I can see something that looks like XML with the docbook example.
Jürgen
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Jürgen Spitzmüller wrote:
>> Michael Gerz wrote:
>>> I suggest renaming the menu item and command to "LaTeX Source".
>>> OK?
>> I think that's not correct if you are working with docbook.
Abdelrazak> Backend Source?
Am Sonntag, 25. März 2007 17:23 schrieb Abdelrazak Younes:
> Jürgen Spitzmüller wrote:
> > Michael Gerz wrote:
> >> I suggest renaming the menu item and command to "LaTeX Source". OK?
> >
> > I think that's not correct if you are working with docbook.
>
> Backend Source?
Not better IMHO.
> I gu
Jürgen Spitzmüller wrote:
Michael Gerz wrote:
I suggest renaming the menu item and command to "LaTeX Source". OK?
I think that's not correct if you are working with docbook.
Backend Source?
I guess we could also modify the menu item depending on the document engine.
Abdel.
Michael Gerz wrote:
> I suggest renaming the menu item and command to "LaTeX Source". OK?
I think that's not correct if you are working with docbook.
Jürgen
46 matches
Mail list logo
