Printable View
Is this a problem within VB6?
During debugging steps most of the time when I hover the mouse over a variable it shows the contents however on other occasions it does not show the contents but there are no errors or other obvious reasons why it doesn't show the contents.
I have seen this, but I always assume it means I have screwed up worse than originally thought...
That's usually the reason. That is not the reason in my case however since it does show the contents most of the time but other times it does not even though no code changes or different paths are in in effect - same code - same execution path but not showing contents.
Your previous thread about this same problem is still unresolved! :p
Wow, must really be driving him crazy then.
My answer was 95% facetious anyway, I often will just create message boxes to show what is in each variable anyway when I get my wires crossed.
why not copy that variable and paste in watch window during debug .you will get all you want . it is always efficient .Quote:
During debugging steps most of the time when I hover the mouse over a variable it shows the contents however on other occasions it does not show the contents but there are no errors or other obvious reasons why it doesn't show the contents.
LOL, absolutely forgot all about that one.Quote:
Originally Posted by Bonnie West
VB6 and earlier always did this. i just CTRL+G to debug and print it by hand or do an 'add watch'. this is normal behavior for the IDE. don't worry about it. classic VB still has one of the greatest debug environments you will see
JMS
Yes, I've experienced this, too, from time to time.
The Watch approach is fool-proof, but still, hovering is so convenient.
Here are 2 possible reasons the hover may not work ..
- If you've typed something, and then try to hover, you may not get a tool-tip.
Perhaps pressing F8, to advance 1 line, will reinstate hover.- Some objects, such as LB1.ListCount (ie, a ListBox), may not support hover.
Can you recall what sort of object/variable was giving you a problem?
Spoo
An array variable after I did a splitQuote:
Originally Posted by Spoo
a = Split(TextString, ":")
.......... for example it didn't show the contents of a(0), a(1), etc but most of the time it does
A listbox entry
List1.List(n) didn't show but most of the time it does
...but VB never shows the contents for an array of listboxes like this
List1(m).List(n)
On this particular situation it didn't show the contents for anything I was hovering...
Strings, Integers, and all the above.
When I left the source code (ie removed focus) and looked at something else then went back to to source code (ie gave focus back) it worked.
I have not simulated your example today, and have not been in the IDE for some time.
Notwithstanding that, my recollections may be handy.
In the past, when expected Tooltip info was not appearing, I would discover a wee bit later that there was an error (bug) in my program.
As you know -
- some errors are alerted immediately
- some errors are revealed when you run the source code
- some errors are revealed when you try to make the EXE
(The following will refer to 'VB' as if it is a person, or an intelligent computer.)
Thus this means that whilst you are writing/browsing code, VB may be slightly aware of some potential problem, but it ain't going to say anything. But what might occur is an interference in it's ability to generate some of those Tooltips (It is distracted).
So when I notice that lack of expected Tooltips, I compile the program, and fix whatever is troubling VB
When I say, I compile the program, I do not mean make the EXE.
I just run the source code, but with full compile.
There is another benefit in doing that (run with full compile) every time you run the program. It will help avoid the situation where you code furiously for a couple of days, and then try to make an EXE. What can happen is, you are confronted with a few errors, that are difficult to solve because you might have coded the error yesterday, and cannot recall (work out) which of all your code changes might have caused the error. Whereas if you could have been alerted to the error within minutes of creating it, 'blind Freddy' could solve it.
An easy trick to running with full compile, is to always run your code by holding down the ALT key and press fsrf (File Save Run Fullcompile).
If you always do this (I have been doing it for years) -
- Your Tooltips may return
- It is easier to solve bugs
- You won't get held up when you decide to make an EXE
I will accept donations (even if it only solves the latter two points)
JMS
This example does not surprise me.Quote:
Originally Posted by jmsrickland
However, I am surprised that you say "most of the time it does"
I would be surprised if it ever does !!
If the array has 20 components, are you saying that the tool-tip comes back
with 20 rows of text? With all due respect, I cannot imagine such a result.
The only way I can think of to find the components of an array is to look in
the Locals Window and expand the array by clicking on the "+"
Spoo
I didn't know it was called tool-tip when you view the contents of a variable by hovering the mouse; I mean I know it called tool-tip when you hover the mouse over a menu item or a button on a tool bar but not when you hover the mouse over a common variable as I pointed out previously. Oh, well, learn something everyday.Quote:
Originally Posted by Spoo
As to you question, I am saying yes if the array had 20 components then it would show the contents of each component like in a(0), a(1), ......... ,a(19) but only one at a time. If I hover over a(0) it shows the contents of a(0) only then if I hover over a(1) it shows the contents of a(1) only. This is common and most of the time I don't have a problem unless there is a pending error that needs to be resolved then It wont show any contents for any variable. Only once in awhile does it not show the contents even though there are no outstanding errors. Did you see where I stated that if I move the focus to another view, like another application running then I move the focus back to the code it will then show the contents of the variables.
JMS
First, the easy bit ..
Yes, but I was trying to focus on the first issue only.Quote:
Did you see where I stated that if I move the focus to another view, like another application running then I move the focus back to the code it will then show the contents of the variables.
Further, I was a little confused by the action that you were describing,
and hadn't really formulated a reply .. sorry, still haven't :(
As for this part ,,
,, I was, perhaps, using the term "tool-tip" somewhat loosely. I meantQuote:
I didn't know it was called tool-tip when you view the contents of a variable by hovering the mouse; I mean I know it called tool-tip when you hover the mouse over a menu item or a button on a tool bar but not when you hover the mouse over a common variable as I pointed out previously. Oh, well, learn something everyday.
the little light yellow box that appears, which kinda looks like a tool-tip.
OK, now for the real issue ,,,
Could you possibly post a screen-shot of when this does work for you.Quote:
As to you question, I am saying yes if the array had 20 components then it would show the contents of each component like in a(0), a(1), ......... ,a(19) but only one at a time. If I hover over a(0) it shows the contents of a(0) only then if I hover over a(1) it shows the contents of a(1) only.
Look's like it's time for me to learn something new .. ;)
Spoo
Now it does not work at any time. Every time I run my projects in the IDE mouse over any variable or anything does not show contents. Before it was just once in a while and it wasn't a big deal but now it is getting quite aggravating as I can't see any contents of any variable.Quote:
Originally Posted by Spoo
Have you tried my
Alt fsrf
to force all errors to be notified ?
JMS
Not working at all ,,, yikes.
Forgive me for asking an apparently obvious question, but were you
at a break-point when you most recently tried to hover?
Spoo
If my Alt fsrf does not help, I could tell you a story about what happened to me a few years ago.
Have you noticed any other minor irritations with VB6 IDE ?
I cannot recall how many months this happened over, but my IDE started deteriorating (things not working, etc)
I finally decided that MS's disdain for VB6 (discarded by them like a used condom), meant they were not testing their OS updates, to ensure that they did not impact the VB6 IDE.
I don't recall (I am old) whether I had to re-install the OS ?
I have a vague recollection that my attempts to re-install VB6 were not a piece of cake, so I may have had to reinstall the OS as well.
But what I do recall was, I switched off automatic OS updates, to never darken my doorstep again.
I have never experienced the same problem again.
Yes, it is always at a breakpoint. Not only the line I stop on but all variables all the time. This is now going on day by day. I close out the project and the next day I open it up again run it til it stops on either a break point or a Stop statement. No change. Still no contents shows. Maybe I'll reinstall VB6 and see what that does.Quote:
Originally Posted by Spoo
What is Alt fsrf?Quote:
Originally Posted by Bobbles
I have never had auto updates on.Quote:
Originally Posted by Bobbles
Have you noticed any other minor irritations with VB6 IDE ?
No. My VB IDE appears to work normally except for this one situation.
JMS
I'm not sure how a Stop would work (I don't use that statement),
and it appears that you were on to the obvious (ie, a break-point).
But, as a last ditch effort, maybe in an "early" sub (FormLoad or maybe
one call lower), add, for test purposes, 2 lines reading ,,,
Natch, this will induce a "crash", but at least it is a breakpoint !!Code:txt = "Hello World"
b = b / 0
Do you get anything when you hover over txt?
Spoo
i have found for years, this happens regularly, in both vb and VBA, often fixed by a reboot of the computer (i seldom shut mine down), possibly some memory or resources isssue
See my post 11 aboveQuote:
Originally Posted by jmsrickland
It is just the keyboard shortcuts for the menu items -
Saving your current page ALT fs (ALT File Save)
And ALT rf (ALT Run Fullcompile)
And you can do them in one ALT fsrf
In post 11 I explained that forcing VB to confront all errors, gets them out of the way, and stops VB being distracted to the point that it is not bothering to show our desired ToolTips.
I have a similar problems when I have large proyects with classes and usercontrol objects, form subclassings, etc.
The problems is, that in aditional to the exposed in this thread, when you are writing the name of an known object, and type the final DOT VB IDE must show that *HELP BOX* with all members of the object (properties, methods, etc.), well, it is DRAWED but 0.2 seconds after it dissapear, making impossible to read it, or to use it.
It happens always, lets say, the fail is not sensitive to "if you are debugging" or "you just opened the project".
Sometimes gets quite frustrating because in big project sometimes I don't remember the name of a custom method and I needs to go all in deep to browse the class or usercontrol to see it.
It affects every help box that pop ups automatic, independently of the object class just wrote.
anyone has clues why it happens?