Date   

string pointer

Gerriet M. Denkmann
 

I have a method like (macOS 13.3, Xcode 9.2 (9C40b)):

- (NSUInteger)computeFor: (NSUInteger)arg reason: (NSString * __autoreleasing *)reason
{
NSUInteger value;
// some computing…
if ( reason != NULL ) *reason = @“Used Chebycheff approximation”;
return value;
}

to be use like:

NSUInteger a = [ self computeFor: 12 reason: NULL ]; // don’t care for reason
or:
NSString *s
NSUInteger b = [ self computeFor: 99 reason: &s ]; // want to know reason

I am not quite sure whether __autoreleasing is the correct annotation. Is it?

But my real problem is this:

BOOL needReason = …
NSString *s;
NSString **stringPointer = needReason ? &s : NULL;
NSUInteger c = [ self computeFor: 42 reason: stringPointer ]; // sometimes want to know the reason

I cannot figure out how to declare the stringPointer without getting compiler warnings.
How to do this?

Gerriet


Push notification debugging mobile profile on Apple's 2265 TN.

Alex Zavatone
 

https://developer.apple.com/library/content/technotes/tn2265/_index.html

Enabling Push Status Messages on iOS

To enable logging on iOS, install the configuration profile PersistentConnectionLogging.mobileconfig on your device by either putting the file on a web server and downloading it using Safari on your device, or by sending it as an email attachment and opening the attachment in Mail on your device. You'll be prompted to install "APS/PC Logging". Download the configuration profile by clicking Companion File at the upper right corner of this technote.




Testing on the Mac to see if it is allowed to be installed before sending it to the iOS device.
On the iOS device.


Looking inside the PersistentConnectionLogging.mobileconfig file, we see the profile expired almost 9 months ago and Apple has done nothing about it.

    <key>DurationUntilRemoval</key>
    <real>604800</real>
    <key>RemovalDate</key>
    <date>2017-06-17T12:00:00Z</date>

What do we have to do to get Apple to give us an actual valid debugging profile to debug push notifications?


Re: Keyboard types on the iPad for UITextFields

Ben Kennedy
 

On 30 Jan 2018, at 6:44 pm, Alex Zavatone <zav@...> wrote:

Oh, it would be OH SO NICE, if the docs and the header files actually indicated this to be the case.

Jesus. The docs need to represent what is there, not mislead the programmer.
For whose benefit is this rant?

We all agree with you.

-ben


Re: Keyboard types on the iPad for UITextFields

Alex Zavatone
 

Argh.  Thank for, Glenn.

Oh, it would be OH SO NICE, if the docs and the header files actually indicated this to be the case.  

The current documentation and comments are DIRECTLY MISLEADING.

It’s there in the headers - without any stipulation if there is a difference between iPhone or iPad - that the keyboard to be displayed will be of “this type with these keys".

Jesus.  The docs need to represent what is there, not mislead the programmer.  

And of course, now it’s expected of me to ask that the docs and the headers reflect this, when instead, I have to spend the time that I don’t have to make a numeric keypad.  

Sweet mother of aggravation.




On Jan 30, 2018, at 8:11 PM, Glenn L. Austin <glenn@...> wrote:

That's correct. There's no "numeric keypad" for the iPad.

-- 
Glenn L. Austin, Computer Wizard, AustinSoft.com

On Jan 30, 2018, at 3:53 PM, Alex Zavatone <zav@...> wrote:

Just checking in to see if someone here knows something I don’t with regards to the available keyboard types vs. the displayed keyboard types on the iPad under iOS.



Of course, the documentation here is rather thick and useless, as nowhere in Apple’s iOS docs can I see an image of the expected keyboard to be displayed for each UITextField.keyboardType.

Am I correct in assuming that there is no numbers and decimal point only keyboard that can be set for the iPad?

Out of all enums

These are the enums from UITextInputTraits.h that I have tried, and not one of them displayed a numbers only keypad, nor do the docs mention that the expected keyboard on an iPad should not be as indicated.

typedef NS_ENUM(NSInteger, UIKeyboardType) {
    UIKeyboardTypeDefault,                // Default type for the current input method.
    UIKeyboardTypeASCIICapable,           // Displays a keyboard which can enter ASCII characters
    UIKeyboardTypeNumbersAndPunctuation,  // Numbers and assorted punctuation.
    UIKeyboardTypeURL,                    // A type optimized for URL entry (shows . / .com prominently).
    UIKeyboardTypeNumberPad,              // A number pad with locale-appropriate digits (0-9, ۰-۹, ०-९, etc.). Suitable for PIN entry.
    UIKeyboardTypePhonePad,               // A phone pad (1-9, *, 0, #, with letters under the numbers).
    UIKeyboardTypeNamePhonePad,           // A type optimized for entering a person's name or phone number.
    UIKeyboardTypeEmailAddress,           // A type optimized for multiple email address entry (shows space @ . prominently).
    UIKeyboardTypeDecimalPad NS_ENUM_AVAILABLE_IOS(4_1),   // A number pad with a decimal point.
    UIKeyboardTypeTwitter NS_ENUM_AVAILABLE_IOS(5_0),      // A type optimized for twitter text entry (easy access to @ #)
    UIKeyboardTypeWebSearch NS_ENUM_AVAILABLE_IOS(7_0),    // A default keyboard type with URL-oriented addition (shows space . prominently).
    UIKeyboardTypeASCIICapableNumberPad NS_ENUM_AVAILABLE_IOS(10_0), // A number pad (0-9) that will always be ASCII digits.

    UIKeyboardTypeAlphabet = UIKeyboardTypeASCIICapable// Deprecated
};

Thanks in advance,
Alex Zavatone



Re: Keyboard types on the iPad for UITextFields

Glenn L. Austin
 

That's correct. There's no "numeric keypad" for the iPad.

-- 
Glenn L. Austin, Computer Wizard, AustinSoft.com

On Jan 30, 2018, at 3:53 PM, Alex Zavatone <zav@...> wrote:

Just checking in to see if someone here knows something I don’t with regards to the available keyboard types vs. the displayed keyboard types on the iPad under iOS.



Of course, the documentation here is rather thick and useless, as nowhere in Apple’s iOS docs can I see an image of the expected keyboard to be displayed for each UITextField.keyboardType.

Am I correct in assuming that there is no numbers and decimal point only keyboard that can be set for the iPad?

Out of all enums

These are the enums from UITextInputTraits.h that I have tried, and not one of them displayed a numbers only keypad, nor do the docs mention that the expected keyboard on an iPad should not be as indicated.

typedef NS_ENUM(NSInteger, UIKeyboardType) {
    UIKeyboardTypeDefault,                // Default type for the current input method.
    UIKeyboardTypeASCIICapable,           // Displays a keyboard which can enter ASCII characters
    UIKeyboardTypeNumbersAndPunctuation,  // Numbers and assorted punctuation.
    UIKeyboardTypeURL,                    // A type optimized for URL entry (shows . / .com prominently).
    UIKeyboardTypeNumberPad,              // A number pad with locale-appropriate digits (0-9, ۰-۹, ०-९, etc.). Suitable for PIN entry.
    UIKeyboardTypePhonePad,               // A phone pad (1-9, *, 0, #, with letters under the numbers).
    UIKeyboardTypeNamePhonePad,           // A type optimized for entering a person's name or phone number.
    UIKeyboardTypeEmailAddress,           // A type optimized for multiple email address entry (shows space @ . prominently).
    UIKeyboardTypeDecimalPad NS_ENUM_AVAILABLE_IOS(4_1),   // A number pad with a decimal point.
    UIKeyboardTypeTwitter NS_ENUM_AVAILABLE_IOS(5_0),      // A type optimized for twitter text entry (easy access to @ #)
    UIKeyboardTypeWebSearch NS_ENUM_AVAILABLE_IOS(7_0),    // A default keyboard type with URL-oriented addition (shows space . prominently).
    UIKeyboardTypeASCIICapableNumberPad NS_ENUM_AVAILABLE_IOS(10_0), // A number pad (0-9) that will always be ASCII digits.

    UIKeyboardTypeAlphabet = UIKeyboardTypeASCIICapable// Deprecated
};

Thanks in advance,
Alex Zavatone


Re: macOS animation works once, then not again

Steve Mills
 

On Jan 30, 2018, at 14:40:29, Quincey Morris <quinceymorris@...> wrote:

On Jan 30, 2018, at 09:52 , Steve Mills <sjmills@...> wrote:

I don’t know, but your code made me wonder what happens (if you haven’t tried it already) if you remove this line from your completion handler:

self.bezView.alphaValue = 1;
and add this variation to the initiating animation block:

self.bezView.animator.alphaValue = 1;
Doing that did indeed make it work. I ended up with 3 animate/completion blocks: 1. Do the zoom/scroll. 2. Fade the bez in very quickly (0.001). 3. Fade the bez out.

I appreciate that Apple has continually added new ways to animate the UI, each one supposedly easier to use than the previous, but damn, there are so many gotchas with each one. One might suck at smooth resizing unless you set the layerContentsRedrawPolicy to a certain value. Another might be very easy to use, but doesn't do a whole bunch of properties at all. One clearly doesn't look at the current value of the property it's animating and start the animation there. Bleah!

Thanks for the suggestion!

--
Steve Mills
Drummer, Mac geek


Keyboard types on the iPad for UITextFields

Alex Zavatone
 

Just checking in to see if someone here knows something I don’t with regards to the available keyboard types vs. the displayed keyboard types on the iPad under iOS.



Of course, the documentation here is rather thick and useless, as nowhere in Apple’s iOS docs can I see an image of the expected keyboard to be displayed for each UITextField.keyboardType.

Am I correct in assuming that there is no numbers and decimal point only keyboard that can be set for the iPad?

Out of all enums

These are the enums from UITextInputTraits.h that I have tried, and not one of them displayed a numbers only keypad, nor do the docs mention that the expected keyboard on an iPad should not be as indicated.

typedef NS_ENUM(NSInteger, UIKeyboardType) {
    UIKeyboardTypeDefault,                // Default type for the current input method.
    UIKeyboardTypeASCIICapable,           // Displays a keyboard which can enter ASCII characters
    UIKeyboardTypeNumbersAndPunctuation,  // Numbers and assorted punctuation.
    UIKeyboardTypeURL,                    // A type optimized for URL entry (shows . / .com prominently).
    UIKeyboardTypeNumberPad,              // A number pad with locale-appropriate digits (0-9, ۰-۹, ०-९, etc.). Suitable for PIN entry.
    UIKeyboardTypePhonePad,               // A phone pad (1-9, *, 0, #, with letters under the numbers).
    UIKeyboardTypeNamePhonePad,           // A type optimized for entering a person's name or phone number.
    UIKeyboardTypeEmailAddress,           // A type optimized for multiple email address entry (shows space @ . prominently).
    UIKeyboardTypeDecimalPad NS_ENUM_AVAILABLE_IOS(4_1),   // A number pad with a decimal point.
    UIKeyboardTypeTwitter NS_ENUM_AVAILABLE_IOS(5_0),      // A type optimized for twitter text entry (easy access to @ #)
    UIKeyboardTypeWebSearch NS_ENUM_AVAILABLE_IOS(7_0),    // A default keyboard type with URL-oriented addition (shows space . prominently).
    UIKeyboardTypeASCIICapableNumberPad NS_ENUM_AVAILABLE_IOS(10_0), // A number pad (0-9) that will always be ASCII digits.

    UIKeyboardTypeAlphabet = UIKeyboardTypeASCIICapable// Deprecated
};

Thanks in advance,
Alex Zavatone


Re: macOS animation works once, then not again

Alex Zavatone
 

Can you dump the properties of the object you are trying to animate and the view before and after each attempt?

What thread is this happening on? Anything else besides thread 1?

A year back, I noticed that animations simply weren’t happening in my iOS app, but only on the iPad. At one point, I gave up in frustration and went off to grab a coffee. When I came back, the animation was completed.

What was happening was that the animation was not happening on the main thread and between 15 and 26 seconds later, it executed.

If that’s not it, are you properly starting and ending the animationContext?

What if you dispatch the animation on the main thread as async with GCD?

Alex Zavatone

On Jan 30, 2018, at 11:52 AM, Steve Mills <sjmills@...> wrote:

I'm probably missing something obvious here. I have an NSScrollView. Its document view is an NSImageView. At some point, I add a custom NSView subclass as a subview of the image view. This custom view draws a bezier path over the image. All good so far.

At certain points, I need to animate a zoom/scroll to focus on a particular area of the image, then show the bezier view, and finally fade out the bezier view (a simple "look here" signal to the user). This works the first time (the bezier draws and fades out), but I can't get the bezier view to show itself again.

I've tried many different forms of animation: NSAnimationContext's runAnimationGroup; adding a CABasicAnimation to the bezier view's layer; NSAnimationContext beginGrouping/endGrouping; possibly others. The property I'm changing is bezView.animator.alphaValue or bezView.layer.opacity.

I've tried forcing the bezier view to be layer-based (as well as replacing the host layer with a CAShapeLayer) or just drawing the bezier in the drawRect method. Here's the code that works just peachy on iOS:

[UIView animateWithDuration:1 delay:0 usingSpringWithDamping:0.7 initialSpringVelocity:1 options:0 animations:^{
if(!CGRectIsEmpty(boxToZoomTo))
[self.scrollView zoomToRect:boxToZoomTo animated:NO];
} completion:^(BOOL finished) {
self.bezView.alpha = 1;

[UIView animateWithDuration:1 animations:^{
self.bezView.alpha = 0;
}];
}];

And here's one attempt that's similar on macOS (setting allowsImplicitAnimation was something else I tried):

[NSAnimationContext runAnimationGroup:^(NSAnimationContext* _Nonnull context) {
context.duration = 1;
context.allowsImplicitAnimation = YES;

if(!CGRectIsEmpty(boxToZoomTo))
[self.scrollView.animator magnifyToFitRect:boxToZoomTo];
} completionHandler:^{
self.bezView.alphaValue = 1;

[NSAnimationContext runAnimationGroup:^(NSAnimationContext* _Nonnull context) {
context.duration = 1;
context.allowsImplicitAnimation = YES;
self.bezView.animator.alphaValue = 0;
} completionHandler:^{
}];
}];

Shouldn't that just work? Why isn't it redrawing the bez view at alphaValue 1 before fading to 0?

--
Steve Mills
Drummer, Mac geek




Re: macOS animation works once, then not again

Quincey Morris
 

On Jan 30, 2018, at 09:52 , Steve Mills <sjmills@...> wrote:

Shouldn't that just work? Why isn't it redrawing the bez view at alphaValue 1 before fading to 0?

I don’t know, but your code made me wonder what happens (if you haven’t tried it already) if you remove this line from your completion handler:

self.bezView.alphaValue = 1;

and add this variation to the initiating animation block:

self.bezView.animator.alphaValue = 1;

(Not the exact animation you were looking for, but the question is whether it works at all.)

Or, going at the opposite end of that same thought, is it in fact meaningful to use the animator proxy:

self.bezView.animator.alphaValue = 0;

inside an explicit animation block? Maybe you can’t mix the two mechanisms.

(I looked back at some code I wrote years ago that used explicit animations to fade views in and out, but it was not much help. I used NSViewAnimation objects, and I had commented it out anyway, because at some macOS update it stopped working reliably and I had no idea why.)




macOS animation works once, then not again

Steve Mills
 

I'm probably missing something obvious here. I have an NSScrollView. Its document view is an NSImageView. At some point, I add a custom NSView subclass as a subview of the image view. This custom view draws a bezier path over the image. All good so far.

At certain points, I need to animate a zoom/scroll to focus on a particular area of the image, then show the bezier view, and finally fade out the bezier view (a simple "look here" signal to the user). This works the first time (the bezier draws and fades out), but I can't get the bezier view to show itself again.

I've tried many different forms of animation: NSAnimationContext's runAnimationGroup; adding a CABasicAnimation to the bezier view's layer; NSAnimationContext beginGrouping/endGrouping; possibly others. The property I'm changing is bezView.animator.alphaValue or bezView.layer.opacity.

I've tried forcing the bezier view to be layer-based (as well as replacing the host layer with a CAShapeLayer) or just drawing the bezier in the drawRect method. Here's the code that works just peachy on iOS:

[UIView animateWithDuration:1 delay:0 usingSpringWithDamping:0.7 initialSpringVelocity:1 options:0 animations:^{
if(!CGRectIsEmpty(boxToZoomTo))
[self.scrollView zoomToRect:boxToZoomTo animated:NO];
} completion:^(BOOL finished) {
self.bezView.alpha = 1;

[UIView animateWithDuration:1 animations:^{
self.bezView.alpha = 0;
}];
}];

And here's one attempt that's similar on macOS (setting allowsImplicitAnimation was something else I tried):

[NSAnimationContext runAnimationGroup:^(NSAnimationContext* _Nonnull context) {
context.duration = 1;
context.allowsImplicitAnimation = YES;

if(!CGRectIsEmpty(boxToZoomTo))
[self.scrollView.animator magnifyToFitRect:boxToZoomTo];
} completionHandler:^{
self.bezView.alphaValue = 1;

[NSAnimationContext runAnimationGroup:^(NSAnimationContext* _Nonnull context) {
context.duration = 1;
context.allowsImplicitAnimation = YES;
self.bezView.animator.alphaValue = 0;
} completionHandler:^{
}];
}];

Shouldn't that just work? Why isn't it redrawing the bez view at alphaValue 1 before fading to 0?

--
Steve Mills
Drummer, Mac geek


Re: Tootips in NSTextView/NSTextfields

Sak Wathanasin
 


On 04 Jan 2018, at 18:00, Andy Lee <aglee@...> wrote:

I did find a problem: the tooltip doesn't seem to work the first time I position the cursor, only on subsequent attempts.

For testing purposes I found it helped to add .cursor:NSCursor.pointingHand to the attribute dictionary.  That cursor's hot spot is the tip of the finger, so to me it feels easier to position the cursor in a way that triggers the tooltip.


Thank you, thank you, thank you - I had just about resigned myself to having to subclass NSTextView and tracking the mouse etc. The issue with its not showing the tooltip the first time is a bit weird; maybe it has something to do with first responders - I'll play around with it.

Thanks again,
Sak


Re: Tootips in NSTextView/NSTextfields

Andy Lee
 

On Jan 4, 2018, at 12:25 PM, Andy Lee <aglee@...> wrote:
Your code works for me.  It's a little fussy though about placement of the text cursor.  I had to position the tiny horizontal mark in the middle of the text cursor just *under* the word "tooltip" instead of directly over it.

I did find a problem: the tooltip doesn't seem to work the first time I position the cursor, only on subsequent attempts.

For testing purposes I found it helped to add .cursor:NSCursor.pointingHand to the attribute dictionary.  That cursor's hot spot is the tip of the finger, so to me it feels easier to position the cursor in a way that triggers the tooltip.

I wonder if there is a bug in the iBeam cursor.  The docs say the default hot spot is "where the crossbeam intersects the I", but it doesn't seem to work that way for purposes of triggering the tooltip.

--Andy


Re: Tootips in NSTextView/NSTextfields

Andy Lee
 

On Jan 4, 2018, at 9:06 AM, Sak Wathanasin <sw@...> wrote:
The word "tooltip" is shown in red as expected, but no tooltip appears when I hover over it. What
am I missing?
Your code works for me. It's a little fussy though about placement of the text cursor. I had to position the tiny horizontal mark in the middle of the text cursor just *under* the word "tooltip" instead of directly over it.

--Andy


Re: Replace object at key path in NS[Mutable]Dictionary

Jonathan Taylor
 

I can load the plist file as an NSMutableDictionary, but it seems that only makes the top level dictionary mutable. The dictionaries-within-dictionaries are still immutable. 

Have you tried using NSPropertyListSerialization with the NSPropertyListMutableContainers option? That should make all the nested dictionaries/arrays mutable.

Thankyou Jens (and also Jon) for your reply. That was just what I was hoping for - an API that I didn’t even know where to look for (though obvious in retrospect!). That should do very nicely.


Tootips in NSTextView/NSTextfields

Sak Wathanasin
 

I want to display tooltips over parts of an attributed string, and thought that using an
NSToolTipAttributeName attribute on the required ranges would do the trick but I can't get it to
work. In my toy (macOS) app, I have a NSTxtView and in my aWakeFromNib, I do

let testString = "Test text with tooltip"
let testNSString = testString as NSString
let tooltipRange = testNSString.range(of: "tooltip")
self.textView.textStorage?.replaceCharacters(in: NSMakeRange(0,
self.textView.textStorage!.length), with: testString)
self.textView.textStorage?.setAttributes([NSAttributedStringKey.toolTip: "sample tooltip
text" as NSString,
NSAttributedStringKey.foregroundColor:
NSColor.red], range: tooltipRange)

The word "tooltip" is shown in red as expected, but no tooltip appears when I hover over it. What
am I missing?

Thanks for any help,

Sak


Re: Replace object at key path in NS[Mutable]Dictionary

Jon Gotow
 

On Jan 2, 2018, at 10:55 AM, Jonathan Taylor <jonathan.taylor@...> wrote:

I have a dictionary that has been loaded from a plist file, which has a deep structure of dictionaries within dictionaries. I would like to modify just one key-value pair deep in that hierarchy. Is there a neat off-the-shelf way of doing that?

I can load the plist file as an NSMutableDictionary, but it seems that only makes the top level dictionary mutable. The dictionaries-within-dictionaries are still immutable. Suppose I want to modify the value associated with the key path dict.next_level.deeper.even_deeper.key. The only way I can see to achieve this is to replicate “even_deeper" as a mutable dictionary, modify the value of “key” in it, replicate “deeper” and modify “even_deeper”, replicate “next_level” and modify “deeper”, and finally modify “next_level” within “dict”.

I could write recursive code to do that, but it feels as if there ought to be a more straightforward way of achieving what I want. Can anyone point me at something I have missed?
I've always just converted the entire dictionary and its contents to mutable objects. I've included some code below for the necessary categories to implement "mutableCopyDeep" methods. It does a deep traversal to create mutable copies of everything in an NSDictionary or NSArray.


- Jon



#import "MutableCopyDeep.h"

@implementation NSDictionary (MutableCopyDeep)

- (NSMutableDictionary*)mutableCopyDeep
{
NSMutableDictionary* copy = [[NSMutableDictionary alloc] init];
[self enumerateKeysAndObjectsUsingBlock:^(id key, id obj, BOOL *stop) {
id cobj = [obj mutableCopyDeep];
[copy setObject:cobj forKey:key];
#if !__has_feature(objc_arc)
[cobj release];
#endif
}];

return copy;
}


@end

#pragma mark -

@implementation NSArray (MutableCopyDeep)

- (NSMutableArray*)mutableCopyDeep
{
NSMutableArray* copy = [[NSMutableArray alloc] init];
[self enumerateObjectsUsingBlock:^(id obj, NSUInteger idx, BOOL *stop) {
id cobj = [obj mutableCopyDeep];
[copy addObject:cobj];
#if !__has_feature(objc_arc)
[cobj release];
#endif
}];

return copy;
}

@end

#pragma mark -

@implementation NSObject (MutableCopyDeep)

- (id)mutableCopyDeep
{
if([self respondsToSelector:@selector(mutableCopyWithZone:)])
return [self mutableCopy];
else
return [self copy];
}


@end


Re: Replace object at key path in NS[Mutable]Dictionary

 



On Jan 2, 2018, at 9:55 AM, Jonathan Taylor <jonathan.taylor@...> wrote:

I can load the plist file as an NSMutableDictionary, but it seems that only makes the top level dictionary mutable. The dictionaries-within-dictionaries are still immutable. 

Have you tried using NSPropertyListSerialization with the NSPropertyListMutableContainers option? That should make all the nested dictionaries/arrays mutable.

—Jens


Replace object at key path in NS[Mutable]Dictionary

Jonathan Taylor
 

HiI all,

I have a dictionary that has been loaded from a plist file, which has a deep structure of dictionaries within dictionaries. I would like to modify just one key-value pair deep in that hierarchy. Is there a neat off-the-shelf way of doing that?

I can load the plist file as an NSMutableDictionary, but it seems that only makes the top level dictionary mutable. The dictionaries-within-dictionaries are still immutable. Suppose I want to modify the value associated with the key path dict.next_level.deeper.even_deeper.key. The only way I can see to achieve this is to replicate “even_deeper" as a mutable dictionary, modify the value of “key” in it, replicate “deeper” and modify “even_deeper”, replicate “next_level” and modify “deeper”, and finally modify “next_level” within “dict”.

I could write recursive code to do that, but it feels as if there ought to be a more straightforward way of achieving what I want. Can anyone point me at something I have missed?

Cheers
Jonny.

[University of Glasgow: The Times Scottish University of the Year 2018]


Re: Is it possible to connect different hosts on LAN with NSXPCConnection?

Akifumi Takata
 

Dear all,

I gave up the use of NSXPCConnection.
Instead, I decided to use NSNetService and NSStream.

Regards,
Akifumi Takata


Showing tooltips myself

Graham Cox
 

HI,

Is there a way to force a tooltip to display when I want it to?

I have a UI with a spring-loaded popover - it is only shown during mousedown on its host view. Tooltips on the items in the popover don’t show because of this. I’d like to be able to show tooltips during the mouse-down tracking (after a suitable delay).

I can’t find any API that allows this - do I have to basically fake tooltips using my own window?

—Graham

981 - 1000 of 1478