Search Results

Hi there, I'm currently playing around with Scribble and ran into an odd behavior. Let's say I have an app where I can scribble on a canvas. After scribble has finished, a custom view with a textView should appear and the scribbled text should be forwarded to the textView. Depending on where I wrote on the canvas, additional info is forwarded to the view and put in as a prefix for the textView. That at least was the idea. To implement this, I've added a UIIndirectScribbleInteraction to the canvas and implemented the UIIndirectScribbleInteractionDelegate. When the focus is requested through indirectScribbleInteraction:focusElementIfNeeded:referencePoint:completion:, I bring up the custom view, insert the prefix based on the referencePoint into the textView, make it become firstResponder and hand over the textView in the completion block. Now since the appearance of that custom view is pretty disruptive, I return true for indirectScribbleInteraction:shouldDelayFocusForElement:. And here is where the problem starts. As soon as I do that, the scribble input is always inserted at the start of the textView, so in front of my prefix. If I do not delay the focus and insert my prefix, the scribble input is correctly appended after the prefix. I do not fully understand why delaying the focus should change the behavior here. Scribble always only gets to know the target textView through calling the completion of indirectScribbleInteraction:focusElementIfNeeded:referencePoint:completion:, and before completion is called, the prefix is inserted. So I feel like scribble should be able to see that there is already text inside that textView and append its text, instead of inserting it into the front. I would welcome any clarification on my issue :) Thanks, Klemens

Hi, I have a custom UITextInput view implementing all the methods (I guess) of UITextInput. I'm also using a custom UITextInputStringTokenizer subclass, but the issue it the same with a bare UITextInputStringTokenizer: whatever I'm trying to select, the interaction selects the whole sentence, or some sub-sentence, but never the word. The same if I strike through, or try to insert or delete a space. I'm seeing the tokenizer being asked for sentences ranges, but never words. In an off the shelf UITextView, I'm seeing the same ranges being asked, and then a convergence with requests for words ranges. It never happens in my view. I'm quite sure the "positions for point" that I'm returning are correct, as well as the tokenizer's responses. If I'm using my finger, everything is fine. In other words, scribble interaction fails to identify the range to act on, and always find a range that is bigger than it should be. If I draw slowly to the right, sometime I see the selection handle position move ~5cm farther than the pencil to the right. If draw slowly to the left, the same, with the handle ~5cm farther to the left. Does anyone has the same issue? This renders scribble unusable in my view. This is for iOS 14 beta 1 on a 10.5 iPad Pro with the 1st generation Pencil. The issue happens whereas I'm installing myself an UIScribbleInteraction or do nothing and let the system do this itself on UITextInput apparently. Thanks in advance. Thomas

Right now after scribble is complete, the drawing disappears. Am I able to keep the drawing if I add a UIScribbleInteraction to PencilKit for example? That way I can get the handwriting translation and keep the pencilkit drawing.

Hello Apple Developer Team, I was wondering if you also allow developers to use your new Handwriting Recognition API for custom usage. For example I want to convert UIBezierPaths to Text. Is there a way to use this new API ?