Re: [kde] Bad Gwenview
- Date: Sun, 3 Aug 2014 12:34:44 +0000 (UTC)
- From: Duncan <1i5t5.duncan@xxxxxxx>
- Subject: Re: [kde] Bad Gwenview
Felix Miata posted on Sun, 03 Aug 2014 07:41:09 -0400 as excerpted:
> On 2014-08-03 05:40 (GMT-0400) Duncan composed:
>> If you can't get gwenview behaving as you like,
>> try gimv and see if it works better for you.
> The trackballs I own have no middle button, while keeping track of
> meanings of middle according to context is something I've never been
> able to manage, not to mention the difficulty of striking two buttons
Generally, striking one and holding it down, then the other, within a
certain (IIRC configurable) period, then let them up within a reasonably
close approximation to simultaneously, is enough. They don't have to be
clicked /exactly/ at the same time.
I've actually been a bit surprised at how well it works, but it does.
> I have many installations, making the complicated options (multiple
> mapping) much too much trouble to contemplate.
Yes, that wouldn't work for everyone. It's just what works for me. And
on my netbook, I generally want the zoom-to-fit, so that too works just
fine for me.
> Whatever version is whatever version, as most are whatever Cauldron,
> Factory or Rawhide offer. 4.13.80 just happened to be the one I wanted
> to view some images with.
> I've been able to find no decent keyboards made since the early '90s.
> All I have were made before Win keys existed. "Decent" is defined to
> mean function keys where they belong, where one hand's fingers can hit
> any combination of Fn/Shift/Alt/Ctrl easily.
"Decent" means different things to different people. Here, it's not
"decent" unless it's an ergonomically split "wave" keyboard. But FWIW I
did try an MS branded one (wireless) at some point and it was
/horrible/. I've stuck with Logitech since.
Anyway, there's other mappings possible. I use a bit different mappings
on my netbook, for instance, as some of its keys are already dual-key
mapping (Fn-Home, for example).
But definitely a few "extra" keys, including an extra modifier generally
not used by built-in mappings for individual apps, which is what the win/
super/meta key ends up being, certainly help. That allows that modifier
key to be mapped to global "window" functions as there's little danger of
a global shortcut conflicting with something app-specific, that way.
> Looks like it has worked in v4 previously:
> While gimv might be better than "Gwenview", KDE3's Gwenview clearly is,
> because when 100% is selected, that's the way it stays until another
> selection is made. Apparently I'm not the only one who thinks selecting
> 100% ought to be sticky:
I agree, which is one reason I had to switch to gimv for awhile. It just
so happens that in my case, the window can be made large enough that in
most cases 100% is smaller than the window, such that gwenview's checkbox
for that option works and I can actually have 100% by default. Were it
to work the other way and the checkbox applied only to larger-than-window
images, I'd have to find another alternative, just as I did when gwenview
lost sticky 100% on small images until they restored it with that checkbox
And as I said, I already apply zoom-step patches to gwenview. If that
checkbox option disappeared again and zoom-to-fit became the hard-coded
default for small images, I might end up trying to diff and patch that as
well. (While I don't claim to be a coder, it's nice to have at least
/limited/ ability to read code and to apply patches. It just struck me
how much I simply assume that I have sources available and /can/ do that,
these days. Quite a difference from back before the turn of the century
when I used proprietary servantware, for sure!)
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
More info: http://www.kde.org/faq.html.