Author Topic: Calculations Panel progress question  (Read 449 times)

0 Members and 1 Guest are viewing this topic.

Padanges

  • Newbie
  • *
  • Posts: 179
Calculations Panel progress question
« on: August 25, 2016, 09:14:48 PM »
Hi,
I'm running some heavy calculations using Calculations Panel (which exponentially depend on ScanGrid entry count - something you get when you need string sorting) and it noticeably freezes the grid (before it gets to the final calculation). Is there a way to make the Grid not to wait for the panel to finish calculations? Or to run calculations in the background?


Regards.

Padanges

  • Newbie
  • *
  • Posts: 179
Re: Calculations Panel progress question
« Reply #1 on: August 25, 2016, 09:35:29 PM »
A follow up question. If it's currently not possible (and requires major changes) to make Grid not to wait for the Calc Panel to return values, then how can I specify not to recalculate on each entry focus change (or mouse click) the whole script? I'm thinking about some sort of conditional statement "if entries not updated then leave calculations unchanged".

RTT

  • Administrator
  • *****
  • Posts: 764
Re: Calculations Panel progress question
« Reply #2 on: August 26, 2016, 02:16:13 AM »
Is there a way to make the Grid not to wait for the panel to finish calculations? Or to run calculations in the background?
No. Running the calculations it in the background is obviously a possibility I should explore. Thanks for pointing out the issue.

A follow up question. If it's currently not possible (and requires major changes) to make Grid not to wait for the Calc Panel to return values, then how can I specify not to recalculate on each entry focus change (or mouse click) the whole script? I'm thinking about some sort of conditional statement "if entries not updated then leave calculations unchanged".

Indeed the calculations panel code is being executed with each grid click, from some code that processes the uncheck all if click not accompanied with the ctrl, or shift, key down, and obviously should only execute if indeed any row got unchecked. Fixed now. Other than that, all the other situations may result in different results, so code must be executed.
Currently the code gets executed for all the rows, if none checked, of just for the checked ones, if any checked. That's why we also get a panel refresh when a row gets checked/unchecked.