I'm using Xcode 6 (Version 6.1.1 (6A2008a)) and I find the dialog that usually pops up when you hover over a variable in Xcode (just before your breakpoint) incredibly useful.
However sometimes this dialog won't appear.
Is this a bug with Xcode or are there reasons why it sometimes won't appear?
I am using the same Xcode version.
Assuming:
You are not hovering on a property: self.myVar (does not work - not sure why!)
You are not hovering on a variable of an instance: cell.myImageView. Hover will only work for cell here.
You are not clicked in on the variable - happens by mistake sometimes with the trackpad.
I think it is bug with some peculiar behavior. It seems to happen when you open and close the Navigator or Utilities pane - which is common during debugging. Here is how I was able to replicate it:
Set a breakpoint
Run
Hover on a variable that works
Close and open Navigator or Utilities pane
Hover on that same variable - it will not work.
This seems to work once. In order to replicate it, you have to run again.
Having said that, if it is not working; if you hover above the variable sideways or up/down or, move away and come back to the variable, it usually will display the variable value.
But i agree, the erratic nature is annoying.
Hope this helps.
Related
When you open the file menu (or any other menu in the menu bar), it looks something like the attached image.
MacOS file menu
In Windows, when you select the command you want, the menu instantly disappears and the action is instantly performed. In MacOS, however, the command you chose blinks, the window fades out, and then the action is performed.
I know there are commands and settings to disable certain animations in MacOS, but I can't seem to find one relating to this yet.
This is one of my major pet peeves with MacOS and I'd appreciate any help. It might be the case that I'm making a huge deal out of this when it's not as such, but it does get annoying sometimes and slows down my workflow.
Thanks!
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.
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
Whenever I try to run my project (in Xcode 4.6.3), it launces the iPhone Sim., the 'screen' on it goes black, and Xcode displays this same exact thing every time
If anything else such as code of the XIB's I'm using**, I would be more than happy to provide those. Thanks!!
**XIB's I'm using ---- whenever I try to link a button to a view controller (in a .storyboard file) it won't link. I two finger click (right click) and drag, usually, the view controller I want to link will be highlighted in blue, and then I am able to just tap it in the Sim., and it will do a quick animation to the next VC. But it the VC I'm trying to link it doesn't even get highlighted. Once again, I'm running Xcode 4.6.3. Thanks again!!
The picture in your comment says that it crashes when trying to set a key (admissionsButton) for your ViewController object that doesn't exist. This could happen if you deleted a property in code but the IB link still remained. If you open up IB and go to your view controller, expand the utilities window (the right sidebar) and then go to the far right option that shows connections. If there is something there that says admissionsButton, try deleting it.
In order to give you more help than that, I would need to see a more detailed log of where the crash happens.
That message could be for anything during the execution of your code. I would use breakpoints from the moment of launch and step through it using the debugger window.
Xcode seems to be doing something annoying today.
I like editing my source code so that I'm typing roughly in the vertical center of my Xcode window. I don't like typing near the bottom or the top of the window as it hides code right before or right after the code I'm busy editing.
Lately, while editing an implementation file, Xcode has a habit of scrolling the text so that I'm editing close to the bottom of the window. This scrolling is triggered every time any code completion takes place.
Has anyone seen this before? If so, how can I turn it off or is it simply a bug?
You may be encountering a bug where one text view scrolls unexpectedly when a second window is open on the same file. Make sure that the file is not open in any other windows if this is what's happening.
I also noticed this in Xcode 5 and earlier. It appears that Apple has fixed this in Xcode 6. I am running Xcode 6.4 and no longer see the issue.