nib2cib blows up on NSSecureTextFields about cappuccino HOT 15 CLOSED

Could you attach a sample nib. It seems to be working OK for me. Again, the bezel doesn't show up due to an unrelated bug, but aside from that the nib converts successfully and loads fine.

from cappuccino.

Damn, if I find out how to attach a file...

from cappuccino.

Alternatively you can just email it to me at francisco at 280 north dot com

from cappuccino.

Well, I can't find out how to do it. Till then, here is the xib: http://gist.github.com/104966

from cappuccino.

It currently contains one placeholder 'a' in the NSSecureTextField. If I remove that, it blows up after being converted and loaded into Cappuccino.

from cappuccino.

I seem to be able to use it OK on my end, except for the fact that it has no background:
http://www.quicksnapper.com/tolmasky/image/cpsecuretextfield

Are any errors being reported on your end?

from cappuccino.

Thats how it works when some placeholder text is in the CPSecureTextField.

When I change the xib to get rid of the "a" in the CPSecureTextField like this and try to load the cib (also in the gist) it totally blows up the nib loading with errors like these:

2009-04-03 14:56:11.366 Cappuccino: Connection from <_CPCibCustomObject 0x000de2> (CPObject) to  and label usernameTextField decoded.
2009-04-03 14:56:11.369 Cappuccino: Connection from <_CPCibWindowTemplate 0x000de0> to  and label password decoded.
2009-04-03 14:56:11.370 Cappuccino: Connection from <_CPCibWindowTemplate 0x000de0> to  and label login decoded.
2009-04-03 14:56:11.382 Cappuccino: Connection from  to  and label nextKeyView decoded.
2009-04-03 14:56:11.389 Cappuccino: Connection from <_CPCibCustomObject 0x000de2> (CPObject) to <_CPCibWindowTemplate 0x000de0> and label passwordWindow decoded.
2009-04-03 14:56:11.396 Cappuccino: Connection from <_CPCibCustomObject 0x000de2> (CPObject) to  and label passwordTextField decoded.
2009-04-03 14:56:11.406 Cappuccino: Connection from <_CPCibWindowTemplate 0x000de0> to  and label username decoded.
2009-04-03 14:56:11.412 Cappuccino: Connection from  to  and label nextKeyView decoded.
2009-04-03 14:56:11.420 Cappuccino: Connection from  to <_CPCibCustomObject 0x000de2> (CPObject) and label checkLogin: decoded.
2009-04-03 14:56:11.427 Cappuccino: Connection from <_CPCibWindowTemplate 0x000de0> to  and label initialFirstResponder decoded.
2009-04-03 14:56:11.492 Cappuccino:  setValue:  forKey: usernameTextField
2009-04-03 14:56:11.501 Cappuccino:  setValue:  forKey: password
2009-04-03 14:56:11.508 Cappuccino:  setValue:  forKey: login
2009-04-03 14:56:11.513 Cappuccino:  setValue:  forKey: nextKeyView
2009-04-03 14:56:11.520 Cappuccino:  setValue:  forKey: passwordWindow
2009-04-03 14:56:11.526 Cappuccino:  setValue:  forKey: passwordTextField
2009-04-03 14:56:11.533 Cappuccino:  setValue:  forKey: username
2009-04-03 14:56:11.540 Cappuccino:  setValue:  forKey: nextKeyView
2009-04-03 14:56:11.547 Cappuccino: [ setTarget: ]
2009-04-03 14:56:11.552 Cappuccino: [ setAction: checkLogin:]
2009-04-03 14:56:11.560 Cappuccino:  setValue:  forKey: initialFirstResponder
2009-04-03 14:56:11.614 Cappuccino: here?7
2009-04-03 14:56:11.621 Cappuccino: here?7
2009-04-03 14:56:11.627 Cappuccino: here?7
2009-04-03 14:56:11.634 Cappuccino: here?7
2009-04-03 14:56:11.640 Cappuccino: here?7
2009-04-03 14:56:11.646 Cappuccino: here?7
2009-04-03 14:56:11.652 Cappuccino: here?7
2009-04-03 14:56:11.658 Cappuccino: here?7

from cappuccino.

This has gotten even worse with the latest beta checkouts - now these errors even happen when there is no default text in the xib in the NSSecureTextField

from cappuccino.

I have to ammend that - after more investigation it seems that the gui actually works - however the rendering is completely broken. The TextFields both don't show up (CPTextField as well as CPSecureTextField, one of the labels is not showing and also the button is not visible.

All elements however seem to work when one manages to get to them via the mouse.
Oh, and also the next keyview attribute doesn't seem to work on the textfields. :/

from cappuccino.

I just fixed the issue with nextkeyview. I don't see any other problems with either CPTextField or CPSecureTextField EXCEPT the background not drawing for CPSecureTextField, which is a known issue and a separate bug, and the solution for which is in the works right now.

Can you confirm, with the latest codebase, that this is true for you as well?

from cappuccino.

It's a bit hard to verify since the rendering is still off.

However with the current version (e395d6e) the nib conversion and loading seems to work - though the rendering is broken for the CPTextField as well as the CPSecureTextfield.

Not sure why this is. though.

From my point of view, converting the nib seems to work ok. It loads, the default values are there for the textfield and the password field. The keyview loop seems to work too. (This is a bit hard to test, because not even the selection is displayed in a textfield).

The background doesn't render though for both fields, and the button is also not rendered and doesn't respond to the \R key equivalent.

from cappuccino.

We've done some significant retooling of the theme stuff recently. Could you make sure you're on the absolute latest commit and also try scrapping your Build folder and building from scratch to see if that solves your rendering issues? If it still mis-renders could you link to a screenshot so that we can get a better idea of what's going on.

Thanks!

from cappuccino.

How exactly am I supposed to attach a screenshot here? Using gist for sourceode is ... ok. But for images?

from cappuccino.

Strange. I am on 77c2ab3 now and I killed my build folder - and it works perfectly (except the button responding to \R).

Very strange. I tested this earlier today being on e395d6e - also scraping my build folder, and there it didn't work at all. The rendering was still very broken.

I have no idea why this is, as that one more commit i've got since the morning doesn't seem to have anything to do with this at all.

BUT: that closes this issue for me. :)

from cappuccino.

Great to hear! Please reopen the bug if it pops up again though.

from cappuccino.