I have just spent many hours to get some code to work, and it is still not working. Coming back to the forum for some hints/help, I find I am not alone working in this same area. Code works with Enter, but not with mouse,
(or vice versa, I have already forgotten I have done it so many ways).
This has got to be the most confusing part of Sesame that I have encountered. I don't think I am alone in thinking that the expectation is that Element Exit programming should run when you exit the element. It should not matter if done with the mouse, with ENTER/Tab/Arrow.
If we must live with this, and it depends on the Mode, then I could use some explanation about which "Mode" is used. There is a lot of inconsistency about the term Mode.
Quote: If leaving one element of a Table view subform to go to another layout element on a different form, the On Element Exit event for the First element will fire only if you are in Edit Mode. If you are in Navigate Mode, The on element exit event will not fire as that element in the subform still has focus for that form even though that form as a whole does not have focus.
Could you please explain Navigate Mode vs. Edit Mode vs. Preview Mode, vs. Add Mode, Update Mode, etc. Page of Users Manual only list 4 modes -Search/Update/Add/Working.
Where is Navigate Mode?
I have spent many hours trying to get TableView SubForm code to execute to no avail. Spencer has been having the same problem, Carl has been having the same problem. I still have "basic" instructions that will not execute consistently. We need to have easy to use tools that do not require extensive code just to do a simple ThrowFocus for example.
If this was for myself, maybe I could live with it.
If I am working for someone else and billing per hour, then my end user could not afford the programs. Since I want to keep their cost down, then I must do this work at no charge so they can afford the product, but now I pay the cost in lost productivity.
If I am working on fixed cost vs. hourly, then I am losing many hours that could be billed for other tasks.
The quote above is probably a good start, but could someone please provide a decision tree that Sesame follows when exiting an element, using the same terminology that is in the Users Guide and Programming Guide?
Like this simplified model, but with all decision branches and the logical order that is followed:
What is the Mode?
If Mode = n then ........
If sub form then ......
If trigger to exit was Enter then ......
If trigger to exit was Mouse then......
We can continue to submit code examples and ask Ray to solve the problem, but it is more important that we have the information so we understand what is going to happen when an element loses focus.
What about when Ray is not available like this weekend, or any other time?
We need to be able to write simple "click" routines that do complete tasks, and not have to add Calculate buttons to parent forms and rely on someones memory to click on a button.
Please understand, this should not be read as a complaint, but as a PLEA for easy to understand logic flow. I don't think that Carl or Spencer or myself are beginners, but it is obvious that we are struggling with some stuf that should be really basic to do.
Looking forward to see the logic flow......thanks for listening.