SanderElias a écrit :
Hi,
Hi,
1. on a successful drop, the draggable does a revert. I only want a
revert, when it's dropped outside an dropzone.
To do this, just remove the element in your ondrop function.
2. Somehow connecting to the draggable fails.
Hi Thomas,
Tanks for the quick reply
1. on a successful drop, the draggable does a revert. I only want a
revert, when it's dropped outside an dropzone.
To do this, just remove the element in your ondrop function.
but I'm moving it to a new parent, would that not remove that too? Or
do I
SanderElias a écrit :
Hi Thomas,
Tanks for the quick reply
You're welcome.
1. on a successful drop, the draggable does a revert. I only want a
revert, when it's dropped outside an dropzone.
To do this, just remove the element in your ondrop function.
but I'm moving it to a new
In the documentation, under MochiKit.Base.partial it says:
This could be used to implement, but is NOT currying.
I don't understand the distinction - would someone explain to me, why
this is not currying?
--
troels
--~--~-~--~~~---~--~~
You received this
Hello? Can anyone help me out here?
-Original Message-
From: mochikit@googlegroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Jason Bunting
Sent: Friday, January 05, 2007 3:18 PM
To: mochikit@googlegroups.com
Subject: [mochikit] parseQueryString bug?
If the url of the page is:
On 1/8/07, troelskn [EMAIL PROTECTED] wrote:
In the documentation, under MochiKit.Base.partial it says:
This could be used to implement, but is NOT currying.
I don't understand the distinction - would someone explain to me, why
this is not currying?
In functional programming, function
On 1/5/07, Jason Bunting [EMAIL PROTECTED] wrote:
If the url of the page is:
http://www.foo.com/bar.aspx?baz=blah#bottom
And the code is:
var args = parseQueryString(document.URL);
var paramValue = args.baz;
At this point paramValue is equal to blah#bottom instead of just blah as
Jorge Godoy [EMAIL PROTECTED] writes:
Hi!
I have this line of code on my application:
connect(document.body, 'onchange', calcular_resultado_creatinina);
Hi!
I've tried connecting on 'window' as well -- thanks Karl for your help! -- but
it didn't work.
A minimal example is
Kevin Damm [EMAIL PROTECTED] writes:
Maybe the onchange event isn't propagating to document.body in IE.
Have you tried wrapping everything in a div and connecting the
signal handler to that div instead? That seems to be a good
workaround.
It doesn't work as well. I have the impression that
