Magic Mouse issue still not fixed in 3.1.3
AnsweredJust updated to 3.1.3 and the Magic Mouse issue still hasn't been fixed, this has been reported by many people since Luminar 3 came out, we were promised the next update would fix this, this was 2 or 3 updates ago, how come this hasn't been addressed? Try editing using a Magic Mouse and barely touch it and you scroll to another photo.
Also Nikon Lens info still isn't showing up for the D850, D500, D300....
-
Bad News - Magic Mouse issue not resolved
Good News - We have a new Splash Screen
See last comment in this post - Kirk Osborn Please Respond
https://community.skylum.com/hc/en-us/community/posts/360034174132-Luminar-3-with-Magic-Mouse
-
As the originator of this issue, I have replied to several threads regarding this issue and Skylum responses are whatever...
I've been told
- Use a different mouse
- We cannot duplicate the problem
- Can you replicate so we can investigate
- Its fixed but it has not been included in the code base
-
Although I've only had a very few issues with Luminar the Magic Mouse bug is one of the most annoying and I fail to understand why Skylum are finding it so difficult to fix? I use the Apple Magic Mouse all day, each and every day with a multitude of different software apps and Luminar is the only app that has this issue. I don't want to use another mouse thank you.
-
You would think this would be a very simple thing to fix.
I use Capture One, and the mouse movement if your cursor is on the image, zooms the image. They have an option in the Preferences with a simple check box to turn this feature off.
Why can't Luminar do the same thing and turn off moving to another image. The program as it is on Mac with a mouse is not really usable. It's just and exercise in frustration until you close it down.
-
Hello Gene Flanigan,
Thank you very much for your feedback. Indeed, this would be a major improvement and we are adding it in our next updates.
Could you please kindly contact us via https://skylum.com/support, so we can send you experimental build, where this issue should be resolved? Look forward to hearing from you.
Please sign in to leave a comment.
Comments
11 comments