get inline

[Peter Haworth]

Hi Scott,
No drag handlers but I know what's causing the problem although I don't
understand why.

A few months back, there was a thread about how to have a scrolling list
field react to drag and drop AND a normal single click.  The solution was
the following code:

get milliseconds()

set the dragData["text"] to empty

   repeat

      if milliseconds() - it > 200 then

         enableReorder the long ID of me

         exit repeat

      end if

      if mouse(1) is "up" then exit repeat

   end repeat


If the mouse is down for 200 milliseconds, it assumes a drag/drop is in
operation, otherwise it's a normal single click.  You can see I put the
enableReoder call in there when the 200 milliseconds expires.


If I replace the above code with a call to enableReorder, the drag/drop
works just fine. What's puzzling me is why the above code stops the
drag/drop even though my log file shows that enableReoder and all its
associated handlers are executed.


Is it possible that LC goes into its own drag/drop mode when the mouse is
down for some interval of time less than 200 milliseconds?  I need the
ability to recognise a single mouse click as well as a drag/drop.


Thanks,



Pete
lcSQL Software <http://www.lcsql.com>



On Tue, Jul 24, 2012 at 12:48 PM, Scott Rossi <scott at tactilemedia.com>wrote:

> If you're getting a drag/drop cursor displayed, you must have some kind of
> drag/drop handler in your stack somewhere.  GetInLine doesn't use any of
> the
> native drag/drop routines.
>
> Regards,
>
> Scott Rossi
> Creative Director
> Tactile Media, UX Design
>
>
>
>
> Recently, Peter Haworth wrote:
>
> > I'm using Scott Rossi's getinline technique to drag and drop lines
> within a
> > scrolling list field.  Used it several times in the past and no problems.
> >  On this particular field, as soon as I start to drag, I get the
> grey/white
> > "no entry/not allowed" icon instead of the line image and the graphic
> that
> > indicates where I am in the drop operation.
> >
> > I put some code in each handler to write the params out to a log file and
> > it looks like it is going through all the expected handler's in Scott's
> > script but alas, no drop.
> >
> > I've compared the properties of this field to others where the drag/drop
> > works but can't spot any obvious differences.  The contents of this field
> > are definitely more complex that the others; it contains tabs and several
> > character with their imagesource set to one icon or another.
> >
> > At this point I'm out of ideas of where to look.  This is on OS X Lion
> and
> > LC 5.5.0.  Any suggestions much appreciated.
> >
> > Thanks,
> >
> > Pete
> > lcSQL Software <http://www.lcsql.com>
> > _______________________________________________
> > use-livecode mailing list
> > use-livecode at lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
> subscription
> > preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>