global listening doesn't seem to work on Ventura

[Pomax]

I'm running Midi Keys with a global enable/disable hotkey, but when I have global input enabled, any typing I do still gets sent into whatever application I'm running instead of being intercepted and turned into MIDI events.

[Pomax]

Okay so that's not true... the listener for the global hotkey does work, but whether it's on or off, typing anything without midikeys in focus does not get those keys routed through midikeys.

[xoxo369]

they dont care about us... let me know if you find a better alternative..

[Pomax]

Please remember that unpaid open source developers are humans too: if they no longer have time to look at this repo, then they don't have time to look at this repo. Unless you paid for the product, which you haven't, blaming them for not responding to an issue is grossly misunderstanding the relationship between you as a user and them as maintainer.

If they ever find the time to look at this: great. If not: this issue will stay here for others to find (and maybe even motivate them to fix it themselves, and file a PR, or fork the project).

[xoxo369]

Please remember that unpaid open source developers are humans too: if they no longer have time to look at this repo, then they don't have time to look at this repo. Unless you paid for the product, which you haven't, blaming them for not responding to an issue is grossly misunderstanding the relationship between you as a user and them as maintainer.

If they ever find the time to look at this: great. If not: this issue will stay here for others to find (and maybe even motive them to fix it themselves, and file a PR, or fork the project).

yeah I offered them money they don't care, we need to find another way to get it updated

[Pomax]

So pay someone else to fork it and update it. It's open source.

[xoxo369]

So pay someone else to fork it and update it. It's open source.

how do I go about that?

[xoxo369]

still upset about this to be honest

[elektronen]

Hey folks. I understand there's a small group of people here that love this app, and have to come to rely on it. I am one of those people as well. The developer has every right to move on to other interests. Nobody does independent coding for free to be shackled to their creation for the rest of their lives.

What I'd like to do is encourage everyone to be constructive, not endlessly complain and berate the developer. Trying to guilt the dev into continuing work on a past passion project is a losing proposition.

Working with git is fairly easy. Forking the code is also easy. Figuring out how Apple changed the Accessibility UI portion of macOS between Big Sur and Ventura seems to be the thing to focus on here. AFAICS, MidiKeys always leveraged the Accessibility UI in order to provide the Global Hot Keys functionality.

[xoxo369]

Do you think apple blocked that kind of scripts because it could be used as a keylogger? Where can i find a developer to pay to fork it and fix it? Also listen to my music guys! @sleepindesigner on SoundCloud

…

On Mon, Jan 6, 2025 at 6:07 PM Mike Carlson ***@***.***> wrote: Hey folks. I understand there's a small group of people here that love this app, and have to come to rely on it. I am one of those people as well. The developer has every right to move on to other interests. Nobody does independent coding for free to be shackled to their creation for the rest of their lives. What I'd like to do is encourage everyone to be constructive, not endlessly complain and berate the developer. Trying to guilt the dev into continuing work on a past passion project is a losing proposition. Working with git is fairly easy. Forking the code is also easy. Figuring out how Apple changed the Accessibility UI portion of macOS between Big Sur and Ventura seems to be the thing to focus on here. AFAICS, MidiKeys always leveraged the Accessibility UI in order to provide the Global Hot Keys functionality. — Reply to this email directly, view it on GitHub <#37 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVGETRWMDRYNZT22R3WQAU32JMLD3AVCNFSM6AAAAABHH7WPIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZUGE2DKMBYGM> . You are receiving this because you commented.Message ID: ***@***.***>

[elektronen]

No, security in an operating system is rarely that targeted. The most common cause of issues for older applications is going to be something Apple changed to broadly improve security or, more likely, a portion of the Accessibility UI that was rewritten to support input device portability. The ability to move keyboard and mouse between computers and mobile devices was introduced right after Big Sur. There's probably a change log available for the version of XCode released with macOS 12 or 13, and that would be a good place to start.

…

On Mon, Jan 6, 2025, 7:00 PM xoxo369 ***@***.***> wrote: Do you think apple blocked that kind of scripts because it could be used as a keylogger? Where can i find a developer to pay to fork it and fix it? Also listen to my music guys! @sleepindesigner on SoundCloud On Mon, Jan 6, 2025 at 6:07 PM Mike Carlson ***@***.***> wrote: > Hey folks. I understand there's a small group of people here that love > this app, and have to come to rely on it. I am one of those people as well. > The developer has every right to move on to other interests. Nobody does > independent coding for free to be shackled to their creation for the rest > of their lives. > > What I'd like to do is encourage everyone to be constructive, not > endlessly complain and berate the developer. Trying to guilt the dev into > continuing work on a past passion project is a losing proposition. > > Working with git is fairly easy. Forking the code is also easy. Figuring > out how Apple changed the Accessibility UI portion of macOS between Big Sur > and Ventura seems to be the thing to focus on here. AFAICS, MidiKeys always > leveraged the Accessibility UI in order to provide the Global Hot Keys > functionality. > > — > Reply to this email directly, view it on GitHub > <#37 (comment)>, or > unsubscribe > < https://github.com/notifications/unsubscribe-auth/AVGETRWMDRYNZT22R3WQAU32JMLD3AVCNFSM6AAAAABHH7WPIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZUGE2DKMBYGM> > . > You are receiving this because you commented.Message ID: > ***@***.***> > — Reply to this email directly, view it on GitHub <#37 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AI2IFQPE7CFLTYLF5XGX6CT2JMYKRAVCNFSM6AAAAABHH7WPIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZUGI2DMNZQGQ> . You are receiving this because you commented.Message ID: ***@***.***>

[xoxo369]

So with that being said how should I go about finding the right developers to fork this and update it? I am genuinely willing to pay up to 100$ for it to work again how it used to.. On Mon, Jan 6, 2025 at 8:29 PM Mike Carlson ***@***.***> wrote:

…

No, security in an operating system is rarely that targeted. The most common cause of issues for older applications is going to be something Apple changed to broadly improve security or, more likely, a portion of the Accessibility UI that was rewritten to support input device portability. The ability to move keyboard and mouse between computers and mobile devices was introduced right after Big Sur. There's probably a change log available for the version of XCode released with macOS 12 or 13, and that would be a good place to start. On Mon, Jan 6, 2025, 7:00 PM xoxo369 ***@***.***> wrote: > Do you think apple blocked that kind of scripts because it could be used > as > a keylogger? Where can i find a developer to pay to fork it and fix it? > Also listen to my music guys! @sleepindesigner on SoundCloud > > On Mon, Jan 6, 2025 at 6:07 PM Mike Carlson ***@***.***> > wrote: > > > Hey folks. I understand there's a small group of people here that love > > this app, and have to come to rely on it. I am one of those people as > well. > > The developer has every right to move on to other interests. Nobody does > > independent coding for free to be shackled to their creation for the > rest > > of their lives. > > > > What I'd like to do is encourage everyone to be constructive, not > > endlessly complain and berate the developer. Trying to guilt the dev > into > > continuing work on a past passion project is a losing proposition. > > > > Working with git is fairly easy. Forking the code is also easy. Figuring > > out how Apple changed the Accessibility UI portion of macOS between Big > Sur > > and Ventura seems to be the thing to focus on here. AFAICS, MidiKeys > always > > leveraged the Accessibility UI in order to provide the Global Hot Keys > > functionality. > > > > — > > Reply to this email directly, view it on GitHub > > <#37 (comment)>, > or > > unsubscribe > > < > https://github.com/notifications/unsubscribe-auth/AVGETRWMDRYNZT22R3WQAU32JMLD3AVCNFSM6AAAAABHH7WPIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZUGE2DKMBYGM> > > > . > > You are receiving this because you commented.Message ID: > > ***@***.***> > > > > — > Reply to this email directly, view it on GitHub > <#37 (comment)>, or > unsubscribe > < https://github.com/notifications/unsubscribe-auth/AI2IFQPE7CFLTYLF5XGX6CT2JMYKRAVCNFSM6AAAAABHH7WPIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZUGI2DMNZQGQ> > . > You are receiving this because you commented.Message ID: > ***@***.***> > — Reply to this email directly, view it on GitHub <#37 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVGETRXF4UZS47XOQS63CDD2JM3ZNAVCNFSM6AAAAABHH7WPIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZUGI3TGNJUHE> . You are receiving this because you commented.Message ID: ***@***.***>

[elektronen]

What you're describing is called a code bounty. While $100 is no small amount, it's one hour of time for an experienced developer, and two hours of time for an honest carpenter. You can do some research and see what you find.

…

On Mon, Jan 6, 2025, 9:24 PM xoxo369 ***@***.***> wrote: So with that being said how should I go about finding the right developers to fork this and update it? I am genuinely willing to pay up to 100$ for it to work again how it used to.. On Mon, Jan 6, 2025 at 8:29 PM Mike Carlson ***@***.***> wrote: > No, security in an operating system is rarely that targeted. The most > common cause of issues for older applications is going to be something > Apple changed to broadly improve security or, more likely, a portion of > the > Accessibility UI that was rewritten to support input device portability. > The ability to move keyboard and mouse between computers and mobile > devices > was introduced right after Big Sur. > > There's probably a change log available for the version of XCode released > with macOS 12 or 13, and that would be a good place to start. > > On Mon, Jan 6, 2025, 7:00 PM xoxo369 ***@***.***> wrote: > > > Do you think apple blocked that kind of scripts because it could be used > > as > > a keylogger? Where can i find a developer to pay to fork it and fix it? > > Also listen to my music guys! @sleepindesigner on SoundCloud > > > > On Mon, Jan 6, 2025 at 6:07 PM Mike Carlson ***@***.***> > > wrote: > > > > > Hey folks. I understand there's a small group of people here that love > > > this app, and have to come to rely on it. I am one of those people as > > well. > > > The developer has every right to move on to other interests. Nobody > does > > > independent coding for free to be shackled to their creation for the > > rest > > > of their lives. > > > > > > What I'd like to do is encourage everyone to be constructive, not > > > endlessly complain and berate the developer. Trying to guilt the dev > > into > > > continuing work on a past passion project is a losing proposition. > > > > > > Working with git is fairly easy. Forking the code is also easy. > Figuring > > > out how Apple changed the Accessibility UI portion of macOS between > Big > > Sur > > > and Ventura seems to be the thing to focus on here. AFAICS, MidiKeys > > always > > > leveraged the Accessibility UI in order to provide the Global Hot Keys > > > functionality. > > > > > > — > > > Reply to this email directly, view it on GitHub > > > <#37 (comment)>, > > or > > > unsubscribe > > > < > > > https://github.com/notifications/unsubscribe-auth/AVGETRWMDRYNZT22R3WQAU32JMLD3AVCNFSM6AAAAABHH7WPIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZUGE2DKMBYGM> > > > > > > . > > > You are receiving this because you commented.Message ID: > > > ***@***.***> > > > > > > > — > > Reply to this email directly, view it on GitHub > > <#37 (comment)>, > or > > unsubscribe > > < > https://github.com/notifications/unsubscribe-auth/AI2IFQPE7CFLTYLF5XGX6CT2JMYKRAVCNFSM6AAAAABHH7WPIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZUGI2DMNZQGQ> > > > . > > You are receiving this because you commented.Message ID: > > ***@***.***> > > > > — > Reply to this email directly, view it on GitHub > <#37 (comment)>, or > unsubscribe > < https://github.com/notifications/unsubscribe-auth/AVGETRXF4UZS47XOQS63CDD2JM3ZNAVCNFSM6AAAAABHH7WPIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZUGI3TGNJUHE> > . > You are receiving this because you commented.Message ID: > ***@***.***> > — Reply to this email directly, view it on GitHub <#37 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AI2IFQPM56DVLNF73GML3QL2JNJG5AVCNFSM6AAAAABHH7WPIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZUGM3DKMZWHE> . You are receiving this because you commented.Message ID: ***@***.***>