[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Texmacs-dev] TeXmacsQT minibuffer prompt implemented in the status

From: Joris van der Hoeven
Subject: Re: [Texmacs-dev] TeXmacsQT minibuffer prompt implemented in the status bar
Date: Tue, 2 Nov 2010 18:39:10 +0100
User-agent: Mutt/1.5.18 (2008-05-17)

Dear Miguel,

On Mon, Nov 01, 2010 at 04:11:49PM +0100, Miguel de Benito Delgado wrote:
>   my name is Miguel, I'm in the process of becoming a mathematician and I
> have been using TeXmacs for the last four years for all my tex-like work. Of
> course I love it and I'm very pleased to have now some spare time to work on
> it. Yesterday I submitted to Savannah's patch tool a small patch for a
> drag&drop feature in the "Open File" dialog (QT), which as a MacOS user I
> was definitely missing. But since I've noticed very low activity in
> Savannah, I'm now posting my second patch here.

For sure, your contributions are welcome. We are not reactive all the time,
but try to do our best to incorporate patches.

>  However simple this might be, I do have two unsolved issues:
> 1. I've decided to simply insert the widgets at the leftmost position of the
> status bar, leaving the rest to adjust itself. This is not pretty, because
> any previous status messages are still displayed, but I couldn't think of
> any other solution, short of replacing the QStatusBar, then restore the
> original one. But since QMainWindow takes ownership of it and deletes any
> objects when it deems necessary, I ended up with some nasty EXC_BAD_ACCESS.
> Any ideas?

Please look at the X11 implementation: it uses the replacement trick.

> 2. Since to make it "modal" I'm executing a local QEventLoop, resizeEvents
> are not being sent wherever they are meant to, and the canvas does not
> update if one resizes the window while the interactive prompt is on. I guess
> I'd have to update the canvas, or whatever, from within
> QWidget::resizeEvent(). What should I do in there?

In the X11 implementation, the widget is not modal.
I agree that it would be better to make it modal,
but I doubt that reimplementing an event loop would be a good solution.
Probably Qt allows for passing all incoming events to a subwidget.
Otherwise, such as system might be implemented.


Best wishes, --Joris

reply via email to

[Prev in Thread] Current Thread [Next in Thread]