[QScintilla] Re: QScintilla Digest, Vol 19, Issue 5

[Patrick Mabie]

qscintilla-request at riverbankcomputing.com wrote:
> Send QScintilla mailing list submissions to
> 	qscintilla at riverbankcomputing.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://www.riverbankcomputing.com/mailman/listinfo/qscintilla
> or, via email, send a message with subject or body 'help' to
> 	qscintilla-request at riverbankcomputing.com
>
> You can reach the person managing the list at
> 	qscintilla-owner at riverbankcomputing.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of QScintilla digest..."
>
>
> Today's Topics:
>
>    1. Re: QScintilla Digest, Vol 19, Issue 4 (Patrick Mabie)
>    2. Re: Re: QScintilla Digest, Vol 19, Issue 4 (Phil Thompson)
>    3. Next Release of QScintilla (Phil Thompson)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 10 Feb 2008 11:51:10 -0500
> From: Patrick Mabie <pmabie at gmail.com>
> Subject: [QScintilla] Re: QScintilla Digest, Vol 19, Issue 4
> To: qscintilla at riverbankcomputing.com
> Message-ID: <47AF2B7E.7050101 at gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>     Hi Phil and all!
>   
>> Using: Visual Studio 2008,QScintilla-gpl-2-snapshot-20080120,Qt 4.3.3
>>
>> //Connection to this Signal
>> void QsciScintilla::cursorPositionChanged (int line, int pos) [signal]
>> connect(CurrentEditor(),SIGNAL(cursorPositionChanged 
>> (int,in)),this,SLOT(UpdateRowCol(int,int)))
>>
>> void MainWindow::processEvents()
>> {
>>     qApp->processEvents(QEventLoop::AllEvents);
>> }
>>
>> void MainWindow::UpdateRowCol(int line,int pos)
>> {
>>     QString RowCol;
>>     RowCol = QString(tr("Row%1 Col %2).arg(line).arg(pos));
>>     statusBar()->showMessage(tr("Row      Col      "));
>>     statusBar()->showMessage(RowCol);
>>     processEvents();
>> }
>>
>> I couldn't belive the lag that was involved with this , if you didn't 
>> let off the key it didn't update , I am not saying this is a bug or a 
>> problem , I just was wonder if you or anyone how come across this?
>>
>> Thanks for your Time.
>>
>> Patrick.
>>     
>
> Frist off thanks for replying and sorry for not including that routine , 
> it's a QT one, As for processEvent(), I only added that when I thought 
> there was a event problem.
>
> /*!
>     Hides the normal status indications and displays the given \a
>     message for the specified \a timeout milli-seconds (if non-zero),
>     or until clearMessage() or another showMessage() is called,
>     whichever occurs first.
>
>     \sa messageChanged(), currentMessage(), clearMessage()
> */
> void QStatusBar::showMessage(const QString &message, int timeout)
> {
>     Q_D(QStatusBar);
>     if (d->tempItem == message)
>         return;
>
>     d->tempItem = message;
>
>     if (timeout > 0) {
>         if (!d->timer) {
>             d->timer = new QTimer(this);
>             connect(d->timer, SIGNAL(timeout()), this, 
> SLOT(clearMessage()));
>         }
>         d->timer->start(timeout);
>     } else if (d->timer) {
>         delete d->timer;
>         d->timer = 0;
>     }
>
>     hideOrShow();
> }
>
>
> Hope this helps, sorry to upset you.
>
> Have a good day!
>
>
> ------------------------------
>
> Message: 2
> Date: Sun, 10 Feb 2008 21:48:33 +0000
> From: Phil Thompson <phil at riverbankcomputing.com>
> Subject: Re: [QScintilla] Re: QScintilla Digest, Vol 19, Issue 4
> To: qscintilla at riverbankcomputing.com
> Message-ID: <200802102148.33610.phil at riverbankcomputing.com>
> Content-Type: text/plain;  charset="iso-8859-1"
>
> On Sunday 10 February 2008, Patrick Mabie wrote:
>   
>>     Hi Phil and all!
>>
>>     
>>> Using: Visual Studio 2008,QScintilla-gpl-2-snapshot-20080120,Qt 4.3.3
>>>
>>> //Connection to this Signal
>>> void QsciScintilla::cursorPositionChanged (int line, int pos) [signal]
>>> connect(CurrentEditor(),SIGNAL(cursorPositionChanged
>>> (int,in)),this,SLOT(UpdateRowCol(int,int)))
>>>
>>> void MainWindow::processEvents()
>>> {
>>>     qApp->processEvents(QEventLoop::AllEvents);
>>> }
>>>
>>> void MainWindow::UpdateRowCol(int line,int pos)
>>> {
>>>     QString RowCol;
>>>     RowCol = QString(tr("Row%1 Col %2).arg(line).arg(pos));
>>>     statusBar()->showMessage(tr("Row      Col      "));
>>>     statusBar()->showMessage(RowCol);
>>>     processEvents();
>>> }
>>>
>>> I couldn't belive the lag that was involved with this , if you didn't
>>> let off the key it didn't update , I am not saying this is a bug or a
>>> problem , I just was wonder if you or anyone how come across this?
>>>
>>> Thanks for your Time.
>>>
>>> Patrick.
>>>       
>> Frist off thanks for replying and sorry for not including that routine ,
>> it's a QT one, As for processEvent(), I only added that when I thought
>> there was a event problem.
>>
>> /*!
>>     Hides the normal status indications and displays the given \a
>>     message for the specified \a timeout milli-seconds (if non-zero),
>>     or until clearMessage() or another showMessage() is called,
>>     whichever occurs first.
>>
>>     \sa messageChanged(), currentMessage(), clearMessage()
>> */
>> void QStatusBar::showMessage(const QString &message, int timeout)
>> {
>>     Q_D(QStatusBar);
>>     if (d->tempItem == message)
>>         return;
>>
>>     d->tempItem = message;
>>
>>     if (timeout > 0) {
>>         if (!d->timer) {
>>             d->timer = new QTimer(this);
>>             connect(d->timer, SIGNAL(timeout()), this,
>> SLOT(clearMessage()));
>>         }
>>         d->timer->start(timeout);
>>     } else if (d->timer) {
>>         delete d->timer;
>>         d->timer = 0;
>>     }
>>
>>     hideOrShow();
>> }
>>
>>
>> Hope this helps, sorry to upset you.
>>
>> Have a good day!
>>     
>
> You misunderstood. You need to post a *complete* (and short) example that 
> demonstrates the problem - otherwise nobody can reproduce it.
>
> Phil
>
>
> ------------------------------
>
> Message: 3
> Date: Sun, 10 Feb 2008 21:54:45 +0000
> From: Phil Thompson <phil at riverbankcomputing.com>
> Subject: [QScintilla] Next Release of QScintilla
> To: qscintilla at riverbankcomputing.com
> Message-ID: <200802102154.45026.phil at riverbankcomputing.com>
> Content-Type: text/plain;  charset="us-ascii"
>
> The current QScintilla snapshot will be released as v2.2 in the next few days. 
> Let me know if there is anything you think still needs fixing.
>
> Phil
>
>
> ------------------------------
>
> _______________________________________________
> QScintilla mailing list
> QScintilla at riverbankcomputing.com
> http://www.riverbankcomputing.com/mailman/listinfo/qscintilla
>
>
> End of QScintilla Digest, Vol 19, Issue 5
> *****************************************
>
>   
Ok
thanks for your time!

Have a good day!