Implementing shift delete in dolphin, some help would be nice.

[Mark]

On Mon, Sep 13, 2010 at 11:13 PM, Lubos Lunak <l.lunak at suse.cz> wrote:

> On Monday 13 of September 2010, Mark wrote:
> > On Mon, Sep 13, 2010 at 10:00 PM, Mark <markg85 at gmail.com> wrote:
> > > --- src/dolphincontextmenu.cpp (revision 1174907)
> > > +++ src/dolphincontextmenu.cpp (working copy)
> > > @@ -69,6 +69,9 @@
> > >      const DolphinView* view =
> > > m_mainWindow->activeViewContainer()->view(); m_selectedUrls =
> > > view->selectedUrls();
> > >      m_selectedItems = view->selectedItems();
> > > +    m_keyInfo = new KModifierKeyInfo();
>
>  And who deletes it?
>
Not in the above patch, but the destructor now does that:
DolphinContextMenu::~DolphinContextMenu()


>
> > Interesting, just found out that just having an instance
> > of KModifierKeyInfo (in the earlier diff: "m_keyInfo = new
> > KModifierKeyInfo();") blocks the GUI when shift is pressed and the right
> > mouse button.
>
>
> http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB
> and see for yourself where it blocks.
>
Yea, i've got that suggestion on irc as well, but that's not really possible
to do with gdb (or i don't know how).
The dolphin interface blocks and the mouse gets extremely slow when i select
an item, press shift (hold it) and press right mouse botton, but as soon as
i lose focus of dolphin (which happens when i try to go to another app) it's
like the shift key is released (even while i'm still holding it) and dolphin
continues normally. This however makes it close to impossible to press CTRL
+ C in gdb to get the trace.

If you have any ideas, please do suggest them!

>
> --
>  Lubos Lunak
>  openSUSE Boosters team, KDE developer
>  l.lunak at suse.cz , l.lunak at kde.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20100914/9d24502e/attachment.htm>