On 6/29/09, Guenter Milde wrote:
> > I don't run this "clipman", and the pasting works as usual for
> > 1.6.2 and 1.6.3.
>
>
> But this still does not tell us if we are faced with a bug in clipman or
> with a bug in LyX exposed by clipman.
>
Clipman was recently updated, and I tested v 1.0.2 aga
According to
http://doc.trolltech.com/3.3/qkeyevent.html#details
"Key events for multi media keys are ignored by default. You should
call QKeyEvent::accept() if your widget handles those events."
Currently, LyX calls accept() for everything, so multimedia keys are
undesirably blocked:
http://w
On Mon, Jun 29, 2009 at 11:14 AM, Enrico Forestieri wrote:
> Would you be interested in maintaining the official LyX/Cygwin package?
I'm honored by your recommendation. I'm interested in helping to
automate the maintenance of LyX/Cygwin, but I desperately need to
finish writing my thesis. Procra
Gregory Jefferis schreef:
This patch identifies the author of tracked changes written out to lyx file
with a hash value constructed from author+email
That way the author id never changes on write, allowing painless merging of
files containing tracked changes.
Comments very welcome - this is not
Jürgen Spitzmüller schreef:
Rob Oakes wrote:
Thank you for taking the time to review my code. I greatly appreciate the
feedback. In the attached patch, I have cleaned up the various variables
and other stylistic that you mentioned.
Thanks, looks good now from my POV. If no further c
Pavel Sanda schreef:
Vincent van Ravesteijn - TNW wrote:
Author: sanda
Date: Sun Jun 28 12:37:34 2009
New Revision: 30281
URL: http://www.lyx.org/trac/changeset/30281
Log:
Keep numbering
I would rather adjust the numbering and keep LFUN_OUTLINE_* together, the same
for LFUN_VC_*.
On 2009-06-29, Helge Hafting wrote:
> Liviu Andronic wrote:
>> On Wed, Jun 24, 2009 at 10:56 PM, Guenter Milde
>> wrote:
>>> However, it happens only with the XFCE4 clipboard running
>>> (xfce-clipman 1.0.1).
>> I can confirm xfce-clipman 1.0.1 issues also with lyx 1.6.2. To make
>> copy/pasting
Pavel Sanda schrieb:
Bernhard Roider wrote:
Hello Abdel,
About a year ago i made a latex style + lyx layout file that do exactly
what you want to create a change log table. I extracted the relevant parts
and attached them together with a screen shot of lyx and the resulting pdf
file.
bernh
Pavel Sanda schrieb:
Bernhard Roider wrote:
Hello Abdel,
About a year ago i made a latex style + lyx layout file that do exactly
what you want to create a change log table. I extracted the relevant parts
and attached them together with a screen shot of lyx and the resulting pdf
file.
bernh
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
You mean parsing the files at every startup or preference change and
comparing the parsed value and the default saved value each time?
Attached is an alternative approach. Since we parse the files anyway in
readUIFile, we can just rem
Abdelrazak Younes wrote:
> For the ui toolbar and menu definitions yes. But not for everthing else
> related to geometry and/or visibility settings.
that woul be bad...
pavel
Abdelrazak Younes wrote:
> You mean parsing the files at every startup or preference change and
> comparing the parsed value and the default saved value each time?
Attached is an alternative approach. Since we parse the files anyway in
readUIFile, we can just remember which of the files has the c
Pavel Sanda wrote:
Abdelrazak Younes wrote:
You mean parsing the files at every startup or preference change and
comparing the parsed value and the default saved value each time? Yes that
would be an option indeed. But that would mean that we save the default
values along the current ones.
Abdelrazak Younes wrote:
> You mean parsing the files at every startup or preference change and
> comparing the parsed value and the default saved value each time? Yes that
> would be an option indeed. But that would mean that we save the default
> values along the current ones. As if we do that
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
In this case nothing. The problem is mainly on toolbar settings AFAIR.
So the easy solution is to remove "stdcontext.inc" and other files from
the test in the uifiles loop. You cannot ignore all include file because
the user may have defined
Abdelrazak Younes wrote:
> In this case nothing. The problem is mainly on toolbar settings AFAIR.
> So the easy solution is to remove "stdcontext.inc" and other files from
> the test in the uifiles loop. You cannot ignore all include file because
> the user may have defined a specific name for his
Andre Poenitz wrote:
> > As I stated several times, if we do this, we will have to adapt many many
> > strings of the current UI which would infringe such a convention.
>
> That reason is different from the "HIG" one, isn't it?
Yes, but it's related. The general argument is that I'd like to have
On Mon, Jun 29, 2009 at 08:16:26AM +0200, Jürgen Spitzmüller wrote:
> Andre Poenitz wrote:
> > I do not completely disagree, but the environment is called "align", not
> > "Align". I would consider this as some kind of opposite of a "proper
> > noun" that's not subject to changes by capitalization.
Jürgen Spitzmüller wrote:
Abdelrazak Younes wrote:
AFAIR some people (Pavel among them IIRC) complained that they want
their hand-made changes to the ui file WRT to default windows and
toolbars position to not be ignored. The best solution would be to have
these default values in a QSettings
Abdelrazak Younes wrote:
> AFAIR some people (Pavel among them IIRC) complained that they want
> their hand-made changes to the ui file WRT to default windows and
> toolbars position to not be ignored. The best solution would be to have
> these default values in a QSettings based class which the us
Abdelrazak Younes wrote:
> So the question now is why are these file touched at all? If you don't
> touch it by hand which program does it? Maybe it's a problem of "make
> install"?
touching any ui files happens quite regularly in trunk, thats why the
reset is done regularly too. maybe to enable
Jürgen Spitzmüller wrote:
Pavel Sanda wrote:
I found a recipe which lets me reproduce the toolbar problem reliably:
Just touch any of the ui files (e.g. stdcontext.inc). After the next
restart, the toolbar settings are lost.
good detective work :)
And some luck :-)
The reason
Pavel Sanda wrote:
> > I found a recipe which lets me reproduce the toolbar problem reliably:
> > Just touch any of the ui files (e.g. stdcontext.inc). After the next
> > restart, the toolbar settings are lost.
>
> good detective work :)
And some luck :-)
The reason for this specific behaviour r
Liviu Andronic wrote:
On Wed, Jun 24, 2009 at 10:56 PM, Guenter Milde wrote:
However, it happens only with the XFCE4 clipboard running
(xfce-clipman 1.0.1).
I can confirm xfce-clipman 1.0.1 issues also with lyx 1.6.2. To make
copy/pasting work with this version of clipman, one can simply unche
Enrico Forestieri wrote:
> > Is there any reason the following files aren't stored somewhere in SVN?
> > lyxeditor.c, lyx-win.c, lyxprofile, lyxrc.dist, setup.hint, etc.
> > It's really awkward for me to manually find/download/create all these
> > extra files.
>
> None that I know of. Are there
On Mon, Jun 29, 2009 at 01:24:36AM -0400, Ben M. wrote:
> Also attached is a very messy script I wrote for myself (not for use
> elsewhere) to create a personal Cygwin package for SVN. I intend to
> use this to install on other computers.
I think that your programming knowledge is well above the
Jürgen Spitzmüller wrote:
> Pavel Sanda wrote:
> > i need to reestablish my settings every other day in trunk which version
> > doesn't change at all. i thought that touch configure.py && make do the
> > trick but no, something more is needed it seems.
>
> I found a recipe which lets me reproduce
Pavel Sanda wrote:
i wouldn't believe that such a blind test could reveal something but aparently
was wrong.
The "cat on the keyboard" test finds bugs sometimes too. :-)
This works because developers usually focus on implementing useful
features. They don't always consider "what happens i
Christian Ridderström wrote:
Hi,
I've got a question about the behaviour of LyX which I'm using on
Windows (Uwe's installer), here's the use case:
* I've got a LyX file open in a LyX window.
* I click on a LyX file in my browser (Opera), and a second LyX window is
opened. Actually, I assum
Pavel Sanda wrote:
> i need to reestablish my settings every other day in trunk which version
> doesn't change at all. i thought that touch configure.py && make do the
> trick but no, something more is needed it seems.
I found a recipe which lets me reproduce the toolbar problem reliably:
Just to
Jean-Marc Lasgouttes wrote:
> > add onoff support for "inset-modify changetype xxx" in include inset
>
> Juergen, this is candidate for branch. I yields nice tick marks in the
> context menu of InsetInclude.
OK.
Jürgen
lasgout...@lyx.org writes:
> Author: lasgouttes
> Date: Mon Jun 29 14:41:43 2009
> New Revision: 30305
> URL: http://www.lyx.org/trac/changeset/30305
>
> Log:
> add onoff support for "inset-modify changetype xxx" in include inset
Juergen, this is candidate for branch. I yields nice tick marks in
Christian Ridderström wrote:
For a Windoze user, the '~\Application\...' is probably going to be a
bit difficult to understand
Did we at some point have a separate document with this information,
like how we have a document about the LaTeX configuration?
I don't recall this ever bei
Pavel Sanda wrote:
> > You cannot copy from the preamble?
>
> both directions are problematic. if i select something in lyx window then i
> never get it into preamble. opposite direction works only sometimes, eg
> when something is already in the selection buffer it stays there and dont
> get updat
Jürgen Spitzmüller wrote:
> Pavel Sanda wrote:
> > > PS. Btw, it's annoying that I can't do a copy and paste from this about
> > > window. That could be useful e.g. for people that want to do bug reports.
> >
> > this is even more annoying with preamble box... :)
>
> You cannot copy from the pream
Pavel Sanda wrote:
> > PS. Btw, it's annoying that I can't do a copy and paste from this about
> > window. That could be useful e.g. for people that want to do bug reports.
>
> this is even more annoying with preamble box... :)
You cannot copy from the preamble?
Jürgen
Christian Ridderström wrote:
> PS. Btw, it's annoying that I can't do a copy and paste from this about
> window. That could be useful e.g. for people that want to do bug reports.
this is even more annoying with preamble box... :)
pavel
Pavel Sanda wrote:
Abdelrazak Younes wrote:
The layout format is a LyX internal format, I don't understand why LyX
should parse the comments.
i'm just copying other modules/layouts. if i understand it correctly
the comment is not for lyx binary but for configure.py to work.
OK the
Christian Ridderström writes:
> I've got a question about the behaviour of LyX which I'm using on
> Windows (Uwe's installer), here's the use case:
>
> * I've got a LyX file open in a LyX window.
>
> * I click on a LyX file in my browser (Opera), and a second LyX window is
> opened. Actually, I
That looks very interesting Bernhard, thanks!
Abdel.
Bernhard Roider wrote:
Hello Abdel,
About a year ago i made a latex style + lyx layout file that do
exactly what you want to create a change log table. I extracted the
relevant parts and attached them together with a screen shot of lyx
a
Hi,
When about to install new .layout file in LyX, I was trying to figure
out where (as I'm on Windowz). The answer can be found through the dialog
Help->About LyX
However, the information isn't exactly... detailed. It just says:
LyX Version 1.6.2
(...some date...)
Bernhard Roider wrote:
> Hello Abdel,
>
> About a year ago i made a latex style + lyx layout file that do exactly
> what you want to create a change log table. I extracted the relevant parts
> and attached them together with a screen shot of lyx and the resulting pdf
> file.
>
> bernhard
would
Abdelrazak Younes wrote:
> The layout format is a LyX internal format, I don't understand why LyX
> should parse the comments.
i'm just copying other modules/layouts. if i understand it correctly
the comment is not for lyx binary but for configure.py to work.
pavel
Hi,
I've got a question about the behaviour of LyX which I'm using on Windows
(Uwe's installer), here's the use case:
* I've got a LyX file open in a LyX window.
* I click on a LyX file in my browser (Opera), and a second LyX window is
opened. Actually, I assume that I've started a new inst
Pavel Sanda wrote:
Abdelrazak Younes wrote:
If this is something that will be parsed by LyX, it should not be in
comments.
yes it should :)
Could you please develop?
The layout format is a LyX internal format, I don't understand why LyX
should parse the comments.
Abdel.
Abdelrazak Younes wrote:
> If this is something that will be parsed by LyX, it should not be in
> comments.
yes it should :)
pavel
Pavel Sanda wrote:
hi,
what about adding this into trunk?
If this is something that will be parsed by LyX, it should not be in
comments.
Abdel.
Jürgen Spitzmüller wrote:
I believe one cause of the problems we have with settings that get lost after
reconfigure is the following:
The settings are saved by Qt in a config file that is named from the LyX
version. Thus we get a new, empty config file after every version change, and
thus the
rgheck wrote:
Pavel Sanda wrote:
Richard Heck wrote:
Pavel Sanda wrote:
Abdelrazak Younes wrote:
Is this InsetCounter a good idea? Could this be based on InsetFlex?
i would use such kind of inset myself and have already been thinking
how to add it ;) (maybe named
Jean-Marc Lasgouttes wrote:
Le 25 juin 09 à 13:06, Abdelrazak Younes a écrit :
I would like to create a task list for items defined in different
tables. Ideally I would like to have a number of possibly
configurable fields:
* id: an auto-incremented counter
* title: title of the task
* descri
Vincent van Ravesteijn - TNW wrote:
> >Author: sanda
> >Date: Sun Jun 28 12:37:34 2009
> >New Revision: 30281
> >URL: http://www.lyx.org/trac/changeset/30281
> >
> >Log:
> >Keep numbering
>
> I would rather adjust the numbering and keep LFUN_OUTLINE_* together, the
> same for LFUN_VC_*.
no probl
51 matches
Mail list logo
