Spencer:
> Hi,
>
>>
>> segfault:
>> I can send screenshots
>>
>
> Please do, if you can (:
Ok, so I implemented this and attached two screenshots of it. This is
about the password option. edit.png shows what it looks like normally.
If you click the "Edit"-button, the label becomes a text entry and grabs
focus. After you modified the string, you can either hit Return or
simply focus something else (by clicking somewhere else or tabbing out)
and the label will reappear.
>
> If not, no worries.
>
>>
>> to know when the string can be applied
>>
>
> If there is an 'Edit' button to enter the experience, there must be some
> 'Save' button to exit.
>
> If this is the case, might there be a 'Save' button instead of an 'Edit'
> button, keeping the form fields and minimizing clicks and micro contexts?
I imagine this without a "Save"-button.
Cheers
%0A>%20and%20the%20label%20will%20reappear.%0A>%20%0A>%20>%20%0A>%20>%20If%20not,%20no%20worries.%0A>%20>%20%0A>%20>>%0A>%20>>%20to%20know%20when%20the%20string%20can%20be%20applied%0A>%20>>%0A>%20>%20%0A>%20>%20If%20there%20is%20an%20'Edit'%20button%20to%20enter%20the%20experience,%20there%20must%20be%20some%0A>%20>%20'Save'%20button%20to%20exit.%0A>%20>%20%0A>%20>%20If%20this%20is%20the%20case,%20might%20there%20be%20a%20'Save'%20button%20instead%20of%20an%20'Edit'%0A>%20>%20button,%20keeping%20the%20form%20fields%20and%20minimizing%20clicks%20and%20micro%20contexts?%0A>%20%0A>%20I%20imagine%20this%20without%20a%20%22Save%22-button.%0A>%20%0A>%20Cheers%0A>%20 "Reply to this message")