ctrl + mouswheel zoom skips 100%

[draders]

When using ctrl+mousewheel to zoom, it seems to skip over 100% and go for example from 110% to 98%.

[david.atwell]

Known bug, and mostly unfixable since everyone's scroll wheels send different information to the program. Mine, for instance, does not skip 100%. A few other people's hit 90% before skipping to 102%. Sorry.

[Sozo]

Curious, mine hits 108 and 96. Darn cheap mouse. Of course, I rarely need to zoom, except when I'm trying to make pixel by pixel details. Good to know, David!

[Benji2]

Try changing how much one tick on your mouse wheel moves in windows settings?

[LFC4EVER]

if you want to view the canvas at 100%, then you can just hit "Ctrl + Shift + A".

[draders]

Problem with that ctrl + shift + a hotkey is it brings up Trillian, and there is no setting to remove the hotkey in it's preferences. I'm confused as to why the tick count would make it impossible to fix this bug. Why couldn't you just check the new value against the old and if its less then 100% from above 100% set it to 100%. As someone who programs for a living, this shows either a design flaw or lazyness.

[david.atwell]

Hey, I have an idea. How about if you don't tell Rick what's lazy or bad design until you program your own award-winning free graphics software, eh? If you're so 1337, fix Trillian so it won't pop up when you use this shortcut.

The point is, you don't know how easy or hard it would be. So don't make it sound like you do.

If your next post in this thread isn't an apology, it will be locked.

[draders]

I do apologize, the developers are obviously not lazy. It's more likely just not a priority. I havn't gone over the source enough to comment on the design either.

However, and I ask this on a "I would really like this fixed" basis, wouldn't adding:

if (this.ScaleFactor > ScaleFactor.OneToOne && newSF < ScaleFactor.OneToOne)
{
   this.ScaleFactor = ScaleFactor.OneToOne;
   break;
}

to the "public virtual void ZoomIn(double factor)" function of the DocumentViewer class's do loop after the newSF declaration fix this problem?

[Rick Brewster]

Yes please use tact when discussing these things. Key words to avoid are "easy" and "lazy".

I've got a bug filed on this already but I just haven't looked at it yet. I've sent myself a new reminder and will look at doing this for v3.5. I'm in the middle of a whole mess of important text and font related stuff though, so don't necessarily expect it in the next alpha update.

For now just press Ctrl+Shift+A or Ctrl+Alt+0. Both are shortcuts for setting the zoom level to 100% (the second does work even though it isn't listed in the View menu -- just use whichever one you're most comfortable with).