Post not yet marked as solved
Thanks for the link.But I think that you have misunderstood my question. I am implementing my own UIPresentationController and I have to / should send these messages from this controller, too.
Post not yet marked as solved
I already filed a bug report.I have a few problems:I do not know under which conditions presentationControllerDidAttemptToDismiss: and presentationControllerShouldDismiss: are sent. So, I also do not know what to do with them. I have found presentationControllerDidAttemptToDismiss: in a demo program from Apple somewhere and did a similar implementation in my app but actually I do not know what I am doing here.When writing your own UIPresentationController I assume that I have to call these methods at appropriate times. And I would like to know when to do it (presentationControllerWillDismiss: and presentationControllerDidDismiss: are obvious).It seems to be that UIPresentationController even has its own blocks (e.g. _sendDismiss) for handling these messages. Therefore, I expect that it might not be sufficient just to send these messages but that there are some additional conditions / preparations required.
I did not call popoverPresentationControllerShouldDismissPopover by myself. This method is called by the popover presentation controller beforre it dismisses the popover. BTW: I have overseen that UIAdaptivePresentationControllerDelegate implements a method presentationControllerShouldDismiss. Therefore, popoverPresentationControllerShouldDismissPopover is not needed anymore.
At least for Apple it seems to be possible (in Numbers they swap a popover against a slide in). But there does not seem to be a public API.
Post not yet marked as solved
Hi,I suppose that all bugs still exist in 11.1 or did you get a feedback from Apple that they have been solved?PS: I experience still the same issues as you have described with 11.0 (at least with that version I tested the new build system as I am too lazy to check all the time if some of the bugs disappeared whenever a new version arises).PPS: The most annoying part is that Xcode still suggests to use the new build system whenever you get a new Xcode version though the bugs make the new build system unusable.
Post not yet marked as solved
Yes, otherwise I would not see any fading.
Post not yet marked as solved
Are you responding to my example? Your example does not have anything to do with what I wrote.double value; ///< This is a value (look at the fading!)If I put the code as shown above into a C++ file (header file with ending .hpp) only "///" is faded, the '<' is not faded. This looks really strange and does not make much sense.
Post not yet marked as solved
There are lots of problems with Doxygen comments. Besides Doxygen I think the whole highlighting (besides reserved keywords) and indentation is broken in Xcode 11. In one evening I have submitted eight bug reports. There are a lot more but I just stopped reporting, it is hopeless (rant off).BTW: I did not report this one but this is also broken:double value; ///< This is a value (look at the fading!)
Post not yet marked as solved
Yes, syntax highlighting is badly broken in Xcode 11. Randomly code is not or wrongly highlighted.It does not help you but it confirms that the problem is not on your side.
Post not yet marked as solved
Hinothing special- (void)documentBrowser:(UIDocumentBrowserViewController *)controller
didPickDocumentURLs:(NSArray<NSURL *> *)documentURLs
{
NSLog(@"documentBrowser:didPickDocumentURLs:");
}and the same for documentPicker:didPickDocumentsAtURLs:. Both methods are surrounded with #if 0 or #if 1 to enable / disable the methods.I just wanted to test UIDocumentBrowserViewController. Therefore, nothing special.
Post not yet marked as solved
Hi,but what kind of logic is behind finding the character in another font? I mean which font is used when the character does not exist in the system font?BTW: I rather find this behaviour odd. I understand that for most people it is the easiest solution but it leads to unpredictable behaviour with respect to the chosen font.
Post not yet marked as solved
Hi,sorry, it seems to be that the smiley got lost during the copy & paste operation. Here again with smiley:UIFont* systemFont = [UIFont systemFontOfSize:20.0];
NSDictionary* attributes = [NSDictionary dictionaryWithObject:systemFont forKey:NSFontAttrib
uteName];
[@"🙂 " drawAtPoint:CGPointMake(100.0,100.0) withAttributes:attributes];Sorry for the format but it seems to be that the editor is not really able to handle the smileys....
