Support Board
Date/Time: Tue, 26 Nov 2024 17:23:23 +0000
Post From: GDI w/2551 and study updates (manual vs auto looping implications)
| [2023-11-11 23:27:38] |
| User719512 - Posts: 264 |
|
You can also force repainting by moving the chart as it has to redraw the screen. Your approach of using persistent data from the main study is the best way I have found, and why the GDI function gets the SC param, since it has no state otherwise. You can optimize by looking at visible bars as well for bar-specific info versus static drawings on the screen that don't scroll with the bars. An approach I use is a single GetPersistentPointer, and then the struct I point it to can change without a ton of updates to the scsf_ code. new it during IsFullRecalculation, and delete during LastCallToFunction. It's a great pattern even if not using GDI. Way easier to manage built-in types, lists<>, etc. in my opinion. Example: PersistentData* p_PersistentData = (PersistentData*)sc.GetPersistentPointer(42);
|