SecureTextEntry with QuickDialog and JSON?

Question

I'm trying to get a sample QuickDialog running via JSON. I current have:

{
    "grouped": true,
    "title": "Hello World",
    "controllerName": "MySampleController",
    "sections":
    [
        { "title":"Question:", "elements":
            [
                { "type":"QLabelElement", "title":"Hello", "value":"world!"},
                { "type":"QEntryElement", "key":"login",  "bind":"textValue:username", "title":"Login"},
                { "type":"QEntryElement", "key":"password",  "bind":"textValue:password", "title":"Password"}
            ]
        }
    ]
}

Which displays a label, username and password input. I would like to make the password input secure, but I have been unable to figure out how to do that via JSON.

I have tried adding the following element:

"secureTextEntry":"yes" but I get an exception:

[ setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key secureTextInput.'
*** First throw call stack:

Any suggestions on how I could get this working properly via QuickDialog's JSON implementation?

Hello, is the console referencing the class name that is not compliant for the key secureTextEntry — Daddy, Jul 29 '13 at 19:23

score 0 · Answer 1 · edited May 23 '17 at 12:20

0

I submit this answer by another StackOverflow member:

Why does valueForKey: on a UITextField throws an exception for UITextInputTraits properties?

There are some properties of UITextField that are not KVC Compliant.

In that question there is another person who has swizzled UITextField to allow a workaround.

edited May 23 '17 at 12:20

Community

1
1

answered Jul 29 '13 at 19:41

Daddy

9,045
7
69
98

I appreciate the answer, but I'm really looking to see if there is an existing way in the QuickDialog framework to get this running. They have the json loading routine, so I'm assuming that i'm overlooking a way of setting the property properly. – Kyle Jul 30 '13 at 10:19
Do you have access to the .m file for QEntryElement? – Daddy Jul 30 '13 at 12:41

score 0 · Answer 2 · edited Dec 31 '20 at 00:56

0

Maybe it is not a genuine way to use code like I am using. But you can modify

QEntryElement.h and QEntryElement.m files according to your requirement.

Remove this self.secureTextEntry = NO; line from - (QEntryElement *)init in QEntryElement.m file.

enter image description here

I modified the entry element file and got securetext entry.

enter image description here

See my modified method, maybe this could help you:

- (QEntryElement *)initWithTitle:(NSString *)title Value:(NSString *)value Placeholder:(NSString *)placeholder andSecureTextEntry:(BOOL)_secured{
    self = [self init];
    if (self) {
        _title = title;
        _textValue = value;
        _placeholder = placeholder;
        self.secureTextEntry=_secured;
    }
    return self;
}

in QEntryElement.h and m files.

edited Dec 31 '20 at 00:56

Jim Simson

2,774
3
22
30

answered Jul 30 '13 at 14:18

Prince Kumar Sharma

12,591
4
59
90

But then EVERY QEntryElement would become secure? – Kyle Jul 30 '13 at 14:42
yeah .. it is true.If here you can set then why not outside the file? – Prince Kumar Sharma Jul 30 '13 at 14:55
see this line in QEntryElement.h file @property(nonatomic,getter=isSecureTextEntry) BOOL secureTextEntry; – Prince Kumar Sharma Jul 30 '13 at 14:57

SecureTextEntry with QuickDialog and JSON?

2 Answers2