Debugging on dragdrop
Ken Ray
kray at sonsothunder.com
Sat Sep 6 11:00:01 EDT 2003
Rodney, you should probably log this into BugZilla if you haven't
already...
Ken Ray
Sons of Thunder Software
Email: kray at sonsothunder.com
Web Site: http://www.sonsothunder.com/
> -----Original Message-----
> From: use-revolution-admin at lists.runrev.com
> [mailto:use-revolution-admin at lists.runrev.com] On Behalf Of
> Rodney Tamblyn
> Sent: Sunday, September 07, 2003 7:43 AM
> To: use-revolution at lists.runrev.com
> Subject: Debugging on dragdrop
>
>
> I don't know if it's been noted before, but the following is a very
> good idea. I find debugging inside a dragdrop handler is liable to
> hang Revolution.
>
>
> local sDrag
>
> #not safe to debug
> on dragDrop
> #get whatever you are interested in out of dragdata & store in local
> var, eg
> put line 1 of dragData["files"] into sDrag
> if sDrag <> empty then
> send completeDrag to me in .5 seconds
> end if
> end dragDrop
>
> #safe to debug
> on completeDrag
> breakpoint
> #add script actions here
> put "received:"&&sDrag
> end completeDrag
>
>
> Rodney
>
>
> --
> Rodney Tamblyn
> 44 Melville Street
> Dunedin
> New Zealand
> +64 3 4778606
> http://rodney.weblogs.com/
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-> revolution
>
More information about the use-livecode
mailing list