Has anyone had the same issue? I have a few watchlist pages for different sectors. They share the same column set. All of them are using "Default Layout" templates. But the layout is actually inconsistent in term of column width. Even worse, when I adjust Page A to be in a good shape, page B would be affected unexpectedly, making Page B's layout screw up. What I expect is once Page A becomes good, all other pages follow the same column width. If this is impossible, I'm OK to do manual adjustment one by one, since this is a one-off work. But now when I adjust page A, page B becomes bad. When I adjust B, A becomes bad again. This is really annoying. Is there a good way to fix it? I'm using 2020/09/09 release. But I think this has been a long standing issue.
you need to give same name to pages of similar functionality, instead all page assuming name "default".
Wow, can't believe this is a common issue that has been so long. Is it possible to hack the settings xml to fix the issue ourselves? The xml file looks fairly complicated. Curious if there's any tutorial on this.
Trend2009 has given you the solution: use as template "Layout A", "Layout B"... where "Layout A" is your custom template for page A.
Thanks for the reminder. So effectively each page would has its own customized settings stored in the corresponding template? Yeah I'll try this out. One downside is that if we want to add a new column to every page, we'll have to add them into every template, instead of just "Default Template". But I think this is less annoying than the column width issue.
Yep , this is an embarrassment to InteractiveBrokers. Obviously a programming bug that could easily be fixed , if they had respect for the time and trouble of their customers . It's decades old !!!!! Yes decades . My workaround has always been to have a unique layout for EVERY DAMN page. A pain in the butt , and defeats the whole purpose of layouts!!!! Maybe they will read this and fix this basic functionality instead of adding another esoteric feature 1 out of 10,000 will use
LOL. If it's been decades long, I suspect that feature is legacy code, and thus none wants to touch it. And such task comes with very low priority to fix, unless the customer complaints are too loud to ignore. Could it because they don't actively support the "Classic View"?
Of course its legacy. Obvious . A legacy BUG And as a programmer, I think Im qualified to say that fixing it is not a big deal, and is probably quite simple . Jesus, all we're talking about here is synchronizing layouts without destroying one page when you move a column on the other. This basic functionality of the user interface is totally whacked. People are wimps and dont complain . They just suffer in silence I use dozens of programs, and NONE have a problem this severe in a widely used portion of the app. As I said, the TWS programmers should be ashamed to leave this unfixed, and make customers fight with the platform