v8.1.43
When you have a coordinate view set to percent with the aspect ratio set to the ratio of the view's size, and you embed a coordinate container that contains pipes (e.g. screenshot) set to percent mode with no aspect ratio (uses the parent view coord container), then when the page loads in the browser, the pipes will not load with the correct size. If you slightly change the size of the browser, it will then resize the pipes correctly.
@mperkins
This is kind of a major display issue and affects every single one of our P&ID mimic screens, and causes all pipework to be misaligned with the devices and other content on the screen, causing confusion to operators. I can't find a viable workaround; moving pipes to the main view is not an option since editing them then becomes impossible due to the sheer number of connection points that then become displayed from all of the other components on the page - this also leads to extreme lag in the interface.
1 Like
This is one of the reasons I moved away from percent mode on coordinate container P&ID screens. I was having this problem with pipes and embedded SVGs mostly.
I usually design my plant floor coordinate screens to work in 1080P and embed that in a breakpoint container to support other sets of resolutions if I'm going to support other resolutions. I generally run my apps in full screen mode because browser UI can cause scroll bars otherwise.
I've also found that a few of my customers have preferred to scroll across a static screen on smaller screens because they're more excited about gaining access from their phones which was never an option before.
One big caveat I've run into with a static resolution is with anchor points causing scroll bars. If you accidentally move an anchor point for an element it can cause you to get scroll bars even though the element is clearly within the bounds of the screens.
can i get a sample view? this feels like something i have delt with before but i dont remeber off the top of my head
1 Like
Before I make a bug ticket for this:
what browser are you seeing this in and can you provide a project or sample view exhibiting the behavior?
1 Like
This is in Chrome and Edge.
I'm trying to produce the simplest page I can to demo the bug, but struggling to get it to misbehave at the moment... I'll upload when I can reproduce it
1 Like
I'm pretty sure it only happens when you have a side dock defined and visible...
I would export the project resources, but the Export Project resources popup has locked up the whole designer when I pressed "Export" 
I'll grab the raw json...
Edit: Oh wait, it came good after about 5mins...
BrokenAlignment.zip (31.3 KB)
This is the left side dock that is configured on both views:
Edit2:
I got the simpler view to die as well by just adding more pipes. I'll upload the new version in 5mins once the save dialogue finally opens (I suspect that the file dialogue is trying to connect to some remote network folder and it can't, and is timing out after an absurdly long time - literally ~4mins after roughly timing it).... but I just added these pipes
BrokenAlignmentSimpleView.zip (9.0 KB)
1 Like
So i noticed your folder _Testing.. i have had examples of you before named _TESTING and it seems my ignition was lagging a bunch too when i imported your stuf, i saw both folders untill it started lagging i closed up everything and reopend and now i only had _TESTING left merging it with the previous folder. maybe something wierd happening there
Anyways i see no problems on my end with the aligment, im on the latest chrome version. firefox also had no problems
1 Like
Did you make sure to set the sidebar to be visible on load? If you're using the navigation between the two pages, then both pages need to have the sidebar set with the same, always-shown settings
I don't know if it's a factor, but I also have an always-shown navigation dock at the top too
1 Like
I haven't been successful in reproducing it yet, but I am creating a bug ticket now so that this can be tracked.
1 Like
I got my colleague to test in v8.1.45 as well and found some weird things. It seems to depend on a few things:
- browser zoom level. Outside of 100%, the misalignment occurs less (he didn't have an issue with the more complex page, but the simpler view still misaligned). At 100% it always misaligns for Edge and Chrome.
- browser: firefox doesn't appear to have the issue at all.
Sometimes the misalignment happens and resizing the width of the browser doesn't fix it, but resizing the height does.
1 Like
Well this is a major display issue for us now after upgrading, so I decided to see if I could work around it somehow. I added a dreaded sleep just to test, to an onchange event when the primary view's page changed size, which simply reads the aspect ratio and changes it by 1 pixel so as to force the page components to readjust, and it did work. The sleep itself is set to 100ms. It's certainly not a permanent fix and it's a horrible work around, but it does realign the pipes... It would be a nightmare to roll out to 100's of our views though, not to mention the potential catastrophe having 100's of views with 100ms sleeps in them may cause.
pageSize is bound to the page.props.dimensions.primaryView.x props- for this particular page, the height is 700, so the '1' simply changes it to 701 with as minimal effort as possible. obviously I wouldn't use this if I was rolling this out to other views
Obviously not a solution, but maybe it helps in identifying and fixing the issue on IA's end
Edit: even a 10ms sleep seems to work
Edit2: removing the sleep works too... I'm sure I tried it without the sleep before...
