[GH-ISSUE #121] Release with updated DCC.swift? #89

Closed
opened 2026-05-05 05:01:27 -06:00 by gitea-mirror · 8 comments
Owner

Originally created by @danDanV1 on GitHub (Sep 12, 2019).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/121

reitermarkus/DDC.swift has been updated with a fix that should allow support for Acer monitors.

Based on update to kfix/ddctl which implement Fix signed/unsigned compare.
https://github.com/kfix/ddcctl/issues/53

@the0neyouseek Can you issue a release with the DCC.swift dependancy updated to latest commit?
41e7c49b04

Originally created by @danDanV1 on GitHub (Sep 12, 2019). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/121 reitermarkus/DDC.swift has been updated with a fix that should allow support for Acer monitors. Based on update to kfix/ddctl which implement Fix signed/unsigned compare. https://github.com/kfix/ddcctl/issues/53 @the0neyouseek Can you issue a release with the DCC.swift dependancy updated to latest commit? https://github.com/reitermarkus/DDC.swift/commit/41e7c49b0450033c5349ca1cf5234a26ebc011b8
Author
Owner

@danDanV1 commented on GitHub (Sep 14, 2019):

@JoniVR should I create a pull request for this? would you accept?

<!-- gh-comment-id:531518077 --> @danDanV1 commented on GitHub (Sep 14, 2019): @JoniVR should I create a pull request for this? would you accept?
Author
Owner

@JoniVR commented on GitHub (Sep 14, 2019):

I was planning on updating DDC.swift first thing when I get time. Then trying to merge in #116 and then create a release. I’ll try to get that done tomorrow but I can’t promise anything. But a PR is not really necessary since it’s should be pretty easy to do.

<!-- gh-comment-id:531520010 --> @JoniVR commented on GitHub (Sep 14, 2019): I was planning on updating DDC.swift first thing when I get time. Then trying to merge in #116 and then create a release. I’ll try to get that done tomorrow but I can’t promise anything. But a PR is not really necessary since it’s should be pretty easy to do.
Author
Owner

@JoniVR commented on GitHub (Sep 14, 2019):

Actually I think I’ll create a release before merging in #116 so we can get these critical fixes out faster.

<!-- gh-comment-id:531520207 --> @JoniVR commented on GitHub (Sep 14, 2019): Actually I think I’ll create a release before merging in #116 so we can get these critical fixes out faster.
Author
Owner

@JoniVR commented on GitHub (Sep 15, 2019):

New release (v1.7.0) has been created. Please let me know if you run into any issues. I'm going to consider this closed in the meantime. :)

<!-- gh-comment-id:531524275 --> @JoniVR commented on GitHub (Sep 15, 2019): New release (v1.7.0) has been created. Please let me know if you run into any issues. I'm going to consider this closed in the meantime. :)
Author
Owner

@danDanV1 commented on GitHub (Sep 15, 2019):

Nice. Works like a charm. Now I can finally control my Acer monitor!

BTW. Not a biggie, but the release wasn't signed with a developer ID. Gives the 'ol "can’t be opened because Apple cannot check it for malicious software" message.

<!-- gh-comment-id:531534921 --> @danDanV1 commented on GitHub (Sep 15, 2019): Nice. Works like a charm. Now I can finally control my Acer monitor! BTW. Not a biggie, but the release wasn't signed with a developer ID. Gives the 'ol "can’t be opened because Apple cannot check it for malicious software" message.
Author
Owner

@danDanV1 commented on GitHub (Sep 15, 2019):

and thank you!

<!-- gh-comment-id:531534928 --> @danDanV1 commented on GitHub (Sep 15, 2019): and thank you!
Author
Owner

@JoniVR commented on GitHub (Sep 15, 2019):

BTW. Not a biggie, but the release wasn't signed with a developer ID. Gives the 'ol "can’t be opened because Apple cannot check it for malicious software" message.

Thanks for letting me know, I think I forgot to notarize because I did sign it. I'll look into it later.

<!-- gh-comment-id:531552845 --> @JoniVR commented on GitHub (Sep 15, 2019): > BTW. Not a biggie, but the release wasn't signed with a developer ID. Gives the 'ol "can’t be opened because Apple cannot check it for malicious software" message. Thanks for letting me know, I think I forgot to notarize because I did sign it. I'll look into it later.
Author
Owner

@JoniVR commented on GitHub (Sep 15, 2019):

Should be fixed now :)

<!-- gh-comment-id:531558372 --> @JoniVR commented on GitHub (Sep 15, 2019): Should be fixed now :)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/MonitorControl#89
No description provided.