Skip to content
This repository has been archived by the owner on Mar 30, 2021. It is now read-only.

Conflicts with Adobe Fireworks CS6 while application is running. #40

Closed
ghost opened this issue Feb 26, 2014 · 8 comments
Closed

Conflicts with Adobe Fireworks CS6 while application is running. #40

ghost opened this issue Feb 26, 2014 · 8 comments
Labels
Milestone

Comments

@ghost
Copy link

ghost commented Feb 26, 2014

Selecting and clicking objects in Adobe Fireworks CS6 doesn't work normally while this application is running (even minimized.) Selecting will work fine again once the Music application is terminated. This application should have no effect on other running applications.

@kbhomes
Copy link
Member

kbhomes commented Feb 27, 2014

Interesting, on the outset I have no clue what could cause this. Were you running the 1.0.2 release (from the ZIP) or from the latest commit at the time you wrote this? Does the problem happen with other CS6 products?

@kbhomes kbhomes added the bug label Feb 27, 2014
@ghost
Copy link
Author

ghost commented Feb 27, 2014

It is strange, but I would guess it has something to do with media keys / hot keys detection. To be more specific about the problem: when I simply click on an object it will not register, however, if I drag the mouse a little bit while clicking down, it will select the object when I release the mouse. I didn't test all other CS apps, but i was also running Illustrator CC at that seemed to be working fine. I had installed the version from the ZIP file.

@kbhomes
Copy link
Member

kbhomes commented Mar 9, 2014

I've installed a trial version of Adobe Fireworks CS6 and can confirm that this bug is affecting me too. I'm currently investigating what could be the root cause.

@kbhomes kbhomes closed this as completed in 440cd20 Mar 9, 2014
@kbhomes
Copy link
Member

kbhomes commented Mar 9, 2014

@mtgpplisez: Good news! This is now fixed, for whatever reason, defining an event tap for the media keys specifically caused the problem, so instead I define an event tap for all events and filter them out to include only the media key events. Everything seems to be working fine in Fireworks, so any other application with a similar problem should now be fixed. Still, I don't see why this bug existed, but at the very least, it's fixed.

@kbhomes kbhomes added this to the v1.1.0 milestone Mar 9, 2014
@kbhomes
Copy link
Member

kbhomes commented Mar 9, 2014

For reference, here is a thread from almost 4 years ago on Adobe's forums where users reported the problem and identified Spotify and two other applications that caused the same issue, all stemming from the event tap for media keys.

@ghost
Copy link
Author

ghost commented Mar 10, 2014

Fixed! Thank you!!

@kbhomes kbhomes reopened this Apr 6, 2014
@kbhomes
Copy link
Member

kbhomes commented Apr 6, 2014

I pushed a commit that un-fixes this issue, unfortunately. I essentially had to revert the fix for this issue in order to fix #117, which was somehow also affected by the event tap. In this case, I figured that the Quick Look use case is more frequent than Fireworks usage and the problems that occur there, so my plan instead is to create an Advanced preferences item that has in it a preference to switch between these two modes: the one where Quick Look works, and the one where Fireworks works.

@kbhomes kbhomes modified the milestones: v1.1.3, v1.1.0 Apr 6, 2014
@kbhomes kbhomes closed this as completed in be27ba5 Apr 7, 2014
@kbhomes
Copy link
Member

kbhomes commented Apr 7, 2014

@mtgpplisez: I've now merged a change that adds a new preference "Use alternative method to listen for media keys", which is off by default. When it is on, it changes the behavior of the event tap in a way that Fireworks will work again. However, Quick Look (and possibly other features) will be broken.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant