Quote:
Originally Posted by st_albert
I concur that the single-click setting is the problem. Too bad; I like single-click for some things (I'm lazy like that), but I agree it's a PITA for other things. Maybe I'll keep it set to double-click for a while...  |
Oh, I hear you on the lazy thing.
There's times when single-click-to-launch is handy as heck. But when you're purposefully blurring the line between "highlight me" and "launch me," there's bound to be some problem areas.
Quote:
Originally Posted by st_albert
I never did have the crash on dragging files around in the book browser, so I don't know if it helps with that problem. Does it?
|
I can't say for sure. I never got it to crash dragging files around, either. But I certainly wouldn't rule it out. Sid isn't called DebianUnstable for no reason.
With Qt essentially being tricked into thinking that items in QTreeView are being double-clicked, that means there's a heck of a lot more signals being emitted when attempting to drag around files in Sigil's Book Browser (on KDE with single-click-to-open enabled), than on systems where the exact same action doesn't result in any new BV/CV tabs being opened (nor does it cause any already open tabs to take focus).