Re: Can I Hide / Show an NSTextField / NSSecureTextField in Cocoa?
Re: Can I Hide / Show an NSTextField / NSSecureTextField in Cocoa?
- Subject: Re: Can I Hide / Show an NSTextField / NSSecureTextField in Cocoa?
- From: David Delmonte <email@hidden>
- Date: Sat, 08 Feb 2014 15:04:53 -0500
I am deferring to the expertise here and will use Mike Abdullah's password logic. However, this app is being designed for use at home - or - I admit - on portables. This is not a corporate entity. I'm not claiming my app is secure: "It's a bit better than writing your password on an envelope". I am wondering what UI people think about hidden passwords. Don't they annoy you when you cant see what your typing? They do me, but I'm old and grumpy.
On Feb 8, 2014, at 1:27 PM, Gary L. Wade <email@hidden> wrote:
Very true, and that's why I asked Apple in a Radar to fix it since, if it
CAN be done, they're more in a position to do it (masters of the hardware
and software) than relying upon each developer to make secondary screens.
Maybe the hint text could be a layer not available for secondary device
consumption on top of the actual bullet being displayed? Maybe a bit
slow/cumbersome and possibly only activated when a secondary screen is
used, but that's how I might start out trying to do it myself. I haven't
tried it myself, but I wonder if screenshots are only possible with the
bullet and no hint text; maybe a tie-in?
It's all academic for us; this needs to be addressed by Apple, so file
your Radar you've been threatening to do, and maybe it'll make the next
upgrade.
--
Gary L. Wade
http://www.garywade.com/
On 2/8/2014 10:10 AM, "Kyle Sluder" <email@hidden> wrote:
> On Feb 8, 2014, at 10:06 AM, "Gary L. Wade"
> <email@hidden> wrote:
>>
>> Yeah, that demo issue came up yesterday, so I filed my own
>> rdar://16013973
>> and as you know, it always helps to add duplicates! I marked mine as an
>> issue with Security and Always. I suggested only showing the hints on
>> the
>> actual device and doing a secondary broadcast without the hint on
>> secondary devices, especially simulators and AirPlay similar to how the
>> old DVD anti-copy-protection thing worked.
>
> AirPlay mirroring is done in hardware, IIRC. App authors have the ability
> to create a second screen and put the AirPlay content there, but for apps
> that don¹t do that the OS just feeds data from the GPU framebuffer to the
> MPEG encoder. It needs to be turned off on all screens if AirPlay is
> active.
>
> --Kyle Sluder
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden