[​🪟​ Custom pop-up windows in Unilogic HMI]

On 4/24/2024 at 1:31 AM, Saragani said:

Why aren't you using Layers?

You can hide an entire layer while editing the HMI, so you won't have to send to back or bring to front.

For me, layers introduce another variable to need to keep track of when editing
Also, I would now want to name all elements in the title section to keep the layer section organized  
I keep all my elements titles at default (button 6 / fixed text 14 /  binary image variable 4 / etc.) 

I can see the benefit of using layers depending on the page being created, I mean it would keep all elements better organized
Most of my HMI pages don't have enough overlapping images to justify setting layers vs. send to back / bring to front

I may try using layers going forward at some point for a screen with lots of overlapping elements

[​🪟​ Custom pop-up windows in Unilogic HMI]

14 hours ago, Fotonic said:

how to manage all the pop-up windows since they'll be placed over other HMI elements (at least in my case) and in the Unilogic editor that would cause some trouble in case the underneath HMI elements need to be accessed for editing.

I have a lot of instances with overlapped elements / graphics  where hide visibility and pop up graphics are used throughout program depending on state / button presses
Right click and use the send to back / bring to front I find easiest to work when using layers of elements



Also can copy top element delete, work on bottom element and paste deleted one back when your done

I find sometimes Copy / Paste and a couple blank HMI Editing pages is useful in keeping all elements in proper location for building and troubleshooting
deleting top layered elements Copy / Paste some more and mesh it back up together
Sometimes using coordinates to mark exact location of elements if you want to move something out of the way and place it back later

All of this is easy when its your project and you're the builder, but I do see this being a bit of a pain for the next person dealing with hidden elements in some one else's program
(but that's what "find tag" is used for) 

[System Error struct is not being used. Consider using it to get error indications]

I have some of the tags in the struct shown as read only on the HMI displayed in an ADMIN section of my project.
This does get rid of the warning when compiling, but I might be using the struct wrong for all I know.
I guess it can be tied in with alarms, but this might be overkill.

[Edit the IP address edit via HMI instead of UniApps]

Would also like to see a similar IP Address feature.   Ability to set IP Addresses as Retained Tag Values directly in UniLogic.   (Panel IP / CPU IP / Ethernet IP Scanners / etc.)
I'm guessing it's easier said than done (or maybe there's a reason it shouldn't be done someone can explain.) 
I have multiple projects all with the exact same code except for IP Addresses which have to be set manually in UniLogic every time for a download / update. 
Would be neat to not have to keep track of these numbers where something as simple as below example would work.

Thanks

[User Access Control - logged out automatically after a download without reset when should not]

Also have this same question using UAC.

It is a nuisance to have to log back into the HMI every single time for a minor download when building / testing a program.
marking UAC system struct as retained throws an error list warning that it is not recommended (still forces login anyways)
Anybody know a work around / way to Enable/Disable UAC without Restoring all Defaults?
Even a way to store the User name to the login box without needing to select from the drop down menu would save a couple steps and help.

Thanks!