mje Posted March 14, 2014 Report Share Posted March 14, 2014 Hi all, I'm wondering if any of you see odd behavior when trying to maximize/restore a window that contains a splitter with subpanels. Specifically if the spliter's panes are set to have minimum bounds, then filled with subpanels, some weird stuff can happen if the window is restored from a maximized state that would violate the a pane's sizing restriction. Best demonstrated in a video: https://www.dropbox.com/sc/raat2m37x1gekl7/qwvo0ldgG_ m Quote Link to comment
Darin Posted March 14, 2014 Report Share Posted March 14, 2014 I'm wondering if any of you see odd behavior when trying to maximize/restore a window that contains a splitter with subpanels. If something like that worked flawlessly it would strike me as pretty odd. Quote Link to comment
0_o Posted March 16, 2014 Report Share Posted March 16, 2014 I saw this happening while working with cursor menu of graphs inside FP that was using splitters.It was very similar to what Cat wrote back in 2010 http://lavag.org/topic/12577-unintentional-cursor-tool-resizing/When I reported it 4 years later I got the following reply:This is a rare bug few people reported. NI expects it to be solved by LV2014.I ended up writing my own cursor menu and still got LV bugs.I'm now at my 4th try with/o splitters waiting to see what LV comes up with next.I stopped counting how many projects I did failed because LV had bugs I couldn't bypass with the classes of LV2011 being the worst.Good luck. Quote Link to comment
mje Posted March 16, 2014 Author Report Share Posted March 16, 2014 Eh, it's not that bad of a bug, it just shifts the layout logic from being automatic to tediously manual. I just need to have the VIs in the subpanels adjust their layouts programmatically. Pain in the ass? Yes. Time consuming and shouldn't be necessary in modern languages? Absolutely. But not difficult. Quote Link to comment
0_o Posted March 16, 2014 Report Share Posted March 16, 2014 Sadly, in my case the cursor legend doesn't have a reference/property node since LV8 and writing my own worked a bit better yet still had lots of LV bugs to deal with and I just didn't want to keep on going and finding more and more bugs so I just left the splitter approach. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.