On Mon, 17 Mar 2008 23:30:46 -0400
rgheck <[EMAIL PROTECTED]> wrote:
> Dominik Böhm wrote:
> > Hello,
> >
> > I just saw that some of the latest svn commits changed the rendering
> > behavior of char-style insets. I liked the way they were rendered
> > before (without the handle and possibility to
Dominik Böhm wrote:
Hello,
I just saw that some of the latest svn commits changed the rendering
behavior of char-style insets. I liked the way they were rendered
before (without the handle and possibility to collapse) much more. Now
my text looks like a mess, as I am using char-styles intensivel
On 18/3/08 10:33 AM, "Stefan Schimanski" <[EMAIL PROTECTED]> wrote:
>>> File>New Window.
>>
>> I just found that the new window is a mirror of the original: if you
>> open a
>> file, it's opened in both, if you close a file, it's closed in both.
>> Was
>> that the intention?
>
> Here (on Mac) i
On 18/3/08 10:35 AM, "Stefan Schimanski" <[EMAIL PROTECTED]> wrote:
>
> Am 17.03.2008 um 07:09 schrieb Eric Cavalcanti:
>
>> Hi,
>>
>> This is a suggestion for improvement on the tabs when we have
>> multiple open
>> files. Those who work with many open files (as you may need in a
>> thesis or
Am 17.03.2008 um 07:09 schrieb Eric Cavalcanti:
Hi,
This is a suggestion for improvement on the tabs when we have
multiple open
files. Those who work with many open files (as you may need in a
thesis or a
book with many chapters) have probably noticed that the caption in
the tabs
all be
Am 18.03.2008 um 01:24 schrieb Eric Cavalcanti:
Hi again,
Another related suggestion: there should be an option to open in a
new
window, so we can put two windows side-by-side when editing
multiple files.
This would greatly improve efficiency when editing a file with
data from
another o
Hi again,
>> Another related suggestion: there should be an option to open in a new
>> window, so we can put two windows side-by-side when editing multiple files.
>> This would greatly improve efficiency when editing a file with data from
>> another one.
>>
>>
> File>New Window.
I just found
Hi,
On 18/3/08 3:00 AM, "Richard Heck" <[EMAIL PROTECTED]> wrote:
> Eric Cavalcanti wrote:
>> Hi,
(...)
> Can you please bugzilla some of this? Some of these are enhancements,
> but some of them are just bugs.
Will do.
>> Another related suggestion: there should be an option to open in a new
>>
Stefan Schimanski wrote:
To bring this thread to the top again: what is the status for the alpha?
i would like to commit my tab lines patch before we freeze
Am 17.03.2008 um 23:09 schrieb Uwe Stöhr:
Stefan Schimanski schrieb:
To bring this thread to the top again: what is the status for the
alpha?
I would propose that we make a mini freeze of 24 or 48 hours to
only include show stopper fixes. Opinions?
24 hors are fine with me. But your bugf
Stefan Schimanski schrieb:
To bring this thread to the top again: what is the status for the alpha?
I would propose that we make a mini freeze of 24 or 48 hours to only
include show stopper fixes. Opinions?
24 hors are fine with me. But your bugfix for 4566 should go in before if
possible w
Hello,
I just saw that some of the latest svn commits changed the rendering
behavior of char-style insets. I liked the way they were rendered
before (without the handle and possibility to collapse) much more. Now
my text looks like a mess, as I am using char-styles intensively. Why
did you change
Am 13.03.2008 um 08:28 schrieb Uwe Stöhr:
> So I am proposing two dates:
> alpha 1 - 19 March
> beta 1 - 2 April
Fine with me. But the new version contains so many new features that
I will not be ready with the docs. I won't find time to work on the
docs before beta 1. So I
Stefan Schimanski schrieb:
Wild guess: #include
Yes this did the trick. This is now needed for a couple of files:
#include
I'm wondering why this is the case and why nobody else than needed this
inclusion.
thanks and regards
Uwe
Jürgen Spitzmüller wrote:
Dov Feldstern wrote:
I've tested your file with the patch committed at r23756, and it seems
to work. Let me know if there are any additional problems.
Yes, this seems to solve the problem. Thanks!
but it introduces new ones. If the table cell is not fi
> It would also be nice to be able to drag and drop to change the order of the
> tabs.
this is implemented in 1.6
p
Jean-Marc Lasgouttes wrote:
Richard Heck <[EMAIL PROTECTED]> writes:
I would be surprised.
You'd be surprised if we didn't complain? Are we, as a group, that docile?
No, I'd be surprised that 4.3 cannot accept code that is valid in 4.2.
At least the documentation sugg
Richard Heck <[EMAIL PROTECTED]> writes:
>> I would be surprised.
> You'd be surprised if we didn't complain? Are we, as a group, that docile?
No, I'd be surprised that 4.3 cannot accept code that is valid in 4.2.
JMarc
Jean-Marc Lasgouttes wrote:
Because then I would have used QDrag::start, just to get complains by
Qt 4.3 people that it does not complile.
I would be surprised.
You'd be surprised if we didn't complain? Are we, as a group, that docile?
rh
Eric Cavalcanti wrote:
Hi,
This is a suggestion for improvement on the tabs when we have multiple open
files. Those who work with many open files (as you may need in a thesis or a
book with many chapters) have probably noticed that the caption in the tabs
all become ".." after a few files ar
> (which should then be indicated, sorry to nag ;-)
i added it to
p
> If contextual menus work in fullscreen (at least on Mac they do), why not
> put a Fullscreen command there. Then you simply need to right-click, select
yes good idea
pavel
On 16 mar 2008, at 15.55, Anders Ekberg wrote:
On 16 mar 2008, at 14.02, Pavel Sanda wrote:
this does not generally solve the problem. on other platform you
don't
get the menu at all. it has already been requested to make some
indication
how to get back but currently i don't see good solut
On Sunday 16 March 2008 15:57:28 Edwin Leuven wrote:
>
> comments welcome
Consistency is a nice word and I like it. :-)
I like the idea of the patch although I have not tested it.
--
José Abílio
On Monday 17 March 2008 11:08:04 Stefan Schimanski wrote:
> Am 17.03.2008 um 11:59 schrieb Uwe Stöhr:
> > I wrote:
> >> D:\LyXSVN\lyx-devel\src\InsetList.cpp(66) : error C3861:
> >> 'lower_bound': identifier not found
> >> D:\LyXSVN\lyx-devel\src\InsetList.cpp(74) : error C3861:
> >> 'lower_bound':
Angus Leeming <[EMAIL PROTECTED]> writes:
> I notice that the LyX donations page,
> http://www.lyx.org/donations.php, is unable to display the PayPal
> image. As a result, the admonition to "click the button below" isn't
> going to bring in much hard cash :-P
>
> Ah, interesting. All looks fine wi
Am 17.03.2008 um 11:59 schrieb Uwe Stöhr:
I wrote:
D:\LyXSVN\lyx-devel\src\InsetList.cpp(66) : error C3861:
'lower_bound': identifier not found
D:\LyXSVN\lyx-devel\src\InsetList.cpp(74) : error C3861:
'lower_bound': identifier not found
Does nobody else have this problem? I had again a l
I wrote:
D:\LyXSVN\lyx-devel\src\InsetList.cpp(66) : error C3861: 'lower_bound':
identifier not found
D:\LyXSVN\lyx-devel\src\InsetList.cpp(74) : error C3861: 'lower_bound':
identifier not found
Does nobody else have this problem? I had again a look what change since Friday causes this
compi
Dov Feldstern wrote:
> > I've tested your file with the patch committed at r23756, and it seems
> > to work. Let me know if there are any additional problems.
>
> Yes, this seems to solve the problem. Thanks!
but it introduces new ones. If the table cell is not fixed-width, only
Standard (or Plai
Am 17.03.2008 um 11:27 schrieb Jean-Marc Lasgouttes:
[EMAIL PROTECTED] writes:
+#ifdef __APPLE_CC__
+ single_window = false;
+#else
+ single_window = true;
+#endif
Stefan, as I wrote earlier this is not how it should be done. Could
you check that the following patch is equivalen
[EMAIL PROTECTED] writes:
> +#ifdef __APPLE_CC__
> + single_window = false;
> +#else
> + single_window = true;
> +#endif
Stefan, as I wrote earlier this is not how it should be done. Could
you check that the following patch is equivalent? I am not sure that a
cmake build will catch this l
On Monday 17 March 2008 09:24:38 Jürgen Spitzmüller wrote:
>
> > There are lots of code where lines with \n are added. This breaks a
> > fundamental assumption of lyx2lyx that says that each line is in a
> > separate list entry.
>
> I wasn't aware of this.
No. It is implicit since it follows the
José Matos wrote:
> OK, please commit.
Done, thanks.
> BTW I will clean the code of lyx_1_6.py before release.
Good.
> There are lots of code where lines with \n are added. This breaks a
> fundamental assumption of lyx2lyx that says that each line is in a separate
> list entry.
I wasn't aware
On Saturday 15 March 2008 10:56:03 Stefan Schimanski wrote:
> Added it to development/mathmacros.
>
> Moreover I also commited some testcases which I used frequently.
>
> Stefan
Thanks. :-)
--
José Abílio
On Sunday 16 March 2008 15:12:39 Jürgen Spitzmüller wrote:
> > José, can I shove it in?
>
> Take this instead.
>
> It changes
> some text\InsetSpace type
> some more text
> to
> some text
> \begin_inset Space type
> \end_inset
> some more text
>
> whi
Stefan Schimanski <[EMAIL PROTECTED]> writes:
>> Why cannot people use qt 4.2 for development? We have had a lot of
>> compatibility problems with qt 4.3.
I use Qt4.2 too. Usually problems are noticed pretty fast. What I am
not sure about, though, is whether somebody tests LyX 1.5.x with Qt 4.1.
36 matches
Mail list logo
