There is no red error text in pine editor - editor

I add some error in my pine editor,but there is no red error text display which it should.
It works fine severl hours ago,but now it doesn't.
I tried to restart tradingview,but error still

Related

Thread1: Breakpoint 1.4 [duplicate]

I am following the Stanford University iOS development course on iTunes U.
In one of the demos (that I have been trying to follow), there is this code that loads the property list from an NSURL and returns it as NSMutableDictionary.
-(NSMutableDictionary *) words
{
NSURL *wordsURL=[NSURL URLWithString:#"http://cs193p.stanford.edu/vocabwords.txt"];
words=[[NSMutableDictionary dictionaryWithContentsOfURL:wordsURL] retain];
return words;
}
The application is successfully built, but at runtime it gives the following error and gets stuck:
I can't figure out what the problem is. Can you please help?
You're stopped at a breakpoint. That's a debugging tool, not an error. See the blue arrow/tab in the left margin, where the line numbers are? Drag that away and drop it anywhere (you'll see a "poof") to remove it, then run your project again.
You can also deactivate all breakpoints by typing ⌘-Y, the key equivalent for the menu item Debug>Deactivate Breakpoints, or you can view all your breakpoints in the Breakpoint Navigator (hit ⌘-6).
When execution stops like this, you can continue from the breakpoint, either by typing continue at the debugger prompt in the Console:
(lldb) continue
Or hitting the "Play" button in the debugger controls. You can also type Control-⌘-Y, which is the equivalent for the menu item Debug>Continue.
This isn't an error. You just set a breakpoint (probably without knowing it).
Drag the little blue Chevron in the column at the left out of the way. You will see it disappear and go poof, and then you can rebuild your app and you should see it run properly.
Now, that said, I think there are some memory management mistakes in your code, but we can return to those later. ;-)
The program is stopping because you have a breakpoint.. That's the blue arrow on the left of the code. Right-click it and delete.

Why is print() text displaying in the middle of the console instead of the end?

In an instructional video I recently watched, entering print() in viewDidLoad() caused the print() text to appear at the end of the text displaying in the console. But when I run the same code, the text appears in the middle of the console (as in, additional text following the body of the print() text displays in the console--see screenshot for example). Here is the code I am referring to:
override fun viewDidLoad() {
super.viewDidLoad()
print("Hello World!")
}
screenshot of print() command displaying in the middle of the console instead of the end
Bug in Xcode 8: it will print stuff automatically in viewDidLoad, viewDidAppear, etc. You are printing your code in view did load, and Xcode will print logs after view did load, that is why it's in the middle.
They are likely using a different Xcode version. Xcode 8 is still in beta and they are printing a lot of different things into the console (especially if you have network requests). The runtime is hitting your print statement before printing some of these other statements.
If you're talking about the console being on the right side: see the two squared icons with a bar inside, highlighted in blue, in the lower right part of Xcode's window? Click on the left one: it will hide the properties panel and expand the console at full width.
If you're talking about the fact that "Hello World!" is in the middle of other text, that's because this other text is debug information that appeared at the same time as your print statement.

Xcode: How to temporarily hide yellow warnings from Issue Navigator

I'm working on a project (written by another developer...) with LOTS of yellow warnings.
During the build process, if there is a critical (red) error, the error keeps moving down beyond the bottom of the left pane, and it's always taking me some time until I can finally point the mouse at it and look at the error.
Is there a way of showing only the red (critical) errors?
Toggle the "!" button (Show only errors) at the bottom right corner of the Issues Navigator to hide Warnings (next to the results filter).
Go to the Project -> Your Project -> Search 'Warning'.
Then turn off warnings you don't want.
Xcode 11.7,
handle Apple Clang Warning Policies
image is more vivid.

playground message "number of times"

I was playing in swift playground. I get a funny message on the right side of the screen (10 times) and have trouble determining the meaning of it. it looks like this:
That message describes how many times that specific line/block of code was run on a single execution of the playground's simulator, which runs constantly in the background.
It indicate for loop iterations. you can check actual output in console by view->Show Assistant Editor->Show Assistant Editor.loops iteration appear printed as shown in Image

Error 1034: converting TLF text to MovieClip for fade in transition

I am trying to make text in my project fade in/out when a test button is pressed. I have gotten as far as writing the basics (I think so at least), however every time I try I click the test button, I get the following error message:
Error Message:
TypeError: Error #1034: Type Coercion failed: cannot convert fl.text::TLFTextField#2de22479 to flash.display.MovieClip. at Products_fla::Products_1/fader()
The code for the button is as follows:
Code:
test.addEventListener(MouseEvent.CLICK, fader);
//Function: fade text
function fader(apple) :void{
clear();
TransitionManager.start(Text.Rubens, {type:Fade, direction:Transition.IN, duration:9,easing:Strong.easeOut});
}
I've been searching for hours now, but I only found that code from a copy/paste from the Adobe website: http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/fl/transitions/Fade.html
P.S. This is my first time using stackoverflow (as I'm a newbie :) and any help will be greatly appreciated.
I believe in the end, I cached the TLF text as a bitmap on runtime, and then applied the alpha transition. This seemed to work. A bit stupid to be honest...

Resources