Jason,
ended up spending a few hours rewriting some of my code in order to try
your code. Instead of dom:ready I implemented the inplace editor
onComplete and its working fine.
Still not sure why cancel doesn't actually kill the invocation or why
editor.dispose(); prevents the editor from
No problem - I have a grid of inplaceeditor's running about 60 instances on
one page so it took a few trys to make it work like I needed
Jason Westbrook | T: 313-799-3770 | jwestbr...@gmail.com
On Mon, Jan 28, 2013 at 6:28 AM, Phil Petree phil.pet...@gmail.com wrote:
Jason,
ended up
Hi All!
I'm implementing the scriptaculous inplace editor and I have it working
except for one small detail:
If I activate the editor, click cancel, activate the editor again I get two
inplace editors. cancel those and activate again and I get three. cancel
those and activate again and I get
On Jan 27, 2013, at 4:10 PM, Phil Petree wrote:
Hi All!
I'm implementing the scriptaculous inplace editor and I have it working
except for one small detail:
If I activate the editor, click cancel, activate the editor again I get two
inplace editors. cancel those and activate again
Thanks Walter.
I tried that already and found the editor to be essentially disabled (you
could click but not get the form).
On Jan 27, 2013 6:14 PM, Walter Lee Davis wa...@wdstudio.com wrote:
On Jan 27, 2013, at 4:10 PM, Phil Petree wrote:
Hi All!
I'm implementing the scriptaculous
So the actual problem is that you are creating multiple inplace editors -
create it once and let the inplace editor handle the click events
I answered a similar question in more depth on StackOverflow
Yes, multiple instances are being created.
Your stackoverflow solution doesn't work for me. The elements to be
inplace edited don't exist when the dom is loaded and may not ever exist.
I'm using a tab control, when the tab is activated an ajax call is made and
some html is returned. In this
