J.D. Purcell
J.D. Purcell
Potential SlimDX replacement, targets .NET Standard 2.0: https://github.com/amerkoleci/Vortice.Windows Supports Direct3D9, DirectInput, XInput, and XAudio2 among others, but not DirectSound. A few years ago I tried out the XAudio2 part and...
I believe that's because Vortice uses XAudio2 2.9/2.8 whereas SlimDX uses XAudio2 2.7. Microsoft stated in the changes for XAudio2 2.8: > Device enumeration functionality has been removed from XAudio2;...
FWIW I was playing around with this in [my commit here](https://github.com/jdpurcell/qView/commit/4a88b7353d60800c1cd5255956bc607e9bb10ab0). I actually did a custom implementation instead of just `setRange` on the scrollbars, to allow a partial rubber band...
Sure, [demo builds here](https://github.com/jdpurcell/qView/releases/tag/demo-constrainscrolling). It's just a proof of concept. It's missing a setting to turn it off, and it only constrains when dragging (i.e. it's unconstrained in certain cases...
[This commit](https://github.com/jdpurcell/qView/commit/82198f00d557fe7229b0be57d91bb69247ac3c39) implements it for mouse/touchpad scrolling as well. [Demo builds here](https://github.com/jdpurcell/qView/releases/tag/demo-constrainscrolling2). [EDIT: I think mouse/touchpad rubber banding in this build only works on Mac?] As much as I'm normally...
Duplicate of #651 which was already fixed in the master branch but not released yet. There are "nightly" builds from GitHub Actions, although the last one from the master branch...
@jurplel I was trying to decipher your title 😂, I don't know if this is exactly what you meant, but it seemed like a cool idea nonetheless, so I implemented...
@fredcallaway qView already supported browsing through images in a folder - once you are viewing an image, press the left or right arrow on your keyboard to navigate to neighboring...
@fredcallaway Yes! On the main qView GitHub page you can click the green check mark next to the latest commit and then click any of the Details links.  Then...
@BloodRaven0 Do you know if the "Image scaling" setting was unchecked when this happened? If so, I suspect this is related to the "bonus fix" I included in #515.