IB TWS layout nightmare

[samovar]

I disagree about Java {languages being sized for the task is much more appropriate than it being "older" or "newer"}, but 110% agree with each and every other observation. "Right on."

Right, Java is appropriate for a project like TWS, but in the meantime more reliable languages have appeared, still aimed at complex desktop applications.

Rust, for example, does a much better job at preventing memory leaks. And a runaway memory leak is the reason TWS forces that annoying daily restart upon us. (Firefox is being rewritten in Rust, while Chrome is still written in C. FF hasn't crashed for me once, this year, while Chrome crashes every day.)

 

[Bad_Badness]

This seems to have fixed some issues for me: from build 980 release notes:

"Previously the Price History tool allowed the user to rearrange columns but did not save the new arrangement when the user logged out. This has been fixed to save the new column arrangement."

 

[roca]

Mate, I run tws on over 6 displays on one machine and on 2 displays on a second machine. I never had layout issues. Not once. And I run on the newest tws version. There is something you are doing wrong for sure. What gets me is that you are looking for IBs fault before you even post a reproducible error that can be properly debugged.

What are you PC scecs and how many charts do you use? Do you experience any slowness on TWS?