Oohhh... Please Expose "Clone Monitor"" Button (Greyed?) on "Console" By Default! (TL;DR)
Posted: Sun Sep 22, 2024 11:46 am
Think tongue in cheek. It's like sarcasm without all that sarcasm.
I've suffered at least 10 discussions about presets, configs, cloning , monitors, id's, copying ,dumping and zmcamtool.pl...
At least 3 or 4 times over at least 5 years....
When the answer to my question and perhaps %80 of others' has been hiding in plain sight for a decade or so.
If you know where to look.
In the manual, hover help, intros, the usual suspects no-one has time for I'm sure.....
But also if you tic a box next to any monitor on the "Console" page. (1.37)...
It's the "Clone Monitor" function.
Everybody has a favorite button they want on top but I think this button competes effectively with the "Scan" button.
In a non-ONVIF environment, this is likely to be the GO-TO button for pros and new users alike after getting the first monitor up and running....
To add a second, third, and Nth identical camera quick fast in a hurry.
And handy even in an ONVIF environment from time to time I bet.
Please unmask this magical bean by default...
Greyed out until a monitor is selected...
Or throw up an error dialog to select monitor..
Or nice to have three-state behavior(always exposed):
1. Enable/Highlight CM button and use settings from ID1 as default if only ID1 and/or clones of ID1 are listed in Console, regardless as to whether ID1 or clones are tic'd. This invites new user "press next" behavior, which is likely desired behavior when facing a second camera. Likely enough, anyway
2. Grey CM button if there is room for ambiguity, ie: fails above, and no monitor is tic'd.
3. Enable CM button if monitor is tic'd, a bit like the behavior it has now.
As well as being interested in seeing this done I'm curious as to what it might entail codewise, especially with respect to scale of affected code. I don't program much beyond machine language but sometimes succeed in modifying code of almost any description, at least a bit.
I'm thinking the simple case of swapping out the hidden "Clone" button for a greyed out button on "Console"....no third state...
Could be as "simple" as a skin tweak or even an option already present somewhere...
Or 3 files, 3 chunks of code to grab, 10 lines of code to modify, 10 lines code to write, max...
Or is that naive.
About 9-12 hours for me lol
What might it actually entail, and what might a reasonable bounty for such a thing be, I was about to donate again anyway and is that much the same thing LOL. Note I don't remember but suspect my donations have been pretty paltry ha.
I've suffered at least 10 discussions about presets, configs, cloning , monitors, id's, copying ,dumping and zmcamtool.pl...
At least 3 or 4 times over at least 5 years....
When the answer to my question and perhaps %80 of others' has been hiding in plain sight for a decade or so.
If you know where to look.
In the manual, hover help, intros, the usual suspects no-one has time for I'm sure.....
But also if you tic a box next to any monitor on the "Console" page. (1.37)...
It's the "Clone Monitor" function.
Everybody has a favorite button they want on top but I think this button competes effectively with the "Scan" button.
In a non-ONVIF environment, this is likely to be the GO-TO button for pros and new users alike after getting the first monitor up and running....
To add a second, third, and Nth identical camera quick fast in a hurry.
And handy even in an ONVIF environment from time to time I bet.
Please unmask this magical bean by default...
Greyed out until a monitor is selected...
Or throw up an error dialog to select monitor..
Or nice to have three-state behavior(always exposed):
1. Enable/Highlight CM button and use settings from ID1 as default if only ID1 and/or clones of ID1 are listed in Console, regardless as to whether ID1 or clones are tic'd. This invites new user "press next" behavior, which is likely desired behavior when facing a second camera. Likely enough, anyway
2. Grey CM button if there is room for ambiguity, ie: fails above, and no monitor is tic'd.
3. Enable CM button if monitor is tic'd, a bit like the behavior it has now.
As well as being interested in seeing this done I'm curious as to what it might entail codewise, especially with respect to scale of affected code. I don't program much beyond machine language but sometimes succeed in modifying code of almost any description, at least a bit.
I'm thinking the simple case of swapping out the hidden "Clone" button for a greyed out button on "Console"....no third state...
Could be as "simple" as a skin tweak or even an option already present somewhere...
Or 3 files, 3 chunks of code to grab, 10 lines of code to modify, 10 lines code to write, max...
Or is that naive.
About 9-12 hours for me lol
What might it actually entail, and what might a reasonable bounty for such a thing be, I was about to donate again anyway and is that much the same thing LOL. Note I don't remember but suspect my donations have been pretty paltry ha.