John Lokanis Posted April 15, 2009 Report Share Posted April 15, 2009 Here is the setup: You have a VI with at least one horizontal splitter. In each pane you have an object set to fit to pane (scale object with pane). (for example, a multi-column listbox). The user maximizes the screen. They then move the splitter bar that separates the upper and lower panes below the previous (un-maximized) bottom of the window. Finally, they return the window to its previous size (by pressing the un-maximize, or restore button). The result is a totally messed up window. Is there any way to avoid this? See attached VI. Download File:post-2411-1239747456.vi Before: After: Quote Link to comment
Darren Posted April 15, 2009 Report Share Posted April 15, 2009 Definitely a bug, I was able to reproduce in 8.6. I couldn't find a workaround, but I filed CAR# 160408 on the issue. -D Quote Link to comment
John Lokanis Posted April 15, 2009 Author Report Share Posted April 15, 2009 QUOTE (Darren @ Apr 14 2009, 03:32 PM) Definitely a bug, I was able to reproduce in 8.6. I couldn't find a workaround, but I filed CAR# 160408 on the issue.-D Thanks for the quick follow up. I guess I'll file that in the 'just don't do that' bin for now... Quote Link to comment
ShaunR Posted April 16, 2009 Report Share Posted April 16, 2009 Can reproduce it too. If you resize the window it sorts itself out. Looks like a refresh problem. I can get round it by writing to the bounds property of the vi (i.e forcing a refresh). But that doesn't enable you to "restore". Quote Link to comment
Mark Yedinak Posted April 16, 2009 Report Share Posted April 16, 2009 I reported a similar bug to NI a while back regarding the resizing of windows and panes. From what I was told at the time they weren't error checking there calculations or watching boundary conditions carefully enough. It was totally screwing up my resizing. I haven't heard of it being fixed yet. Quote Link to comment
mthheitor Posted April 17, 2021 Report Share Posted April 17, 2021 Sorry from posting in this old thread, but I'm still having the same bug 11 years later. I'm using LabVIEW 2019 and having this "restore" issue. Wasn't this problem solved? 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.