Board index » General » Ask a question
Tooltips?
Enter your message here, it may contain no more than 60000 characters.
[quote="Syrifina"]You will only get a prompt to view the error log if it recognizes that there was an error. I look at it this way: An error means that I made a mistake in coding it like missing info, nonexistent variables, wrong syntax, etc and BEM will give you an error warning (and log) to view the problem. An execution mistake means that I wanted a certain behavior to happen but it's doing something else. BEM is basically saying, "I'm doing what you told me; It may not be what you want, but this is what you told me to do" therefore there's no "error". Stuff like clicking at the wrong spot, doing stuff at the wrong time, not doing something because the "trigger" isn't there, etc. It just means you need to go back and take a look at the log and see how you can clarify what you are trying to do so that man and machine can be on the same page. You can view them manually on the main screen; not the "pop-up" edit/create mode. On the right side you can see information about macros like what is running, which line it's executing in real-time, what triggers are active, and links you can click on to view the error and execution logs. Again, you can only view the error log if it actually recognizes an error...so use the execution log if there isn't an error (log) available. That's why I generally script in visual elements where I can. If something isn't working I'll already have a good idea of where it is in the script and can refer to the execution log to tell me "why" it's doing what it's doing.[/quote]
[img] is OFF
[flash] is OFF
[url] is ON
Disable BBCode
Please click and drag the 2 correct statements to the right hand side.
2 correct statements
Chickens can talk
Fish can swim
Dogs have 4 legs
Elephants can fly
Please drag the options with the mouse to the correct list, to avoid automated registrations.
Statements 2 correct statements
Topic review - Tooltips?
Post subject: Re: Tooltips?
Posted: Wed Oct 20, 2021 9:33 am
Thank you for that.
The HTML window has worked perfectly for my debugging, allowing me to set up a HUD updating with variable changes.
Appreciate the advice there
The HTML window has worked perfectly for my debugging, allowing me to set up a HUD updating with variable changes. :)
You will only get a prompt to view the error log if it recognizes that there was an error.
I look at it this way: An error means that I made a mistake in coding it like missing info, nonexistent variables, wrong syntax, etc and BEM will give you an error warning (and log) to view the problem. An execution mistake means that I wanted a certain behavior to happen but it's doing something else. BEM is basically saying, "I'm doing what you told me; It may not be what you want, but this is what you told me to do" therefore there's no "error". Stuff like clicking at the wrong spot, doing stuff at the wrong time, not doing something because the "trigger" isn't there, etc. It just means you need to go back and take a look at the log and see how you can clarify what you are trying to do so that man and machine can be on the same page.
You can view them manually on the main screen; not the "pop-up" edit/create mode. On the right side you can see information about macros like what is running, which line it's executing in real-time, what triggers are active, and links you can click on to view the error and execution logs. Again, you can only view the error log if it actually recognizes an error...so use the execution log if there isn't an error (log) available.
That's why I generally script in visual elements where I can. If something isn't working I'll already have a good idea of where it is in the script and can refer to the execution log to tell me "why" it's doing what it's doing.
I've seen the log, but it only comes up when there has been execution issues, and havent worked out how to view it manually?
The idea of using the mouse as an indicator may work though, I'm normally a c# coder, so typically have access to debug console etc.
Depends on your script; I'll give you some tips though.
First there are logs you can check to see what happened and what went wrong, error and execution.
If you want it to display something along the way, I'd suggest using display html rather than message box. I think that's closer to what you're describing.
If the problem has to do with looking for something on the screen you can script in visual indicators; same for if you're looking at the error log but can't find where it's going wrong. For example anywhere you have look for or find a color, image, or pixel pattern - replace it (or add before) with "mouse.move" to that location. same for "click at color, image, pixel pattern, etc. That way if the mouse doesn't move to that location when it's supposed to, then you know that is the part of the script you need to look at.
Post subject: Tooltips?
Im wondering if there is any way to get tooltips to display at the cursor to assist with debugging where things aren't working correctly?
I have tried using window.displaymessage("my debug message","no") but as its continuing the box just gets hidden behind the window until I stop the script making it useless.