Skip to content

Various Enhancements#66

Merged
the0neyouseek merged 16 commits intoMonitorControl:masterfrom
reitermarkus:enhancement
May 7, 2019
Merged

Various Enhancements#66
the0neyouseek merged 16 commits intoMonitorControl:masterfrom
reitermarkus:enhancement

Conversation

@reitermarkus
Copy link
Contributor

  • Update to Swift 5
  • Switch to Carthage
  • German Translation
  • Switch to DDC.swift
  • Refactoring

@reitermarkus
Copy link
Contributor Author

@the0neyouseek, I changed the hideDisplayOsd function to check for the vendor and model number instead of the display name.

Copy link
Member

@the0neyouseek the0neyouseek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we have a more future proof approach and store this specific configuration in a file somewhere (Utils.swift for example) ? I'm thinking something like :

struct DisplayWithExceptions {
	var name: String?
	var vendorNumber: Int
	var modelNumber: Int
	var exceptions: [DisplayException]
}

enum DisplayException {
	case longerDelay
	case hideOsd
}

static let displaysToCheck: [DisplayWithExceptions] = [
	DisplayWithExceptions.init(name: "LG Ultrawide",
							   vendorNumber: 7789,
							   modelNumber: 30460,
							   exceptions: [.hideOsd, .longerDelay])
]

Then we would loop over this for any function that requires it

Edit: Other than this, amazing PR ! Thanks for your incredible work on this !

@reitermarkus
Copy link
Contributor Author

@the0neyouseek, ok, I added a whitelist now.

@the0neyouseek the0neyouseek merged commit 6e91c71 into MonitorControl:master May 7, 2019
@the0neyouseek
Copy link
Member

I'll build and publish an updated version tonight

@reitermarkus reitermarkus deleted the enhancement branch May 7, 2019 13:37
@reitermarkus
Copy link
Contributor Author

@the0neyouseek, I made a release draft so you only have to build it. 😉

@the0neyouseek
Copy link
Member

@reitermarkus Thanks for all your work ! If you have time, could you take a look through the open issues and close the ones that should now be fixed by this PR (or even #59). Have a nice day !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants