I'll give that a go.
Bob S
> On Mar 24, 2017, at 14:50 , J. Landman Gay via use-livecode
> wrote:
>
> The theory is that something is interfering with the drop, so altering the
> text after the drop completes might fix it. Could be a bug, but using "send"
> may work around it.
__
The theory is that something is interfering with the drop, so altering
the text after the drop completes might fix it. Could be a bug, but
using "send" may work around it.
On 3/24/17 4:38 PM, Bob Sneidar via use-livecode wrote:
In that case sending would only replace the dropped text. No point
In that case sending would only replace the dropped text. No point in that. The
text is getting into the field using either method. It's just that the window
controls become unresponsive like they might if a script was still running. Why
moving a window or switching focus would clear the conditi
Try the "send" method then, which updates the text after the drop.
On 3/24/17 3:47 PM, Bob Sneidar via use-livecode wrote:
Whoops! Spoke too soon. Still makes the window unresponsive.
Apparently the problem is intermittent. But it also looks like exit
to top without allowing the drop is the only
No, because the problem apparently happens AFTER the text is placed. Everything
works, I just cannot manipulate any controls until I either move the window or
select something ANYTHING, even a different program (window loses focus).
Bob S
> On Mar 24, 2017, at 14:02 , Dr. Hawkins via use-live
would using "set the text of me" rather than "put into me" make a
difference?
On Fri, Mar 24, 2017 at 1:47 PM, Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Whoops! Spoke too soon. Still makes the window unresponsive. Apparently
> the problem is intermittent. But it also
Whoops! Spoke too soon. Still makes the window unresponsive. Apparently the
problem is intermittent. But it also looks like exit to top without allowing
the drop is the only reliable solution.
Bob S
> On Mar 24, 2017, at 13:33 , Bob Sneidar via use-livecode
> wrote:
>
> So here is the new
Interesting. I added the exit to top yesterday because it seemed to fix the
responsiveness problem. It has been working without exit to top and pass
dragdrop of over 2 years. I think it's because I am not acually allowing the
drop to happen, but rather intercepting it, getting the dragData ["tex
On 3/24/17 1:03 PM, Bob Sneidar via use-livecode wrote:
constant cModeList = "uppercase,lowercase,numbers,custom"
constant cCustomChars = "!#$%&'*+-/=?^_`{|}~.@"
on dragDrop
put cleanASCII(the dragData ["text"], cModeList, cCustomChars) into me
exit to top
end dragDrop
The first thing to
Here is a handler in a field script. The exit to top is necessary because of
the issue. The source can be an email from the Mail app, or it can be text from
an OCR'd PDF. The CleanASCII function is necessary because Acrobat will insert
non-printing characters for what reason I do not know, that
Just tried a simple test on Mac OS Sierra / LC8.1.3 and it seems to work fine
here. Is there anything else that could be interfering with the dragDrop?
Maybe the Message Watcher could give a clue as to what is happening.
Paul
> On 24 Mar 2017, at 08:00, Bob Sneidar via use-livecode
> wrote:
>
11 matches
Mail list logo
