| QUOTE (clyde @ August 09, 2013 04:34 pm) | ||
Precisely - a very big issue with this suggestion. |
I thought about this quite a bit before I posted the suggestion. For over a week I pretty much ruled it out as being too big of a hit on performance for anyone's taste. But then it dawned on me that there are already calculated fields and these are not causing a performance hit (that I can sense). So if there is already a "recalculate" subroutine in GSAK for those fields that perhaps custom field recalculation could piggy-back on that routine. But even if it is not that simple, if it is a big performance hit, surely it would only be a performance hit for the actual use of such a field by the user. As such the user can then decide that its not worth the hit and turn it off if not.
I think we all use spreadsheets where recalculation is done (automatically by default). When a spreadsheet recalculation slows things down too much, it is possible to switch it from automatic to manual or off. Perhaps we would want that sort of ability here as well.
Even if the recalculation were only done after a Load, Waypoint edit/add, Global Replace, Purge logs, and whenever a macro terminates, then that would probably be perfectly adequate.
| QUOTE (clyde @ August 09, 2013 04:34 pm) |
| The other problem I see is the limitation of the sqlite language/functions For example, I don't think you could perform the calculations using sqlite alone to satisfy the Swiss grid coordinates which prompted this request. |
I do want to be sure to clarify that while the other thread got me thinking in this direction, it is not the prompt for this feature request. I was prompted by the realization of the many other uses.