Mike Lischke

Upgraded to Yosemite and encountering this problem here too now. Is there any fix in sight? If not I might have to stop using this otherwise nice control.

This is how WebKit "solved" the issue: http://trac.webkit.org/changeset/170980/trunk/Source/WebKit/mac/WebCoreSupport/WebInspectorClient.mm I tried adding this to INAppStoreWindow.m: @interface NSView (AppKitDetails) - (void)_addKnownSubview: (NSView *)subview; - (void)_addKnownSubview:(NSView *)aView positioned:(NSWindowOrderingMode)place relativeTo:(NSView *)otherView; @end if ([self.themeFrameView...

> If you only intent to have a custom title bar height on Yosemite: > My current work-around is to check if it's running on Yosemite at runtime. If not,...

@raffael This is pretty cool. Thanks for that. What about adding something that can be used to switch between WAYWindow and INAppStoreWindow depending on the app kit we are running...

Well, it's not that ugly and works pretty well (after applying my changes to avoid WAYWindow to crash). I recommend everybody here to try this out, even though there's still...

utkarshagutpa, pls don't hijack issues for support questions. You could open an own issue or ask on Stackoverflow. WAYAppStoreWindow automatically handles compatibility by replacing the actual class that is instantiated...

This makes no sense, really. A parse tree is a superset of an AST. You have all the info, which is contained in an AST already in your parse tree....

Fragment rules also produce weird behavior when used in a parser. I don't remember many details, as I avoid that scenario by habit already for a long time. However it...

Interesting indeed. I mentioned this as a possible optimisation a few times in the past, when people asked for faster startup times.

Someone once mentioned also web services, where a parser is instantiated for each web request, which means currently it always starts in cold state.