You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
INAppStoreWindow draws the titleBarView on top of the standard title bar text. This prevents a document-based application from correctly showing the document name in the titlebar. This issue can be visualized by inserting:
in the -windowControllerDidLoadNib: method of Document.m in the SampleDocumentApp. The original title becomes visible when the titleBarView is moved downwards revealing the original title.
The text was updated successfully, but these errors were encountered:
just a quick note: this only affects the visibility of the document name. Version controls as well as the path control & document icon show up correctly. UI also works as expected.
nsThemedFrame draws the title into its background in _drawTitleStringIn:. this is private api.
This is a known issue. We put the title bar view over the theme frame's background, so the default title won't be visible. Only way to solve this is to draw the title manually into the view. This doesn't affect the path control and other widgets because they are placed above the title bar view. I initially didn't plan on having INAppStoreWindow supporting titles, but I suppose they do make sense for document based apps.
I'll implement title drawing if I have some free time. In the meanwhile, if this is an urgent need then you may find it quicker to implement yourself :) If you do, a pull request would be much appreciated!
INAppStoreWindow draws the titleBarView on top of the standard title bar text. This prevents a document-based application from correctly showing the document name in the titlebar. This issue can be visualized by inserting:
in the -windowControllerDidLoadNib: method of Document.m in the SampleDocumentApp. The original title becomes visible when the titleBarView is moved downwards revealing the original title.
The text was updated successfully, but these errors were encountered: