How to view errors/toggle log window in pine script editor? - debugging

Maybe a stupid question. I'm new to TradingView and pine script, so please bear with me if there's some simple way to do this...
I figured out how to copy and modify a script from the library. At first, I could see a tiny edge of a window at the bottom of the script. When I saved or attempted to add the script to the chart, the window showed whether the script processed or had errors.
Now, though, I seem to have "lost" that window. How can I display that window? Also, once displayed, how can I make it larger?
Edit:
Here's a screenshot of the bottom of my editor -

Right-clicking on the console (errors) window showed a little pop-up saying:
While my cursor is in the editor window, holding Ctrl (or Cmd on a Mac) plus the backtick key toggles the console window open and closed.
Now, I can see the console log window whether I have errors or not.

you can show/hide the pane with pine scripts with the "_" icon on the right side:
show
hide
On the rigt side next to the "_" icon you can toggle/maximize the pine script window.

Add any error to your script and save the script.
In the lower left corner, you will see a small gray triangle.
Drag it up with the mouse.

The "Show console" was never visible in my browser. Only the "Toggle console", which did not do anything for me.
I tried a different browser and the console showed well. So I figure it was the browser I was using "Firefox".
So, I re-started Firefox, by going to Un-install Programs in Windows, clicking "Remove program", in front of the Firefox logo, which gave me the choice to restart Firefox. I did took that choice and this fixed the problem for me. I hope it helps others.

On Firefox, it may bug and never show it even with the shortcuts (because it becomes a tiny single-line that can't be dragged at the bottom of the page).
In order to fix it without uninstalling firefox: clean the site data for the domain.

Related

Inspecting a browser's Developer Tools [duplicate]

According to Google this can be accomplished by visiting "chrome-devtools://devtools/devtools.html" in Chrome but now visiting that page in the stable version of Chrome (or Canary), just shows a 99% stripped version of the inspector.
To reiterate my "title" this is in reference to "inspecting" the inspector. Not just inspecting a normal webpage.
And while I don't think it's necessary to know to resolve the issue, I"m inspecting the inspector so I can style it as discussed by Paul Irish and here: https://darcyclarke.me/articles/development/skin-your-chrome-inspector/
Follow these easy steps!
Press Command+Option+i (Ctrl+Shift+i on Windows) to open DevTools.
Make sure that the developer tools are undocked into a new window. You may have to undock from the menu:
Press Command+Option+i again on this new window.
That will open the DevTools on the DevTools.
You can redock the page's DevTools if you want.
If it's not already, select Elements — it's the first icon at the top of the inspector.
A little beyond the scope of your question, but still valid in understanding why you're experiencing your problem can be found by understanding how Chrome Developer Tools: Remote Debugging works.
Open chrome://inspect
Open the inspector on that page (cmd + alt + i)
Scroll to the bottom of the page, under the Other section click the inspect link
The URL in the Other section should look something like this:
chrome-devtools://devtools/devtools.html?docked=true&dockSide=bottom&toolbarColor=rgba(230,230,230,1…
EDIT: they've fancied up the chrome:inspect page so you have to click the Other header on the left to get this to work now.
I just got this to work. The key is that you have to start up chrome in 'Remote Debugging' mode.
on OSX, open an terminal window and execute the following:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222
On windows, Its
chrome.exe --remote-debugging-port=9222
(better windows instructions can be found here: https://developers.google.com/chrome-developer-tools/docs/remote-debugging#remote)
This will start up an instance of chrome, that will send debugging messages to a local webserver on port 9222.
If you access that web service, it will give you the ability to use the inspector to inspect any chrome window that is running. Since we want to inspect the inspector, we need to start an inspector window first (As above Use the shortcut keys; for Mac it's Command+option+i.)
Now, go ahead and navigate to
http://localhost:9222
It will present you with a list of windows to display in the debugger. Select the window that starts with "Developer Tools" and you'll be able to inspect the css for the inspector.
Its hard to see in the image below, but on the left I have my chrome window pointing at the remote debugger, highlighting one of the toolbar labels. On the right you see it lit up with the tooltip just as if we were debugging a web page.
A few weeks ago somebody pointed this out in stackoverflow's "javscript" chatroom. First, and very importantly, make sure the inspector is undocked from your browser window. Then it's just a matter of opening a inspector window and then inspecting that window. In windows it's CtrlShiftI (Edit: I said, CtrlShiftI but that brings up the console inspecting the console... you should be able to navigate back and forth.) for the keyboard shortcut. (Other keyboard combos for other options and OSes here and here.) Just do that twice and you're good.
Edit: ok, you're probably confused as to undock the window. This is what you'd click if it's docked..
Edit II: I'm not quite sure why you can't inspect. JDavis's answer is consistent with the Google Docs for Apple computers. If you're using Linux it appears to be the same as Windows. You supposed to hit the inspector key combination while the focus is over the inspector window.

Visual Studio Yellow Tooltip stuck on screen

I'm running VS2013 Professional on Windows 7 x64 and often finding that, after a debug session, the yellow tooltips from the debugger don't go away and stay on the screen on top of other windows. For example, the image attached shows a debug tooltip now also showing on top of me posting this question.
I am able to hide it temporarily by pressing Win + d to show the desktop, but as soon as I open / navigate to any window, the tooltip is right back.
The only way I've been able to get rid of these tooltips has been to close and re-open my Visual Studio. Any thoughts about what else I could do?
Try sending the WM_CLOSE message to the tooltip window.
I had hoped to be able to do that with Spy++, but alas you can't send messages from that.
I downloaded SendMessage from StephansTools, this then lets me use the cross hair to select the offending tooltip window and then send the WM_CLOSE message to it.
Caveat: This only seems to work in some circumstances. It's worth a try but may not work every time.
On your screenshot, the tooltip is "this is the next statement that will be executed". This tooltip appears when you hover over a yellow arrow to the left of the code while stepping in debugger (there must be no breakpoint on the current line).
It's quite likely that when the tooltip is stuck, you can un-stuck it by howering over that yellow arrow again, then moving mouse cursor away from it.
As for permanent solution to the problem, I would blame third-party applications that install hooks. Try to temporarily disable whatever such software you have and see if it helps. If you can't figure the exact repro to get the problem, you can simply close any other software you can and do your debugging for a while.
Some typical examples of hooking software:
Input assistance (voice to text, ...)
Automatic keyboard layout correction
Dictionary and language translation
Anything that creates new buttons in other programs
Screenshot software

Tmux pane switch causes displayed info to change

Has anyone any idea what is going on here. I'm not 100% how to word this problem so my google searching has found nothing so far.
I am using terminal on Mac OSX and just started using Tmux. When I fire up a session I get the first screen shot, then when I create a new pane for side by side development with <C-b>% a new pane opens but the old one gets corrupted in some way. See second image.
When I jump back to the first pane with <C-b>LeftArrow it returns to show the correct info, but then anything in the right pane gets jumbled.
Any ideas?
UPDATE: When I edit files in vim in the right pane (for example) the text appears in the left pane when I hit return and move to the next line. The colouring suggested it is using the wrong width for the screen?

Clicking on issue ellipsis link just shows a lightbulb, why?

Clicking on the ellipsis link next to the issue, e.g.
I get a little light-bulb icon with an x
in the lower right hand side of my window. If I click on a link for duplicated code I get a similar x icon. Why is this? How do I fix this?
This turned out to be a browser problem. I refreshed Firefox and the lightbulb icon now expands to a window showing the correct information. Refreshing Firefox also fixed a persistent "Still Working..." problem where no menus, etc. were available after I installed SonarQube on a new server.

Disable " Stay on top" features on photoshop CS2

Photoshop CS2 always stay on top, even when I click another app from the windows taskbar (right of the start button).
It's completly annoying me. Always need minimized, click the other app, reclick again on photoshop, re-reminimized.
I only have 1 screen at work so I can't let photoshop on one screen and work with the other app on the other screen.
I look in all photoshop menu, find nothing
I googled the problem, and find a adobe page explain this problem is a "feature".
I only want photoshop cs2 work all other app on windows and loose focus, let new app appear on top.
Thank you.
I had this problem and somehow solved it. But my solution may be just as fickle as why the problem occurs in the first place. But here's what I did:
On the layers palette (F7) I clicked on the small arrow just below the close "X" button, on the right. Then I selected "Pallete Options"
Didn't change any options but just clicked OK.
Now the entire window remained on top, not just the palettes. So I restarted Photoshop and it seemed to fix the issue.
I found that if you open up "edit > preferences > Memory & Image Cache" and set your memory usage up then it will fix it. I am on a Windows 10.
See this post:
https://www.reddit.com/r/photoshop/comments/35lmtu/photoshop_keeps_putting_itself_in_front_of_my/
Go to Edit > Preferences > File Handling > Uncheck Enable Version Cue Workgroup File Management
I literally JUST found this on accident and fixed it after having issues with all my toolbars being hidden behind stuff, and not being able to minimize without clicking on the PS window first etc. Seems to have worked!
Topmost Toggle will help you: http://www.softpedia.com/get/Desktop-Enhancements/Other-Desktop-Enhancements/TopmostToggle.shtml
Works for CS2 even in Win8
Try Topmost Toggle. Works on Window 7, Window 8 and even Windows 8.1. I use it for disabling Photoshop CS2 and when Firefox bug out. Works like a charm and it's pretty easy to use:
Download and extract Topmost Toggle
Run the program - you will see that it minimize on tray
Ctr + Right click on your program and click
Enjoy!
Big thanks to user2761076
I am having same issue with CS2 on Windows 7 64 bit. To work around, I hit tab on keyboard when photoshop window is active, that makes all pallets invisible, then I can switch to any window I need to work on.
As per this article there seem to be issue with Microsoft update https://forums.adobe.com/thread/2142314

Resources