Trend View Feature Requests

[franji1]

Does anyone else feel like DmD cripples with too much Trend View data compiling, and frequently have to kill DmD from the Task Manager and start it over?

We've seen this lately, probably due to all the more advanced features/instructions being added every release.  The next release will address that, but basically, if you have a bunch of Ladder Views doing status and a bunch of Trend Views doing status, the GUI can get overwhelmed.  Then menus start to get slow (the Ladder Toolbox animations gets real S-L-O-W - that's how I know the GUI is starting to get overwhelmed).

Realtime status is not trivial.  Even the best PCs can get bogged down once you add more and more and more live status.  When it gets bogged down, turn off status on specific views, or just close them outright.  I've seen projects with 10/20/50/100 code blocks, but you typically only need to do status on a few at any one time.

Trend Views I understand - those maintain historical data.  Just close down unused Ladder Views and the software should respond better (especially if you have a number of Trend Views logging for DAYS)

[Controls Guy]

It can be kind of a pain in the butt to have to constantly maintain Status status for each tab individually on an ongoing basis.

Would it be practical to have only visible tabs polling, even when status is enabled for that tab?   Or greatly reduce refresh frequency on hidden tabs, say like 10% of the default update frequency?

(And yeah, anything DMD session just sitting there collecting days of data, I definitely turn off status or close any open ladder tabs)