Is your feature request related to a problem? Please describe.
I think it would potentially be easier to manage inventory if I could have both the bank and warbank visible at the same time.
Describe the solution you'd like
I think the simplest solution would be to be able to open a second copy of the existing window; I'm fine having to select bank/warbank in each from their individual bag changer bars.
Describe alternatives you've considered
I skimmed over #1943 and saw the varying solutions you were initially looking at for combining bank and warbank into a single window. I think my potential solution might be a much simpler way to accomplish my goals, but I wouldn't be surprised if there were complications I was unaware of (such as selecting a bag from the bag changer acting on both windows rather than being independent, or blizzard's implementation making this unfeasible).
Additional context
I'd be happy with any solution to accomplish this; maybe something already exists that I'm unaware of.
(Not that using the bag 10-14 rules for the blueprint isn't viable for me, as I would like my one-blueprint-for-all-windows to apply within both the bank and warbank contexts).
Is your feature request related to a problem? Please describe.
I think it would potentially be easier to manage inventory if I could have both the bank and warbank visible at the same time.
Describe the solution you'd like
I think the simplest solution would be to be able to open a second copy of the existing window; I'm fine having to select bank/warbank in each from their individual bag changer bars.
Describe alternatives you've considered
I skimmed over #1943 and saw the varying solutions you were initially looking at for combining bank and warbank into a single window. I think my potential solution might be a much simpler way to accomplish my goals, but I wouldn't be surprised if there were complications I was unaware of (such as selecting a bag from the bag changer acting on both windows rather than being independent, or blizzard's implementation making this unfeasible).
Additional context
I'd be happy with any solution to accomplish this; maybe something already exists that I'm unaware of.
(Not that using the bag 10-14 rules for the blueprint isn't viable for me, as I would like my one-blueprint-for-all-windows to apply within both the bank and warbank contexts).