any help coming soon on the bogus AVPlayerOutputPushDelegate warning ???

I think this is probably an Apple issue ...

Screen Shot 2014-09-05 at 10.35.06 AM.png

but ... it makes this useless. Having a false positive in every class is a bummer. Tends to encourage leniency : i thrive on green summary indicators and all i am getting is this for no reason at all.

Screen Shot 2014-09-05 at 10.35.13 AM.png

Upvoting a bug report that gets pushed back to the very bottom of the backlog wont help. Could you intervene with the product owner so that this bogus can be removed from my sight and render the summary box useful again ? pleaaaase ....

10 comments
Comment actions Permalink

While it's not fixed, you can suppress or disable this inspection (see the screenshot).



Attachment(s):
Screen Shot 2014-09-08 at 15.47.42.png
0
Comment actions Permalink

i dont know how to obtain that menu in context ... but it does not really matter : i probably have 400+ classes (files) in one project alone where this bogus shows up at the moment. The inspection is useful (for my own mistakes) and i keep it around for that purpose. Working around apple framework bugs , i can live with. But working around IDE bugs is a bit hard to take. FIX the goddam thing.

How about one or two cleanup sprints to get rid of long-time annoyances like this ? Would JetBrains allow IntelliJ to become as crappy as AppCode is becoming ?  Here are a few examples:

  • losing the index every 10 minutes of work, forcing me to close and reopen the project
  • couplings between projects at the file system level !!!!!!
  • autocompletion so slow that i can type completely the line of code before any suggestion is offered.
  • beachballing every 2 minutes for GC
  • etc etc etc

In spite of all this, this product has the JetBrains finesse and could be a phenomenal product. As it stands, i get the feeling that you are more concerned about piling-up more and more 'third level' features that you forget the basic thing : the usability is degenerating at every build that comes out.

0
Comment actions Permalink

Press the right arrow to get this menu.
If GC is running too often, try to increase Xmx for AppCode and enable the memory indicator.

What's the number of this issue in YouTrack?

0
Comment actions Permalink

Avoiding the issue again. Right now i am running at 3Gb. Point is, cant you force a GC at convenient places (from a workflow standpoint). For example, after a build, a clean, a global search, etc ... the extra second will hardly be noticed, but at least users wont get the beach ball when editing code, where it is the most noticeable AND irritating.

ps: press the right arrow ? when, how ? if i hover over the highlighted import or click into it, pressing the right arrow just moves the cursor.

0
Comment actions Permalink

opt+enter, then right arrow

0
Comment actions Permalink

opt-enter , right arrow works well on other inspection results in the same file, but does nothing on this one. Did I mention "bogus" in the title of the discussion ?

0
Comment actions Permalink

It should work. After you select "suppress", file should look like this:

 
#pragma clang diagnostic push
#pragma ide diagnostic ignored "NotVisibleClass"
#import "i.h"
i* x;
#pragma clang diagnostic pop
0
Comment actions Permalink

opt-enter right arrow just moves the cursor on that, ie no menus are appearing. another bug ? not really, it is just the outcome of another but imho ... just fix the bogus so you dont have to mess with inspections.

and yes, pragma'ing out the inspection removes the stupid warning.   400+ files.  

ps : should it not be 'pragma ide diagnostic push/pop' ?  because clang never even blinks at these... ie no compile warnings.

0
Comment actions Permalink

Could you please create issue in YouTrack or point me to existing one?

0

Please sign in to leave a comment.