InPlace Editor with initial empty string

[itsm...@hotmail.com]

If I start with an initially empty string I don't get any place to
click & activate the editor. I would think that empty string is a
common default.

Alternately, the user may sometimes erase all the text in the field.
After that there is no way to activate the editor and enter text into
that same field.

Any suggestions? Am I doing something wrong?

[Justin Perkins]

On Jan 16, 2008 7:07 PM, itsm...@hotmail.com <itsm...@hotmail.com> wrote:
>
> If I start with an initially empty string I don't get any place to
> click & activate the editor. I would think that empty string is a
> common default.

I've typically used a default string as the value (for example, "not
set") and then if that value is detected (or empty string) when the
form is posted, then I just return the default string.

There's not really much that IPE can do in this case as most of the
implementation for these cases relies on page load values and server
behavior.

-justin

[Andrew Kaspick]

I use the externalControl option for cases like this. Doesn't matter
if the value is blank or not, I always have something to click on.

[Itsme]

> There's not really much that IPE can do in this case as most of the
> implementation for these cases relies on page load values and server
> behavior.

Hmmm. I don't like the idea of some distinguished value like "not set"
because the user will never be able to enter that string, and I don't want
my business objects to be know about it. Not too keen on the clutter of an
external control either, but maybe I can use it only in the case of empty
strings.

Hmmm. Hate it when simple things make me think hard. ...

[Itsme]

From: "Itsme" <itsm...@hotmail.com>

> Hmmm. Hate it when simple things make me think hard. ...

Hate it even more when I make simple things hard all on my own ... your
suggestion of "not set" works well, thanks Justin!