On Mon, Dec 30, 2002 at 02:08:09PM +0100, Alfredo Braunstein wrote:
> unlock() is declared inside an #ifdef QT_THREAD_SUPPORT on qapplication.h.
And they don't supply a qtconfig.h header. Oh joy.
I'm going to hassle them again - this is obviously unacceptable.
In the meantime, we just ignore th
John Levon wrote:
> On Fri, Dec 27, 2002 at 04:08:44PM +0100, Alfredo Braunstein wrote:
>
>> >This is not a bug
>
> Hrrm.
Indeed.
>
>> and the a.unlock() is a safe and appropriate method to
>
> Is unlock() a no-op on non-thread Qt ?
unlock() is declared inside an #ifdef QT_THREAD_SUPPORT o
On Fri, Dec 27, 2002 at 04:08:44PM +0100, Alfredo Braunstein wrote:
> >This is not a bug
Hrrm.
> and the a.unlock() is a safe and appropriate method to
Is unlock() a no-op on non-thread Qt ?
If not we need an #ifdef
john
--
"I will eat a rubber tire to the music of The Flight of the Bumbleb
John Levon wrote:
> On Sat, Dec 21, 2002 at 01:56:05AM +0100, Alfredo Braunstein wrote:
> I do not want to apply this until you have confirmation from Trolltech
> that this is a bug, a nd the workaround is good.
>
> Send an example app to [EMAIL PROTECTED], they are quite responsive
>
> regards
-BEGIN PGP SIGNED MESSAGE-
On Samstag, 21. Dezember 2002 16:18, Alfredo Braunstein wrote:
> Err... wasn't already defined on the patch? Anyway, we are waiting for Qt's
> solution. Bye, Alfredo
You are right ... I suffer under the consequencies of
manually patching (cut & paste with the mo
Alfredo Braunstein wrote:
> Err... wasn't already defined on the patch? Anyway, we are waiting for
> Qt's solution. Bye, Alfredo
I mean: Trolltech's solution. :)
Kornel Benko wrote:
> -BEGIN PGP SIGNED MESSAGE-
>
> On Samstag, 21. Dezember 2002 15:30, Kornel Benko wrote:
>> yx_gui.C: In function `void lyx_gui::exit()':
>> lyx_gui.C:177: no matching function for call to `QApplication::unlock()'
>
>
> Sorry, I should investigate first.
> Defining
-BEGIN PGP SIGNED MESSAGE-
On Samstag, 21. Dezember 2002 15:30, Kornel Benko wrote:
> yx_gui.C: In function `void lyx_gui::exit()':
> lyx_gui.C:177: no matching function for call to `QApplication::unlock()'
Sorry, I should investigate first.
Defining -DQT_THREAD_SUPPORT would have made
-BEGIN PGP SIGNED MESSAGE-
On Samstag, 21. Dezember 2002 01:56, Alfredo Braunstein wrote:
> John Levon wrote:
> > I've got this ever since upgrading to RH* / Qt 3...
>
> The following patch cures it. I think it's simply a qt bug. It seems that
> QApplication destructor assumes that QApplic
John Levon wrote:
> On Sat, Dec 21, 2002 at 01:56:05AM +0100, Alfredo Braunstein wrote:
>
> Send an example app to [EMAIL PROTECTED], they are quite responsive
I'm sending this example to QT
//#define QT_THREAD_SUPPORT
#include
int main(int argc, char **argv)
{
QApplication a(argc,arg
On Sat, Dec 21, 2002 at 01:56:05AM +0100, Alfredo Braunstein wrote:
> The following patch cures it. I think it's simply a qt bug. It seems that
> QApplication destructor assumes that QApplication::exec() was called
> before.
I do not want to apply this until you have confirmation from Trolltec
John Levon wrote:
> I've got this ever since upgrading to RH* / Qt 3...
The following patch cures it. I think it's simply a qt bug. It seems that
QApplication destructor assumes that QApplication::exec() was called
before.
Don't ask me the rationale.
Bye, alfredo
Index: ChangeLog
==
On Fri, Dec 20, 2002 at 04:14:14PM +0100, Alfredo Braunstein wrote:
> It seems to quit cleanly. However, now I get on exit:
>
> Mutex destroy failure: Device or resource busy
I've got this ever since upgrading to RH* / Qt 3...
I don't know what it means yet ..
regards
john
--
"ALL television
John Levon wrote:
> Here's the fix. Lars, OK ?
It seems to quit cleanly. However, now I get on exit:
Mutex destroy failure: Device or resource busy
What does it mean?
Alfredo
John Levon wrote:
> Here's the fix. Lars, OK ?
Great, thanks. Alfredo
John Levon <[EMAIL PROTECTED]> writes:
| On Fri, Dec 20, 2002 at 01:41:48AM +0100, Lars Gullik Bj?nnes wrote:
|
| > | Here's the fix. Lars, OK ?
| >
| > What about saving of last files and other cleanup that is done upon
| > exit?
|
| lyx_gui::exit() is only called at the end of QuitLyX.
Then
On Fri, Dec 20, 2002 at 01:41:48AM +0100, Lars Gullik Bj?nnes wrote:
> | Here's the fix. Lars, OK ?
>
> What about saving of last files and other cleanup that is done upon
> exit?
lyx_gui::exit() is only called at the end of QuitLyX.
regards
john
p.s. I have a simple fix for the table-scrollin
John Levon <[EMAIL PROTECTED]> writes:
| On Thu, Dec 19, 2002 at 08:36:55PM +0100, Alfredo Braunstein wrote:
|
| > On Qt:
| > Open a document for which autosave is newer, so the popup appears. close the
| > main window from the WM. Crash.
|
| Here's the fix. Lars, OK ?
What about saving of las
On Thu, Dec 19, 2002 at 08:36:55PM +0100, Alfredo Braunstein wrote:
> On Qt:
> Open a document for which autosave is newer, so the popup appears. close the
> main window from the WM. Crash.
Here's the fix. Lars, OK ?
regards
john
Index: lyx_gui.C
==
On Thu, Dec 19, 2002 at 08:36:55PM +0100, Alfredo Braunstein wrote:
> On Qt:
> Open a document for which autosave is newer, so the popup appears. close the
> main window from the WM. Crash.
Confirmed. But I'm not sure what's going on to be honest :
#6 0x0810034d in LyXTextClass::load() const
On Qt:
Open a document for which autosave is newer, so the popup appears. close the
main window from the WM. Crash.
Bye, Alfredo
21 matches
Mail list logo
