This event needs to be restricted to when a record is clicked on. Currently, it fires under all kinds of circumstances (1st time form load, new dataset, running getFoundSetUpdater [fires once still – but not for every record like it used to], etc).
It gets trully confusing when there are multiple tab panels on a form – each showing a form with an onRecordSelection event. You really can’t do anything useful with this event when they are all firing at uncontrollable times.
Hi David,
I can understand your frustration. BUT - I think you’re looking for a different kind of event. I think they SHOULD fire a lot - because I do lots of dynamic setup stuff that can be affected by changing foundsets, etc.
Just my own personal USD $0.02…
Hi Bob,
Maybe. I would have to understand a bit more about what you are doing before I disagree with you but it seems to me that dynamic stuff that relies on changing found sets can be dealt with in any number of different ways. The only thing that can’t be dealt with in another way is soon to be fixed with the addition of an onSearch event (trapping for a manual user search).
Currently, the only way to trap for a user clicking a record in a list or table view is to put an invisible button over a row in a list view or attach the same method to all the fields in a table view. Not the most elegant of solutions.
In any case, I can’t think of a situation where it is advantageous to have the onRecordSelection event fire when using a getFoundSetUpdater. (FYI: every form that shares the same table and is visible fires the onRecordSelection event when employing getFoundSetUpdater.)
Everything that fires the onRecordSelection event I use ALL the time and in a wide variety of circumstances. And these circumstances can’t be trapped for (if getFoundSetUpdater just ran, don’t do this…).
To me, it seems that some more thought needs to go into this implementation so maybe we are in fact agreeing
The current definition is when a record is selected, not taking in account where the selection comes from.
-Can be a script changing the selection
-User click
-User record nav. with ALT up/down
-(selected) record change (for example after a find)
What you want is somthing like onRecordClick or Action…I guess
Makes sense. With the definition being that broad I have yet to find a situation where I can safely use it. I know I would use an “onRecordClick” event all the time.