so ok, i'm not going to commit this. if you want me i can produce the
patch,
which will remove the caching,
>>>
>>> Yes. Please do that.
>> No please, I think I have the solution.
>
> Please svn update and try again.
yesss! good work Abdel :)
pavel
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
Pavel Sanda wrote:
Thinks tend to change, and I am pretty sure this was once called
once per keystroke.
If the 'paste' button is visible, it is called 'once' per keystroke!
Do you have the main toolbars switched off Pavel?
yes i have all stan
Abdelrazak Younes wrote:
Pavel Sanda wrote:
Thinks tend to change, and I am pretty sure this was once called
once per keystroke.
If the 'paste' button is visible, it is called 'once' per keystroke!
Do you have the main toolbars switched off Pavel?
yes i have all standard buttons on.
In any c
Pavel Sanda wrote:
Thinks tend to change, and I am pretty sure this was once called
once per keystroke.
If the 'paste' button is visible, it is called 'once' per keystroke! Do you
have the main toolbars switched off Pavel?
yes i have all standard buttons on.
In any case this patch is wrong be
>> Thinks tend to change, and I am pretty sure this was once called
>> once per keystroke.
>
> If the 'paste' button is visible, it is called 'once' per keystroke! Do you
> have the main toolbars switched off Pavel?
yes i have all standard buttons on.
> In any case this patch is wrong because it
Jean-Marc Lasgouttes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
If the 'paste' button is visible, it is called 'once' per keystroke!
Do you have the main toolbars switched off Pavel?
It is 'paste selection', I think. Is it in the toolbar?
Ah... right! The original problem was with
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> If the 'paste' button is visible, it is called 'once' per keystroke!
> Do you have the main toolbars switched off Pavel?
It is 'paste selection', I think. Is it in the toolbar?
> In any case this patch is wrong because it is turning around the real
Andre Poenitz wrote:
On Wed, Dec 12, 2007 at 12:04:14AM +0100, Pavel Sanda wrote:
reasons why
we dont ask directly
qApp->clipboard()->text(QClipboard::Selection).isEmpty() ?
The only reason was speed issue.
what about to call this whenever middle button is clicked ?
Might work. Otoh we get t
On Wed, Dec 12, 2007 at 12:04:14AM +0100, Pavel Sanda wrote:
> > > >> reasons why
> > > >> we dont ask directly
> > > >> qApp->clipboard()->text(QClipboard::Selection).isEmpty() ?
> > > >
> > > > The only reason was speed issue.
> > >
> > > what about to call this whenever middle button is clicke
> > >> reasons why
> > >> we dont ask directly
> > >> qApp->clipboard()->text(QClipboard::Selection).isEmpty() ?
> > >
> > > The only reason was speed issue.
> >
> > what about to call this whenever middle button is clicked ?
>
> Might work. Otoh we get the signal delivered anyway...
i really d
10 matches
Mail list logo