Thanks to Peter for pointing out some issues. Update to fix them:
https://docs.google.com/file/d/0By_mW8YYOZpAZ19VUHdHcjViY28
On Wed, Jul 24, 2013 at 3:38 AM, Geoff Canyon gcan...@gmail.com wrote:
Thanks for pointing out the new messages for behaviors. This
Thanks for pointing out the new messages for behaviors. This
versionhttps://docs.google.com/file/d/0By_mW8YYOZpAOTE2blU1Y2JhMnM/should
address the following:
-- All messages should be before or after so they won't interfere with
your code.
-- Clicking on the selection should not change the
Thanks Geoff.
It looks like this is probably not going to work as a behavior for me since
the field I'm using it on includes mouseUp/Down handlers to handle
situations other than drag/drop, but other than that, this is great, thanks
again.
Pete
lcSQL Software http://www.lcsql.com
On Mon, Jul
Peter Haworth wrote:
It looks like this is probably not going to work as a behavior for me since
the field I'm using it on includes mouseUp/Down handlers to handle
situations other than drag/drop, but other than that, this is great, thanks
again.
I wonder if Geoff's script could be revised to
On Tue, Jul 23, 2013 at 11:02 AM, Richard Gaskin ambassa...@fourthworld.com
wrote:
I wonder if Geoff's script could be revised to use before mouseDown or
after mouseDown to allow instances to handle the primary forms of those
messages without interference?
Great idea, The before/after
Thanks Kaus for pointing it out, and particularly Scott who wrote the thing
in the first place. When I think back on all I went through with Navigator
trying to make the built-in drag-drop messages work (badly) it's
frustrating that this works so well without using the drag-drop messages at
all
https://docs.google.com/file/d/0By_mW8YYOZpATnFfeExKNkt1VXc
This version updates the history of the selection after a drag so the
problem you saw should be corrected. Feel free to update the instructions,
etc. and repost on your site. Let me know if you think of anything else it
needs.
On Sun,
On Tue, Jul 23, 2013 at 12:34 PM, Peter Haworth p...@lcsql.com wrote:
It looks like this is probably not going to work as a behavior for me since
the field I'm using it on includes mouseUp/Down handlers to handle
situations other than drag/drop, but other than that, this is great, thanks
On Tue, Jul 23, 2013 at 1:02 PM, Richard Gaskin
ambassa...@fourthworld.comwrote:
I wonder if Geoff's script could be revised to use before mouseDown or
after mouseDown to allow instances to handle the primary forms of those
messages without interference?
I checked, and the appropriate
On Sun, Jul 21, 2013 at 1:56 PM, Geoff Canyon gcan...@gmail.com wrote:
https://docs.google.com/file/d/0By_mW8YYOZpATnFfeExKNkt1VXc
This version updates the history of the selection after a drag so the
problem you saw should be corrected. Feel free to update the instructions,
etc. and repost
On Mon, Jul 22, 2013 at 3:44 PM, Peter Haworth p...@lcsql.com wrote:
Resending because the original got caught in the dreaded message is too
long vortex.
This is very useful, thanks Geoff.
I can't quite figure out what's going on with the format statement that's
part of the send of
On Mon, Jul 22, 2013 at 2:03 PM, Geoff Canyon gcan...@gmail.com wrote:
The dragLines message I messed up fixing the issue Scott mentioned above
(darn regression errors...) I have it fixed now, I'll upload a new copy in
a bit. To answer your question -- the first param is the drag lines, the
https://docs.google.com/file/d/0By_mW8YYOZpAME5lTE44c2oxRU0
That should fix the message so that, optionally, you can add a handler to
your list like this:
on dragLines dragLines,dropLines
end dragLines
and then if you select lines 12 and 18 and drag them to the top of the list
you would get
It's great Geoff! The one minor issue I noticed is, after a drag/drop
action, the field doesn't appear to be put back into a state of being able
to drag a new line. Doing so seems to enable one or multiple line
selections, but no drag. I have to click a second time to start a drag
action. But
I did some quick research, and this looks to be as much of a pain as I
remember -- or am I missing something? All I want is to place a scrolling
list field on a card, enable the multipleLines and nonContiguousHilites of
it, and then enable the (non-existent) supportDragAndDrop property.
On Wed,
Hi Geoff,
Am 18.07.2013 um 18:23 schrieb Geoff Canyon gcan...@gmail.com:
I did some quick research, and this looks to be as much of a pain as I
remember -- or am I missing something? All I want is to place a scrolling
list field on a card, enable the multipleLines and nonContiguousHilites of
You can load the stack directly in LC:
go URL http://www.tactilemedia.com/site_files/downloads/getinline.rev;
But this manages single lines only -- you'd have make to make adjustments
to handle multiple lines, which will be challenging with a discontiguous
selection.
Regards,
Scott Rossi
Does anyone have code to share that allows discontiguous selection and drag
and drop within a list field? i.e. if I have a list field with:
1
2
3
4
5
I can click 3 to select it, shift-click 5 to select 3 to 5, command-click 4
so that 3 and 5 are selected, and then click and drag 3 (with 5 along
18 matches
Mail list logo
