Tab view container keeps switching back

unhandled

#1

This is probably a wish list thing. Every time something upstream from tab view component changes, the tab view snaps back to the first tab. I wish it remembers which tab I have open last.


(Andrew Heumann) #2

it just means you’re not updating contents correctly. If you use “Set” output components to update the contents of the window the tab will stay.


#3

Thanks!


#4

This is very helpful! It seems as though there is a length limit to the “tabbed interface” I wonder if there is a way to give more vertical dimension to a “tabbed interface”?


(Andrew Heumann) #5

what do you mean length limit? if you have too many tabs to fit on one line they will fold onto another line: image


#6

Sorry, to clarify, I am asking about the actual length of the contents of the tab.


(Andrew Heumann) #7

there should be no limit on that either. can you send a screenshot? what are you experiencing?


#8

I also noticed that radio buttons in different tabs are not one-only selected, even though they are grouped together. Is there a way to make sure they switch?


(Andrew Heumann) #9

this is the normal and desired behavior - since a tab creates a different Root Visual it separates the scope of the radio button groups, as I understand it.

The GroupName uses the root visual to determine the scope. In this way, if you open two intance of the same window, the RadioButton would still works fine. Otherwise the radio buttons in both windows will effects each other.
from https://social.msdn.microsoft.com/Forums/vstudio/en-US/3b07622f-2244-48c1-ad14-9769a9e79d35/how-to-split-a-group-of-radio-buttons-across-tabs?forum=wpf

No way around this that I know of!


(Andrew Heumann) #10

with that said, I think having linked radio buttons in different tabs would be a total anti-pattern from a UI perspective…


#11

Ah yes scope is my worst enemy…Thanks for the clarification tho.


#12

“there should be no limit on that either. can you send a screenshot? what are you experiencing?”

Thank you for confirming this @andheum We had limited our grid size, and had forgotten about setting that limit.