locked Re: Any plans to add more RX squares ?
toggle quoted messageShow quoted text
I had thought of this myself but, as Laurie has previously noted and as I’ve now come understand, it is not just a matter of visual real-estate but, more importantly, the time it takes for (1) painting (aka “rendering”) the squares and (2) the user to read, interpret and react to the squares. Perhaps even most important is, after all the above, there is no more time for the user to execute their desired action before the grid start to re-render the next time slice.
The nifty feature Laurie added a while back to retain the grid cell data as log as possible up to a limit does not help when all the grid cells are already populated.
In so much as it can take at least 1-6 secs to render all the squares based on PC and code speed plus another 1-2 secs for typical cognitive brain response. That leaves less than 8-10 secs to visually, decipher and react to their analysis of 50 info boxes?
I may be maturing but I challenge anyone to keep that up for more than a few minutes without entering something us data nerds used to call “data wash” or “data-out”.
However, assuming there are no other limiting factors and it is technically possible, I am not opposed to allowing a user to select another 1 row and column for a total of 50 grid cells. Such an option would be inherently self-limiting when the user realizes they can’t respond to the resulting deluge.
Just my 13 cents.
TomK KT1TK 73
From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Thursday, September 24, 2020 8:49 PM
Subject: Re: [HamApps] Any plans to add more RX squares ?
On 25/09/2020 10:15 am, ed.n5dg@... wrote: