-
-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Montage profiles #1057
Comments
Yeah, I figured something like this would happen with the state change code I added - it would mess up local montage group definitions. Will look into it. |
Thank you. |
Let's try this https://drive.google.com/file/d/1EChiGR9wW40SSOljCXjWMy-cKRGquYnV/view?usp=sharing Expected behavior: |
Sorry I'm not at home to get my hands on everything I need to test. Just have my mobile with me in out of town work. I will update when I get back and able to test this. |
#1057 bazillion hacks to make this work
#1057 bazillion hacks to make this work
testing, will report back Edit: It seems to be saving profiles now and working as described. |
All is well and working as described. I have compiled android debug APK and after 48 hrs I have no issues to report. Montage profiles save, persist, and work. State changes work as well. |
Actually found some buggy behavior, I will try and explain in a follow up post tmrw. |
Before you create an issue, please make sure you have read the FAQ. Common questions on API, no image etc are covered there. Please also read HOWTO REPORT ISSUES
The version of zmNinja you are reporting:
The version and OS of ZoneMinder you are using:
Platform zmNinja is running on
Did you build the package from source code yourself?
Y
Describe the bug
Montage profiles dont persist, it allows you to create and access the profiles but after you close zmNinja and its been cleared from memory then reopened, the profiles are gone.
Debug logs
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: