My method has zero overhead, and would execute faster. With your method, if you had 40 buttons you had to disable, you would need an additional 40 transparent buttons to effectively disable the actual buttons. The recommendations for FTView, and indeed any HMI or SCADA system, has always been to minimise the number of active objects on the displays. ![]() I would much rather place a wallpapered image of the button, perhaps with a red line through it to show it is not available for use, and make the available real buttons visible by user credentials. ![]() I most certainly have had the need to disable buttons for unauthorised users.Įach to their own method, but I still don't like the idea of the display scan having to parse dynamic objects that (a) needn't be visible to an unauthorised user, (b) will slow down the HMI scan, (c) use more memory, and (d) could cause confusion to an unauthorised user, as he may be pressing "hidden" (by the transparant overlay) buttons that won't work. Using the object explorer/browser makes it easy for everyone to see the hierarchy. rectangle retro lightbox billboard vintage frame sign board. floral vintage retro golden corner border rectangle frame transparent background free vector and. Grouping makes sure everything goes together if moved. Lacupella Acrylic Transparent Fondant Smoother Rectangle Crafted from high quality food safe cast acrylic, heavy duty construction for everyday use 1/2 inch. vintage golden floral retro corner border or rectangle frame transparent background. You obviously haven't had a need, at least two in this thread have. Of course you can set it to NULLBRUSH to make it look transparent: windowClass. There are many times you want to show objects but not allow use. ![]() It's a work around for not having an enabled property. Daba, yes it's more work (seconds of work).
0 Comments
Leave a Reply. |