From the beginning I have been hearing that I should be using ThrowFocus() instead of GOTO.  It has been explained that GOTO was provided as a carryover from Q&A for consistency.

But I recently found that I need to change my thought process and not always use ThrowFocus() instead of GOTO.  There is a big distinction between the two.  And I believe that GOTO has its place and purpose.

GOTO will change focus and programming control instantly from that line in the programming code.
ThrowFocus() does not do that.
ThrowFocus() allows the rest of the programming to continue and does not change focus and programming control until the rest of the programming codes has been executed.

This distinction is critical.  I had some code with ThrowFocus() but had unexpected results for me.  That is because I was expecting program control to change at that part of the code, but instead it continued with the following lines. That is not what I expected.

This difference can be seen like this:
Make text elements named LE1 and LE2 and LE3
Make a text element named LE3.
Put the following code in LE1, On Element Exit.

LE2 += "Line 1" + " - "
//ThrowFocus(LE3)
GOTO LastName
LE2 += "Line 2" + " - "
LE2 += "Line 3" + " - " 

Move the cursor to LE1, and press TAB to exit the element.
This will result in LE2 will say Line 1 and focus will go to LE3.
Now comment out GOTO line and remove comments // from the ThrowFocus line, and repeat exit from LE1.
This will result in LE2 will say lines 1,2,3 and focus will go to LE3.  Totally different results.

The Programmers Guide manual is very clear in explaining the difference.
Quote:
But I had been listening to instructions here on the forum vs. RTFM, accepting the recommendations blindly, with faith. But the forum recommendations made it sound like they were interchangeable.

Two lessons learned: 
1.  ThrowFocus() is not a replacement for GOTO.  They both have their purpose and behave differently.
2.  No matter who provides recommendatioins on the forum, we should go back to the manuals and read the content for full clarification. 

Hello Bob,

You know how we preach against the use of STOP? Well Goto is the same way. Using Goto to stop additional code from running is a big No-No and is never recommended under Any circumstances. It can, in every case I have ever seen, be replaced by a ThrowFocus() and a conditional.

If you as the programmer are counting on Goto's nature to not run the rest of the code after the Goto, you need to re-design that code as Goto may not always do that, not to mention it is a horrible programming practice.

-Ray

Hello Bob,

Using Writeln() to try and figure out focus events is not going to work as WriteLn() is going to take the focus and cause focus events. I use FileWrite() and/or @Msg() as neither of those cause focus events.

-Ray

Quote:


Putting the WriteLN() before the ThrowFocus() will also cause some focus issues if the Window is not already open. The most reliable way to debug with Writeln() is to have it open by writing something to it, on an event that you are not testing, Such as having a command button write out some piece of data. Then leave that window open and out of the way, Do not minimize it. When it is open other WriteLn() calls do not move focus to the WriteLn() window, which is actually called the "Slate" if you wanted to know. But again there are better ways to debug focus events then to use WriteLn().

-Ray