Availability of command-line options to get/set brightness, contrast or input

[emoacht]

This is for unsubscribed users only

As I have explained repeatedly in other Issues, the command-line options to get/set the brightness, contrast or input has been part of the add-on features since its beginning. I prioritized implementing and extending this feature over adding the code to limit its use to subscribed users only. Consequently, it has been available to unsubscribed users as well.

Now, I have almost finished implementing all the functionalities I could think of, and I have finally added the code to restrict the use by unsubscribed users.

An unsubscribed user still can use the basic functionalities to get/set the brightness of the last selected monitor as a trial, while all sub-options, except the value to set brightness, will be ignored.

This Issue is related to #437 #464 #467 #573 #585 #624 #625 #626

[DennisGaida]

Could you still add command line output (or a helpful note) when trying to make use of command-line options for non-subscribed users? I tried for a couple of minutes to get anything working and all /get does is start up the app itself - no output. Only after a lot of hair pulling and re-installs I figured out that the command-line options are hidden behind a subscription model.

[emoacht]

The header of Command-line options section in readme clearly states that it is an add-on feature. I generally believe that there is no need to add any fuction for those who don't read readme.

[DennisGaida]

I generally believe that there is no need to add any fuction for those who don't read readme.

That somehow comes off as condescending, whereas I am really trying to improve your (already good) app.

I searched for "command line options" in the readme and tried them out right away via shell. The behavior of no-output-at-all could be improved is all I am saying. Something like "This add-on feature is only available via the subscription" would have really helped me me in my quest as well as nudged me into subscribing. It makes sense from a UX perspective, but also business-wise I would say.

You are completely correct that this is documented just fine in the readme, for me it was my first contact of Monitorian also having a subscription that I didn't know about at all.