HeliosDisplayManagement
HeliosDisplayManagement copied to clipboard
Command line 'arguments' parsing hyphens
Hey there,
Brilliant program, thanks for the work!
I've noticed that the command line --arguments "blah"
doesn't play nice when the arguments contain a hyphen as the executable isn't escaping / ignoring any hyphens inside the quotation marks, so attempts to parse something like
--arguments "-tcp"
as a second -t time call such as -t cp
and fails as a result (tested with -tcp and -nosplash), one provides the error -t/--timeout option violates format
, the other is being treated as -n with no error and the usual list of command line options pops up.
Initially occurred with a shortcut made by HDM itself, so I assume just the way the executable reads them in.
As a secondary question (that isn't an issue) do you have a road map or list of 'possible features' somewhere? I'm interested to see where this is going and what is already planned so I don't end up posting feature requests you're already working on.
Hey,
Yeah, I am aware of the issue with the command line. This is what .Net does and there is no clear away around that. I need to investigate this further.
In regard to what I have in mind to do with this project:
- Make it possible to edit profiles
- Make it possible to add a new profile directly from the application
- Automatic update check and notifications
- Create a read me file
- Considering if we should save and apply monitor colour configuration (#9)
- Considering if we should save and apply taskbar settings (#14) - The code behind this is already done actually
- AMD Eyefinity support using ADL
Makes sense that .NET would have a silly problem like that.
Any possibility of keeping that list / considered features somewhere open like the Wiki page for the project? Including 'current complete / partially implemented features' so that people can get an idea without necessarily having to poke around the application?
Thanks again!
That supposed to be the job of "Create a read me file" task. But at this point, I rather try to add the much-needed edit and add profile feature instead of writing a read me file. But in time, before even trying to implement AMD Eyefinity API I will make sure to fix the readme file. That would be the first release of this project as well (v1).
To this date, every release was a pre-release. Let's just say I am not happy with the state of this project as of now. I just need more time. I have a plan :)
Ah right, I understood it was pre-release, my questions were more from the point of view of outside assistance, say someone else saw the project and wanted to see if they could help or had experience / existing code/information they could port to it, knowing where it's at and what is planned makes it easier to direct any such input.