I noticed this problem just this morning after spending many hundred hours debugging my app for the past few months when everything worked just fine.
This is the setup which is hardly unusual. There is a function in a prg file and a Click method that calls it. There are a couple of print statements like:
"coimng out of the function: "+numeric_id
and such in the function(s) and one in the Click method. All output is character strings. The button is clicked many times during the debug.
I get only one line of output out of the function but the rest of it is overlapping this first line no matter where it is coming from. The ACTIVATE SCREEN statements are everywhere. All print statements are " " not " " !!!
I figured the continuousScroll property should be responsible for it. It is set to .T. (default). I tried to change it to .F. to see what would happen--it fell back to .T. next time I brought the screen up.
My debugging (essentially in the home run) is paralized.
I am sure it is something with the screen parameters I do not see. Please help.
Thanks.
_screen.ContinuousScroll problem
chrisjohnson
tjanke
I expected the output from DEBUGOUT on the screen _VFP.
Well, as has been pointed out to you many times before, just because this is what you expect, this does not mean that this is how the product works. You need to educate yourself instead of making ( erroneous ) assumptions and then complaining when they turn out to be wrong.
It is a totally inconvenient idea for me since I am using the debugger as a last resort
That is too bad. The debugger is a very powerful tool and can save you tons of debugging time if you learn how to use it.
Toddap
Brian thanks,
No I haven't. It is also in regards to Marcia's post. I am in a big hurry now, leaving for the airport in 10 mins. Will be back in a week and only then will be able to read any further developments.
She is talking apparently about the debug window. If this is true, I haven't checked it. I expected the output from DEBUGOUT on the screen _VFP.
It is a totally inconvenient idea for me since I am using the debugger as a last resort--it clatters already very crowded space. Tracing variables does not save time, breakpoints are too cumbersome. It is just my preference to use and statements inserted into the code to snatch the variables.
Well, anyway, as always I will appreciate the suggestions but I would really prefer if someone could figure out why I got in trouble with the " " statement.
Thanks.
Venkat Sathyamurthy
The Debugger is an invaluable tool in getting VFP code working. Learning to use it effectively will save you hours and hours of time.
That said, if you insist on avoiding it, you'll probably find WAIT WINDOW statements easier to work with in debugging than and .
Tamar
Patrick Antonioli
I have no idea what you are talking about either. The statement:
DEBUGOUT "looking for ", m.numeric_id
produced no output whatsoever, NONE.
Obviously, you did not read the topic in the on-line help that I referred you to. Since it is obviously too dificult for you to look it up yourself, I will post the topic here for your viewing pleasure:
Parameters
Specifies one or more expressions to evaluate and display in the Debug Output window. You can specify multiple expressions of different types.
If the expression you specify is an object or object reference, Visual FoxPro automatically converts it to the string, "(Object)", to provide the character equivalent. In the following example, the _VFP system variable is returned as "(Object)" and passed to DEBUGOUT:
Remarks
Use DEBUGOUT to identify when a procedure or function is executed. For example, you can place DEBUGOUT at the beginning of a procedure to display a message in the Debug Output window, indicating that the procedure has begun executing.
You can abbreviate DEBUGOUT to a minimum of only six characters, which distinguishes it from the DEBUG command.
When you pass multiple expressions, a comma appears as a space. A carriage return line feed (CRLF) is added at the end of the line.
DEBUGOUT is disregarded in applications you distribute.
bc020400363
And you've made my point also.
If you think there is a bug, you should file a bug report with repro steps. That's the recommended route when you run into an issue that you want fixed.
DiegoV
I just checked this app on another machine--it is surreal: the same problem that started bugging me this morning is here too! It means that the problem is in my code as they say but what
I haven't made any unusual major changes since yesterday night when everything worked just fine. Bizarre.
Rebecca Karma
I am back.
When the code breaks down the only way to find out where it occured is to invoke the debugger and I use it every time in order to locate a problem. However, I do not do step by step tracing variables EXCEPT in cases of extremely convoluted loopy blocks when the problem gets elusive. One of the reasons I do not do it is the limited amount of space on the screen. It is more convenient for me to use and to examine the execution dynamics.
DEBUGOUT of course works. The debug output window displays all needed output but my original question remains unanswered.
Why did I get this weird behavior for " " operator all of a sudden
I have a clue of sorts but it does not help me to fix the problem. Right before it happened first time my wireless keyboard batteries failed--they were too low to connect. The same thing happened to the mouse batteries. I noticed that the windows on the screen became jumpy. When I moved the mouse they would not stay still but jump erratically all over the screen. It took me about 5 min to figure out what was wrong. I think the mouse sent some errant code somewhere and changed an environment variable or two but so far I haven't been able to find out which one.
Thomas Nowak
Well how much time have you saved by DEBUGGING your Debugging There is some easy ways to make the DEBUG work fast, easy, and save you this kind of aggravation.
READ about Set Step On and RESUME in the help, use it in your code when you want to start the process, and again at the end of long functions that are not an issue. That way the debugger starts when it needs to, and you can speed thru code that works until you get to the next section.
Use the tools Microsoft invented for the purpose at hand. In order to do this though you must learn the Basics first.
m_shane_tx
"I have no idea what you are talking about"
I have no idea what you are talking about either. The statement:
DEBUGOUT "looking for ", m.numeric_id
produced no output whatsoever, NONE.
But thanks for the answer anyway.
Mougenot
Hi Brian
I am afraid that you did get a reply from AlexBB to your post. Unfortunately it added no value to discussion and I had to delete it. Here is the main text of the deletion message that I posted to him, so that everyone will know what I am doing. If anyone objects, then please let me know publicly. I include some of his less offensive remarkls so that you can judge the tone of the message.
-- Begin --
I have warned you before about being aggressive in your replies on the forum. Your fitrst message back starts again:
>> I challenge you. IT IS A LIE.
If that is not aggressive I don’t know what it is
>>Do not make things up! You might be in a fog of dreaming or something.
This is a personal remark and has no relevance to anything. It is gratuitously offensive
>>I do not need your inapparopriate sermon
And we do not need your inappropriate remarks and insults.
>> All this infantile display of red color reminds me of a female baboon running around displaying their red bottom to attract attention.
And this is not an offensive remark
>> I will not accept anything short of a direct answer to the question I've posted.
I don’t care what you will accept. You ask for help then insult and ignore those who give it. Please take your postings elsewhere
You are impatient, aggressive and offensive. It will not be tolerated here and your posts will, unless you tone things down, simply be deleted. You can complain all you like about 'censorship' and 'suppression' and it will do you no good because you have done this too often in too many places.
Either behave nicely to people or take your rantings elsewhere.
-- End --
amal02
If you have an idea to improve the product, you should use product feedback. Venting your dissatisfaction merely to vent your dissatisfaction goes against the purpose of this forum, which is to exchange ideas and help each other when we get stuck. The people who frequent this forum are people who have bought into the product and prefer to use it over any competitors product. That's not to say that they feel the product is not without its flaws.
Over the last 6 months I've observed that you come here to commiserate. There are churches and help groups for that. The reason people choose to interact with you is because they want to help you be productive in your software development--there is no other reason. You avoid following people helpful suggestions because it takes away justifications to be miserable. If Foxpro makes you miserable and/or unproductive, then you should spend your valuable energy towards other things in life.
Brian
noel 55
I get only one line of output out of the function but the rest of it is overlapping this first line no matter where it is coming from. The ACTIVATE SCREEN statements are everywhere. All print statements are " " not " " !!!
I have no idea what you are talking about. If you are trying to get output while debugging your application, the best way to do so is by using the DEBUGOUT command.
You can read details of how to use it in the on-line help.
Matt Hair