Reliable script to handle selection/drag-and-drop in a list field?

Geoff Canyon gcanyon at gmail.com
Tue Jul 23 01:48:24 EDT 2013


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 that message with dragLines = 12,18 and dropLines = 1,2

gc


On Mon, Jul 22, 2013 at 4:03 PM, Geoff Canyon <gcanyon at gmail.com> wrote:

>
> On Mon, Jul 22, 2013 at 3:44 PM, Peter Haworth <pete at 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 dragLines.  Everything after the second backslash is
>> listed in red in the script editor as if there's an error but no errors
>> are
>> listed when a compile it.  I'm not sure what parameters are supposed to be
>> passed but what I see is the final line numbers of the dropped lines (in
>> quotes), then an empty string (in quotes).  SHould the second parm be the
>> original line numbers?
>>
>> Pete
>> lcSQL Software <http://www.lcsql.com>
>
>
>
> I'm seeing the red text in the format command as well. It happens after
> the second escaped quote I think, and appears to be an error in the syntax
> highlighting rather than an actual error.
>
> 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
> second is the drop lines.
>



More information about the use-livecode mailing list