Peter Kümmel wrote:
> This is the Qt message:
> QPixmap::operator=: Cannot assign to pixmap during painting
>
> and happens at >
> void QWorkArea::resizeEvent(QResizeEvent * resizeEvent)
> {
> workWidth_ = viewport()->width();
> workHeight_ = viewport()->height();
>
> verti
Peter Kümmel wrote:
> Now I see the next bug:
>
> When you often open and close lyx in the
> normal mode the windows moves down on
> the screen.
> So the stored coordinates are not that
> of the upper left corner.
>
> I will have a look an this, and will also
> post a 'final patch' :-)
>
> Peter
Bo Peng wrote:
Later on, when installing aspell English dictionary, the installer
runs OK, but exits with error message "the setup wizard of the English
spell checker dictionary was not completed, Do you want to run the set
up again?".
That's because of the new Aspell dictionaries. The next bui
I am trying the installer on a new machine with which I probably do
not have administrative privilege. I get downloading error for both
miktex and imagemagik, but I can download ghostview and ghostscript.
Error messages say hostname resolving problem.
Later on, when installing aspell English dic
I am wondering what if the
> built-in (?) download link is no longer valid.
Good. SourceForge and CTAN never delete files, so the download links
should remain valid. Of course the files can also be hosted on the LyX
server, Lars should probably decide.
I am trying the installer on a new machine
Hi!
I have tried with/ and without "--disable-stdlib-debug"
and with "--disable-concept-checks"
I got the same messages.
Alex
> | $ ./configure --prefix=/home/alex/lyx/bin/lyx150svn-qt
> | --with-frontend=qt --with-qt-libraries=/usr/lib/qt3/lib64
> | --with-version-suffix=-150svn-qt --disable-
On Tuesday 13 June 2006 13:16, Helge Hafting wrote:
> > Or did I misunderstood what you said?
> >
>
> I think we agree about this, it is Lars that seems to hold back.
I would like not to forget this issue. Please could you fill a bugzilla
entry for 1.5.0. I agree that something needs to be
And are they well-docmented behaviors?
Yes.
At least I do not see them in ./configure --help. I am really
wondering how many people in this list know the difference between
CCFLAGS and CPPFLAGS.
Anyway, if scons provides CCFLAGS and CPPFLAGS, maybe scons already
knows how to handle them. I w
Bo Peng wrote:
> Angus Leeming wrote:
>> We do things a little differently to this in the
>> Makefile.ams.
> These look way too complicated! And are they
> well-docmented behaviors?
Yes.
> I think I will implement only what I proposed.
Your call. But we took several years to arrive at this
lev
On Mon, Jun 12, 2006 at 11:42:25PM +0300, Martin Vermeer wrote:
> On Mon, Jun 12, 2006 at 10:18:04PM +0300, Martin Vermeer wrote:
> > On Mon, Jun 12, 2006 at 12:47:56PM +0200, Juergen Spitzmueller wrote:
> > > Juergen Spitzmueller wrote:
> > > > I'm seeing drawing errors in 1.4 every now and then w
Andrzej Tomaszewski wrote:
What you mean by correct settings?
On both computers main coding system is of course cp-1250.
In the indicated place (I have only laptop handy) I have many things
checked, among them UTF-7 and -8, ISO-8859-1 and -2...
Should I have some special conversion tables insta
We do things a little differently to this in the
Makefile.ams.
If someone passes in CCFLAGS (or defines a CCFLAGS)
environment variable, then this is used verbatim. The
user is then responsible for all CCFLAGS options
passed to the compiler.
We also use CPPFLAGS (IIRC) to enable the user to
spec
Bo Peng wrote:
>> Abdelrazak Younes wrote:
>> One bug though: When I pass CCFLAGS="-O3 -w"
>> to scons, I see that the options is just appended
>> to the default options (-O2 -Wall), ex:
>> g++ -o
release\common\frontends\qt3\QCommandBuffer.o
>> -c -O3 -w -Wall -O2
> What exactly do you mean? D
Sure, I won't touch the msvc flags.
I meant that if you pass your own flags when building msvs projects,
you should make sure that /Zi, /map etc are passed as well.
I will investigate your other bug reports later today.
Bo
Bo Peng wrote:
>> Seems all is in the lyx project a little bit different. ;)
>
> I know that tortoiseSVN and other svn clients have better log support,
> but I am using the old and faithful 'svn log | more'
>
> Maybe others like your style better?
No. The consensus was that we use the log m
Bo Peng wrote:
produce a hell lot of warning. It is not very important as, the way it
is now, the two first options take precedence over the "-Wall -O2". But
it is a bit ugly...
What about if I want to add profiling support (-pg option)?
I was trying to set some default flags for debug and rel
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Peter Kümmel wrote:
Am Dienstag, 13. Juni 2006 16:19 schrieb Abdelrazak Younes:
No bug under Linux, also no error message.
Indeed. Now I see it too as well in the "younes" branch. But I am 100%
sure those two bugs weren't there before.
Fine, now
produce a hell lot of warning. It is not very important as, the way it
is now, the two first options take precedence over the "-Wall -O2". But
it is a bit ugly...
What about if I want to add profiling support (-pg option)?
I was trying to set some default flags for debug and release mode.
Witho
Bo Peng wrote:
One bug though: When I pass CCFLAGS="-O3 -w" to scons, I see that the
options is just appended to the default options (-O2 -Wall), ex:
g++ -o release\common\frontends\qt3\QCommandBuffer.o -c -O3 -w -Wall -O2
What exactly do you mean? Do you want me to remove -O2 if -O3 is
passe
Seems all is in the lyx project a little bit different. ;)
I know that tortoiseSVN and other svn clients have better log support,
but I am using the old and faithful 'svn log | more'
Maybe others like your style better?
Bo
Peter Kümmel wrote:
Do you have more than text in this document in the first show up?
the attached document reproduces it.
the second line has "noun" on and is the culprit
another disturbing thing:
deleting line 2 and maximizing still gives funky resizing
however after closing and reopening
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
>> Am Dienstag, 13. Juni 2006 16:19 schrieb Abdelrazak Younes:
>>
>> No bug under Linux, also no error message.
>>
>>> Indeed. Now I see it too as well in the "younes" branch. But I am 100%
>>> sure those two bugs weren't there before.
>>
>> Fine, now
Peter Kümmel wrote:
Am Dienstag, 13. Juni 2006 16:19 schrieb Abdelrazak Younes:
No bug under Linux, also no error message.
Indeed. Now I see it too as well in the "younes" branch. But I am 100%
sure those two bugs weren't there before.
Fine, now the question is before WHAT?
I don't know! A
Bo Peng wrote:
> Hi, Peter,
>
> Could you please shorten your svn log message a little bit? With all
> the diff in the log, it is difficult for me to see what is going on.
> After all, the diff can be easily obtained with svn diff -r.
>
> Cheers,
> Bo
>
>
Seems all is in the lyx project a littl
Hi, Peter,
Could you please shorten your svn log message a little bit? With all
the diff in the log, it is difficult for me to see what is going on.
After all, the diff can be easily obtained with svn diff -r.
Cheers,
Bo
Am Dienstag, 13. Juni 2006 16:19 schrieb Abdelrazak Younes:
No bug under Linux, also no error message.
> Indeed. Now I see it too as well in the "younes" branch. But I am 100%
> sure those two bugs weren't there before.
Fine, now the question is before WHAT?
Peter
> 3. add changes to 1.5/scons so that scons can automatically detect
> 1.4/1.5 and compile appropriately. That is to say, people who want
> scons for 1.4.x can copy development/scons from trunk and compile.
>
> I prefer method 3, giving the fast evolving nature of the current
> scons system. Any
Edwin Leuven wrote:
Peter Kümmel wrote:
It depends on the scrolling before resizing.
things are messed up here also if i load a document and then maximize
the window. no scrolling needed...
Indeed. Now I see it too as well in the "younes" branch. But I am 100%
sure those two bugs weren't t
Edwin Leuven wrote:
> Peter Kümmel wrote:
>> It depends on the scrolling before resizing.
>
> things are messed up here also if i load a document and then maximize
> the window. no scrolling needed...
>
>
I've the impression it depends on the stuff which has been painted
before the resize occur
Now I see the next bug:
When you often open and close lyx in the
normal mode the windows moves down on
the screen.
So the stored coordinates are not that
of the upper left corner.
I will have a look an this, and will also
post a 'final patch' :-)
Peter
Peter Kümmel wrote:
It depends on the scrolling before resizing.
things are messed up here also if i load a document and then maximize
the window. no scrolling needed...
Edwin Leuven wrote:
> Peter Kümmel wrote:
> > I also see the bug when compiled with mingw,
>> but under Linux it is gone.
>>
>> Maybe it is a Qt bug.
>>
>> The Qt4/msvc patch doesn't change the Qt code
>> much, most changes are for the Borland compiler
>> and qmake, and they are harmless.
>
> but
Abdelrazak Younes wrote:
>> I also see the bug when compiled with mingw,
>> but under Linux it is gone.
>
> You mean "the bug" or the "Qt error message"? I indeed see occasionally
> the message but I am quite sure the resize bug was not there with mingw.
With mingw I see the bug AND the error me
Peter Kümmel wrote:
> I also see the bug when compiled with mingw,
but under Linux it is gone.
Maybe it is a Qt bug.
The Qt4/msvc patch doesn't change the Qt code
much, most changes are for the Borland compiler
and qmake, and they are harmless.
but it hasn't always been there (mingw)
revert
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Peter Kümmel wrote:
At least I'm now 100% sure this is the right place to look for the bug:
I've tested your shared_ptr solution, and the resize bug is gone, but
I get-as assumed-this from Qt: :)
QPaintDevice: Cannot destroy paint device that is bei
Would be nice to let people have a chance to comment on the final
version before committing.
I was waiting for the final version of the patch as well. ... Lars,
you are facing two impatient developers now, Peter and Bo. :-)
Bo
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
>>
>> At least I'm now 100% sure this is the right place to look for the bug:
>> I've tested your shared_ptr solution, and the resize bug is gone, but
>> I get-as assumed-this from Qt: :)
>>
>> QPaintDevice: Cannot destroy paint device that is being pa
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | Lars Gullik Bjønnes wrote:
| > | > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | > | Lars Gullik Bjønnes wrote:
| > | > | > This is among the things the any patc
Helge Hafting wrote:
> Use the preview-latex feature that we already use to render pretty
> math! Render the word "Test" with latex, and use the
> resulting image as the preview in your form. This way, you
> only need the font to exist in latex, it is ok if it isn't available to X.
Did you read
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | Lars Gullik Bjønnes wrote:
| > | > This is among the things the any patch makes possible. IMNSHO quite
| > | > nice.
| > | > svn diff -r14
Helge Hafting <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Helge Hafting <[EMAIL PROTECTED]> writes:
| >
| > | $ ./autogen.sh
| > | Using automake (GNU automake) 1.9.6
| > | Using autoconf (GNU Autoconf) 2.59d
| > | This autoconf version is not supported by LyX.
| > | LyX only su
Abdelrazak Younes wrote:
One bug though: When I pass CCFLAGS="-O3 -w" to scons, I see that the
options is just appended to the default options (-O2 -Wall), ex:
g++ -o release\common\frontends\qt3\QCommandBuffer.o -c -O3 -w -Wall -O2
This happens also with frontend=qt4 but this is new.
Some o
Andrzej Tomaszewski wrote:
Even stranger is for me the fact, that on my laptop LyX looks like on
the .png above (some Polish letters are displayed and some other not),
but on my desktop none of the diacritical marks looks incorrectly apart
from ó, which appears in Western European charset.
Di
Jean-Marc Lasgouttes wrote:
Joost, does the current 1.4.2svn build on windows have iconv support
built-in? This is pretty important.
Yes, iconv support is built-in.
Joost
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | Lars Gullik Bjønnes wrote:
| > | > This is among the things the any patch makes possible. IMNSHO quite
| > | > nice.
| > | > svn diff -r14086:14087 svn://svn.lyx.org/l
Juergen Spitzmueller wrote:
Charles de Miramon wrote:
Very nice. A preview of fonts would be very useful for new users
This is not so easy, unfortunately. After all, lots of these fonts are only
available to LaTeX, not to qt, for instance.
If you want to do it, here is the way:
U
Hello,
With the attached patch, the qt3 frontend in the "younes" branch has
exactly the same functionality as in "trunk". I have tested it quite a
lot. I expect the xforms and gtk frontends to behave the same as they
share the same encapsulation code (of the old API into the new API) as qt3.
Bo Peng wrote:
Can the following be applied (lyx1.4svn)?
Index: src/support/gzstream.h
===
--- src/support/gzstream.h(revision 14087)
+++ src/support/gzstream.h(working copy)
@@ -32,9 +32,7 @@
// standard C++ with new heade
Lars Gullik Bjønnes wrote:
Helge Hafting <[EMAIL PROTECTED]> writes:
| $ ./autogen.sh
| Using automake (GNU automake) 1.9.6
| Using autoconf (GNU Autoconf) 2.59d
| This autoconf version is not supported by LyX.
| LyX only supports autoconf 2.5[2-9].
|
| $ autoconf --version
| autoconf (GNU A
Jose' Matos wrote:
On Friday 09 June 2006 12:20, Helge Hafting wrote:
I think "no lines" is the better way. No old stuff breaks. There
isn't even an update of the document format.
I don't understand you here. There is nothing related with an update for the
file format.
Exactly
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
>>
>> At least I'm now 100% sure this is the right place to look for the bug:
>> I've tested your shared_ptr solution, and the resize bug is gone, but
>> I get-as assumed-this from Qt: :)
>>
>> QPaintDevice: Cannot destroy paint device that is being pa
Peter Kümmel wrote:
> At least I'm now 100% sure this is the right
> place to look for the bug:
> I've tested your shared_ptr solution, and the
> resize bug is gone, but I get-as assumed-this
> from Qt: :)
> QPaintDevice: Cannot destroy paint device
> that is being painted. Be sure to
> QPainter
Peter Kümmel wrote:
At least I'm now 100% sure this is the right place to look for the bug:
I've tested your shared_ptr solution, and the resize bug is gone, but
I get-as assumed-this from Qt: :)
QPaintDevice: Cannot destroy paint device that is being painted. Be sure to
QPainter::end() paint
Angus Leeming wrote:
Abdelrazak Younes wrote:
Georg Baum wrote:
Abdelrazak Younes wrote:
I think they are at a good place in
frontends/ but I agree that the lyx
namespace is wrong. What about a new
namespace in order to avoid
confusion? Multiple possibilities:
- gui
- gui_interface
- interfac
Abdelrazak Younes wrote:
> Georg Baum wrote:
>> Abdelrazak Younes wrote:
>>> I think they are at a good place in
>>> frontends/ but I agree that the lyx
>>> namespace is wrong. What about a new
>>> namespace in order to avoid
>>> confusion? Multiple possibilities:
>>> - gui
>>> - gui_interface
>>>
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
>> Abdelrazak Younes wrote:
I don't think we could just delete it, it's in use, but I will try.
>>> Indeed. Sorry I did not understand your question. Let's going back to
>>> the beginning, we have:
>>>
>>>verticalScrollBar()->setPageStep(viewp
Peter Kümmel wrote:
Abdelrazak Younes wrote:
I don't think we could just delete it, it's in use, but I will try.
Indeed. Sorry I did not understand your question. Let's going back to
the beginning, we have:
verticalScrollBar()->setPageStep(viewport()->height());
Should do nothing
paint
Abdelrazak Younes wrote:
>>
>> I don't think we could just delete it, it's in use, but I will try.
>
> Indeed. Sorry I did not understand your question. Let's going back to
> the beginning, we have:
>
>verticalScrollBar()->setPageStep(viewport()->height());
>
> Should do nothing
>
>pain
Peter Kümmel wrote:
Georg Baum wrote:
One of the tricks used earlier was to make sure that
was included before the qt headers.
But it is! is included in LyXView.h which is the
second include in QtView.h (after config.h), which is the second include
in QCommandBuffer.C (after config.h).
I
Georg Baum wrote:
Abdelrazak Younes wrote:
I think they are at a good place in frontends/ but I agree that the lyx
namespace is wrong. What about a new namespace in order to avoid
confusion? Multiple possibilities:
- gui
- gui_interface
- interface
- ui
- ui_communication
...
I'd prefer gui,
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Try to inverse the two lines:
paint_device_ = QPixmap(viewport()->width(), viewport()->height());
verticalScrollBar()->setPageStep(viewport()->height());
Does not help.
I guess the "verticalScrollBa
Abdelrazak Younes wrote:
> I think they are at a good place in frontends/ but I agree that the lyx
> namespace is wrong. What about a new namespace in order to avoid
> confusion? Multiple possibilities:
> - gui
> - gui_interface
> - interface
> - ui
> - ui_communication
> ...
I'd prefer gui, but
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
>> Abdelrazak Younes wrote:
>>> Try to inverse the two lines:
>>>
>>> paint_device_ = QPixmap(viewport()->width(), viewport()->height());
>>> verticalScrollBar()->setPageStep(viewport()->height());
>>
>> Does not help.
>>
>>> I guess the "verticalScr
Peter Kümmel wrote:
Abdelrazak Younes wrote:
Try to inverse the two lines:
paint_device_ = QPixmap(viewport()->width(), viewport()->height());
verticalScrollBar()->setPageStep(viewport()->height());
Does not help.
I guess the "verticalScrollBar()->setPageStep()" results in a painting
even
Abdelrazak Younes wrote:
>
> Try to inverse the two lines:
>
> paint_device_ = QPixmap(viewport()->width(), viewport()->height());
> verticalScrollBar()->setPageStep(viewport()->height());
Does not help.
> I guess the "verticalScrollBar()->setPageStep()" results in a painting
> event so paint
Georg Baum wrote:
Abdelrazak Younes wrote:
- It is confusing that src/frontends/Gui.h defines lyx::Gui, and
src/frontends/qt3/Gui.h defines lyx::frontend::Gui.
But I asked multiple time if anyone had any objection (you also said
that it was fine with you ;-)).
At that time I did not see the p
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > This is among the things the any patch makes possible. IMNSHO quite
| > nice.
| > svn diff -r14086:14087 svn://svn.lyx.org/lyx/lyx-devel
|
| Why don't you post the patch?
was in a hurry.
Lars Gullik Bjønnes wrote:
> Peter Kümmel <[EMAIL PROTECTED]> writes:
>
> | Lars Gullik Bjønnes wrote:
> | > [EMAIL PROTECTED] writes:
> | >
> | >
> | > | Author: kuemmel
> | > | Date: Tue Jun 13 10:05:00 2006
> | > | New Revision: 14088
> | > |
> | > | Log:
> | > | Qt3/Qt4:
> | > |- don't
Peter Kümmel <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > [EMAIL PROTECTED] writes:
| >
| >
| > | Author: kuemmel
| > | Date: Tue Jun 13 10:05:00 2006
| > | New Revision: 14088
| > |
| > | Log:
| > | Qt3/Qt4:
| > |- don't save geometry values of the maximized lyx window
| >
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > This is among the things the any patch makes possible. IMNSHO quite
| > nice.
| > svn diff -r14086:14087 svn://svn.lyx.org/lyx/lyx-devel
|
| Why don't you post the patch?
was in a hurry.
(and only changed the branch)
Abdelrazak Younes wrote:
> Georg Baum wrote:
>> Why don't you simply grep for 'emit'? You would find several places where
>> emit is #undefined, and a README that tells you not to do so.
>
> You know, sometimes you miss the most obvious thing to do because you
> look for something else :-(. I was
Peter Kümmel wrote:
Lars Gullik Bjønnes wrote:
[EMAIL PROTECTED] writes:
| Author: kuemmel
| Date: Tue Jun 13 10:05:00 2006
| New Revision: 14088
|
| Log:
| Qt3/Qt4:
|- don't save geometry values of the maximized lyx window
|- save/restore the maximized property of the lyx window
|
Lars Gullik Bjønnes wrote:
> [EMAIL PROTECTED] writes:
>
>
> | Author: kuemmel
> | Date: Tue Jun 13 10:05:00 2006
> | New Revision: 14088
> |
> | Log:
> | Qt3/Qt4:
> |- don't save geometry values of the maximized lyx window
> |- save/restore the maximized property of the lyx window
> |
Peter Kümmel wrote:
I've tried to fix the resize bug,
- open lyx
- resize to a small window
- load a file
- scroll down a bit <- this is important
- maximize teh window,
but I could only find where it happens
and couldn't figure out how to fix it.
In QWorkArea::resizeEvent the asignment of th
Lars Gullik Bjønnes wrote:
This is among the things the any patch makes possible. IMNSHO quite
nice.
svn diff -r14086:14087 svn://svn.lyx.org/lyx/lyx-devel
Why don't you post the patch?
Abdel.
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > - It is confusing that src/frontends/Gui.h defines lyx::Gui, and
| > src/frontends/qt3/Gui.h defines lyx::frontend::Gui.
|
| But I asked multiple time if anyone had any objection (you also said
| that it was fine with
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > - It is confusing that src/frontends/Gui.h defines lyx::Gui, and
| > src/frontends/qt3/Gui.h defines lyx::frontend::Gui.
|
| But I asked multiple time if anyone had any objection (you also said
| that it was fine with you ;-)).
At lest to me it w
Georg Baum wrote:
Am Montag, 12. Juni 2006 18:09 schrieb Abdelrazak Younes:
Lars Gullik Bjønnes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
One of the tricks used earlier was to make sure that
was included before the qt headers.
But it is! is included in LyXView.h which is the
seco
[EMAIL PROTECTED] writes:
| Author: kuemmel
| Date: Tue Jun 13 10:05:00 2006
| New Revision: 14088
|
| Log:
| Qt3/Qt4:
|- don't save geometry values of the maximized lyx window
|- save/restore the maximized property of the lyx window
|
| - fix changed lyx_gui::start interface for xform
[EMAIL PROTECTED] writes:
| Index: frontends/qt3/lyx_gui.C
| ===
| --- frontends/qt3/lyx_gui.C (revision 14083)
| +++ frontends/qt3/lyx_gui.C (working copy)
| @@ -222,12 +222,12 @@
|
|
| void start(string const & batch, vecto
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
>> Andre Poenitz wrote:
>>> On Mon, Jun 12, 2006 at 04:32:46PM +0200, Peter Kümmel wrote:
Peter Kümmel wrote:
> I don't think the event handling counts, because it shows
> the uptime time of lyx, even when nothing is painted.
This mak
Peter Kümmel wrote:
Andre Poenitz wrote:
On Mon, Jun 12, 2006 at 04:32:46PM +0200, Peter Kümmel wrote:
Peter Kümmel wrote:
I don't think the event handling counts, because it shows
the uptime time of lyx, even when nothing is painted.
This makes more sense (I've disabled all std::* calls):
82 matches
Mail list logo
