Recently I have noticed, that even if I choose fixed size, webvisu comes up with a reduced resolution. What I see, is "DevicePixelRatio = 1.25. This ends up with blurry fonts, and some scaling problems / some thin lines invisible. While the same visu works perfecly with targetvis, Ratio 1.0: Sharp fonts, proper size. So, what's going on exactly? What is this device pixel ratio, and why isn't it 1? (the generated webvisu meta tag show ratio 1.0...) This is using 3.5.18 SP3 VISU 4.3.
Maybe this is relevant for you: https://forge.codesys.com/forge/talk/Runtime/thread/cd00f6c317/#2905 However, you can use managed ethernet switches, and their ports as virtual network adapter for your OS, using VLAN tagging...
Maybe this is relevant for you: https://forge.codesys.com/forge/talk/Runtime/thread/cd00f6c317/#2905
The easiest thing you can do is to add a code to ""OnMouseClick"" input: TestVar:= NOT TestVar; Other option is to bind TestVar to ""Input configuration / Toggle / Variable""
When I finished posting the opening post / question of the topic I had the impression, that it won't be easy to get obvious and clean answer for such a complex value as "performance". It is interesting to see the changes in CODESYS from 2.3 to nowadays. I remember I could barely wait the first release of 5.3 or 5.4 on Moeller XV panel - the object oriented features very promising. That time, and still now I'm hoping to have a development platform that can spare me a lot of time - building reusable,...
When I finished posting the opening post / question of the topic I had the impression, that it won't be easy to get obvious and clean answer for such a complex value as "performance". It is interesting to see the changes in CODESYS from 2.3 to nowadays. I remember I could barely wait the first release of 5.3 or 5.4 on Moeller XV panel - the object oriented features very promising. That time, and still now I'm hoping to have a development platform that can spare me a lot of time - building reusable,...
When I finished posting the opening post / question of the topic I had the impression, that it won't be easy to get obvious and clean answer for such a complex value as "performance". It is interesting to see the changes in CODESYS from 2.3 to nowadays. I remember I could barely wait the first release of 5.3 or 5.4 on Moeller XV panel - the object oriented features very promising. That time, and still now I'm hoping to have a development platform that can spare me a lot of time - building reusable,...
"You can also configure a visualization element with a property in those properties where you select an IEC variable. Then CODESYS creates additional code for the property handling when a visualization is compiled." Funny, but the "activate property handling for all visualization" was recently removed (SP17 or 18?)... This might suggest, that it doesn't really matter anymore? "A plus for the interface approach is that you can handle FBs with different logic with the same visualization element. You...