Am Freitag, 7. Januar 2011 schrieb Kornel:
> Am Donnerstag, 6. Januar 2011 schrieb sw...@lyx.org:
> > Author: switt
> > Date: Thu Jan 6 21:58:19 2011
> > New Revision: 37139
> > URL: http://www.lyx.org/trac/changeset/37139
> >
> > Log:
> > cmake: Server.cpp is moc-able on win32 only
>
> Since wh
Am Donnerstag, 6. Januar 2011 schrieb sw...@lyx.org:
> Author: switt
> Date: Thu Jan 6 21:58:19 2011
> New Revision: 37139
> URL: http://www.lyx.org/trac/changeset/37139
>
> Log:
> cmake: Server.cpp is moc-able on win32 only
Since when? It was mocable on linux.
Kornel
signature.asc
De
Am Donnerstag, 6. Januar 2011 schrieb Peter Kuemmel:
> > > But ATMit is mixed in the cmake files, and in lyx's code also tabs are
> > > used.
> > >
> > > Peter
> >
> > Mixing is a consequence having tab stop != indent.
> >
> > Kornel
>
> I've no problem switching to spaces. Do you prefer 2,
> there is bug in the current box dialog.
> insert->box->simple frame, page breaks.
> right click for context menu -> settings.
> there is no way how to enable inner box again.
The bug was the menu item. It was a bug that we allowed framed boxes with inner boxes to have page
breaks. Only without
Am 06.01.2011 um 22:26 schrieb Peter Kümmel:
> On 06.01.2011 22:18, Peter Kümmel wrote:
>> On 06.01.2011 22:02, BH wrote:
>>> On Thu, Jan 6, 2011 at 3:55 PM, Stephan Witt wrote:
Am 06.01.2011 um 19:21 schrieb BH:
> On Thu, Jan 6, 2011 at 12:03 PM, Stephan Witt wrote:
>> Am 06.
On 06.01.2011 22:18, Peter Kümmel wrote:
> On 06.01.2011 22:02, BH wrote:
>> On Thu, Jan 6, 2011 at 3:55 PM, Stephan Witt wrote:
>>> Am 06.01.2011 um 19:21 schrieb BH:
>>>
On Thu, Jan 6, 2011 at 12:03 PM, Stephan Witt wrote:
> Am 06.01.2011 um 16:13 schrieb BH:
>
Yes -- cur
On 06.01.2011 22:02, BH wrote:
> On Thu, Jan 6, 2011 at 3:55 PM, Stephan Witt wrote:
>> Am 06.01.2011 um 19:21 schrieb BH:
>>
>>> On Thu, Jan 6, 2011 at 12:03 PM, Stephan Witt wrote:
Am 06.01.2011 um 16:13 schrieb BH:
>>>
>>> Yes -- current svn with Qt-4.7.1 (Carbon, 32 bit). I'm on OS
On Thu, Jan 6, 2011 at 3:55 PM, Stephan Witt wrote:
> Am 06.01.2011 um 19:21 schrieb BH:
>
>> On Thu, Jan 6, 2011 at 12:03 PM, Stephan Witt wrote:
>>> Am 06.01.2011 um 16:13 schrieb BH:
>>>
>>
>> Yes -- current svn with Qt-4.7.1 (Carbon, 32 bit). I'm on OS X 10.6.5,
>> using the 10.5 SDK.
>
> OS
Am 06.01.2011 um 19:21 schrieb BH:
> On Thu, Jan 6, 2011 at 12:03 PM, Stephan Witt wrote:
>> Am 06.01.2011 um 16:13 schrieb BH:
>>
>
> Yes -- current svn with Qt-4.7.1 (Carbon, 32 bit). I'm on OS X 10.6.5,
> using the 10.5 SDK.
OS X 10.6.5, Qt-4.7.1 (Carbon, 32 bit), 10.5 SDK.
It's all the sam
> >
> > But ATMit is mixed in the cmake files, and in lyx's code also tabs are
> > used.
> >
> > Peter
>
> Mixing is a consequence having tab stop != indent.
>
> Kornel
I've no problem switching to spaces. Do you prefer 2,3, or 4?
Peter
--
NEU: FreePhone - kostenlos mobil telefonieren
Am Donnerstag, 6. Januar 2011 schrieb Peter Kuemmel:
> > That's, what I don't like much. Too many people define the tab value
> > different.
> >
> >
> >
> > Kornel
>
> But ATMit is mixed in the cmake files, and in lyx's code also tabs are
> used.
>
> Peter
Mixing is a consequence having t
Am Donnerstag, 6. Januar 2011 schrieb Stephan Witt:
> Am 06.01.2011 um 19:27 schrieb Kornel:
> > Am Donnerstag, 6. Januar 2011 schrieb kuem...@lyx.org:
> > > Log:
> > > cmake: use tabs
> >
> > That's, what I don't like much. Too many people define the tab value
> > different.
>
> For leading tabs
Original-Nachricht
> Datum: Thu, 06 Jan 2011 18:29:36 +0100
> Von: "Peter Kuemmel"
> An: lyx-devel@lists.lyx.org
> Betreff: Re: status.**x in msvc project
>
> Original-Nachricht
> > Datum: Tue, 4 Jan 2011 15:33:07 +0100
> > Von: Kornel
> > An: lyx-devel@list
Original-Nachricht
> Datum: Thu, 6 Jan 2011 19:27:17 +0100
> Von: Kornel
> An: lyx-devel@lists.lyx.org
> Betreff: Re: r37132 - lyx-devel/branches/BRANCH_1_6_X/development/cmake/src
> Am Donnerstag, 6. Januar 2011 schrieb kuem...@lyx.org:
> > Log:
> > cmake: use tabs
>
> That's
Am 06.01.2011 um 19:27 schrieb Kornel:
> Am Donnerstag, 6. Januar 2011 schrieb kuem...@lyx.org:
> > Log:
> > cmake: use tabs
> That's, what I don't like much. Too many people define the tab value
> different.
For leading tabs any value results in perfectly aligned rows.
So, I don't understand yo
Am Donnerstag, 6. Januar 2011 schrieb kuem...@lyx.org:
> Log:
> cmake: use tabs
That's, what I don't like much. Too many people define the tab value different.
Kornel
signature.asc
Description: This is a digitally signed message part.
On Thu, Jan 6, 2011 at 12:03 PM, Stephan Witt wrote:
> Am 06.01.2011 um 16:13 schrieb BH:
>
>> This is a follow-up to problems we've had with on-screen display of
>> fonts, where the spacing between words and cursor position was not
>> calculated correctly due to ligatures, swooshes, or other font
Original-Nachricht
> Datum: Tue, 4 Jan 2011 15:33:07 +0100
> Von: Kornel
> An: lyx-devel@lists.lyx.org
> Betreff: Re: status.**x in msvc project
> Am Dienstag, 4. Januar 2011 schrieb Vincent van Ravesteijn:
> > But now I realise you might not use MSVC too often ;
> >
> > Vince
Am 06.01.2011 um 16:13 schrieb BH:
> This is a follow-up to problems we've had with on-screen display of
> fonts, where the spacing between words and cursor position was not
> calculated correctly due to ligatures, swooshes, or other font
> features. My guess is that the fix to that problem was to
This is a follow-up to problems we've had with on-screen display of
fonts, where the spacing between words and cursor position was not
calculated correctly due to ligatures, swooshes, or other font
features. My guess is that the fix to that problem was too general,
creating problems with monospaced
On Thu, Jan 6, 2011 at 1:44 AM, Stephan Witt wrote:
> Am 05.01.2011 um 01:00 schrieb BH:
>
>> On Tue, Jan 4, 2011 at 3:21 PM, Vincent van Ravesteijn wrote:
I have to admit that I don't understand the problem.
I don't understand what version "trunk" refers in the ticket
comments - 1
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
> 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
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
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
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
On Thu, Jan 6, 2011 at 9:58 AM, Vincent van Ravesteijn wrote:
>> In principle this works out-of-the-box because the settings are
>> restored by Qt.
>
> What I forgot to say is:
>
Last,
Have you ever thought about a search history ?
Vincent
> In principle this works out-of-the-box because the settings are
> restored by Qt.
What I forgot to say is:
If you also want to remember the settings in the dialog, like
word-wrap, case-sensitivity and so on, you need to implement the
following two functions:
- void FindAndReplace::restoreSessi
On Wed, Jan 5, 2011 at 4:13 PM, Tommaso Cucinotta wrote:
> Il 05/01/2011 16:05, Vincent van Ravesteijn ha scritto:
>>
>> A side-effect also was that we don't remember the outliner visibility
>> status on exit, because all documents were closed on exit and also the
>> outliner then. I think you wan
29 matches
Mail list logo
