I never intended that handler to do anything but demonstrate how the
scrollWheel was linked to the rawkeyDown message. It is and was always
possible to pass rawKeyDown so that the keyboard was not crippled. I assumed
everyone knew that.
There is a thread on the forums, "keysDown works across appli
Thank you, Craig and Mike, for your responses. But the problem with the
rawKeyDown message is that the mouse needs to be in the LiveCode window. I can
scroll in my web browser all day and LiveCode wouldn’t ever notice. So
unfortunately this is not what I’m looking for.
Doing a feature request f
Have you tried to set the formatForPrinting of your stack to true?
Kind regards,
Mark Schonewille
http://economy-x-talk.com
https://www.facebook.com/marksch
Buy the most extensive book on the
LiveCode language:
http://livecodebeginner.economy-x-talk.com
Op 24-Dec-16 om 00:38 schreef Charles Sz
I was kicked form list again and missed a few messages.. Did someone
actually come up with an answer to detect scroll activity?
On Fri, Dec 23, 2016 at 4:17 PM, hh wrote:
> > Jacqueline LG wrote:
> > It doesn't seem logical to expect a "doScrollUpStuff" handler to also
> > manage all other keyst
I have a script for moving text from a text field to my app to a print card.
The text at the end of the first sentence runs into the beginning of text of
the second sentence when printing on Windows on LiveCode 6.1.3
I send the following problem to LC tech support and I got a message this is a
> Jacqueline LG wrote:
> It doesn't seem logical to expect a "doScrollUpStuff" handler to also
> manage all other keystrokes.
It's possibly "unusual" as naming has some conventions. But still
logical, why not? Nothing is blocked as long as we don't know what
doScrollUpStuff does.
Quentin derive
It doesn't seem logical to expect a "doScrollUpStuff" handler to also
manage all other keystrokes. One would expect the original rawKeyDown
handler to manage non-scroll keys by passing them to the engine.
If the intent is to block all keys except those used for scrolling, then
Craig's way woul
What you say is logically totally wrong.
"DoScrollUpStuff" may of course easily be written such that Craig's
script does the same as your script. And even more, for example
reader's exercises :-))
> Quentin L. wrote:
> sez dunbarx:
> > The "rawkeyDown" message may be trapped as follows:
> >
> >
More disabling today.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
sez dunbarx:
> The "rawkeyDown" message may be trapped as follows:
>
> on rawkeydown tkey
>if tkey = 65308 then doScrollDownStuff
>else doScrollUpStuff
> end rawkeydown
Hold it. That code, as written, will trap *A*L*L* rawKeyDown events, and
silently kill everything that's *not* a scrol
For those of us who don't speak regex, I'm glad it's easier than it looked.
On Fri, Dec 23, 2016 at 12:27 PM, Ali Lloyd wrote:
> It's not hard to fix. One way would be to add a function
>
> function escapeRegExp(str) {
> return str.replace(/[\-\[\]\/\{\}\(\)\*\+\?\.\\\^\$\|]/g, "\\$&");
> }
>
It's not hard to fix. One way would be to add a function
function escapeRegExp(str) {
return str.replace(/[\-\[\]\/\{\}\(\)\*\+\?\.\\\^\$\|]/g, "\\$&");
}
to dictionary_functions.js
and add the line
pTerm = escapeRegExp(pTerm);
to the dataSearch function here:
https://github.com/livecode/liv
did you try quoting the string instead of escaping it? I don't think this
is going to be trivial to fix without having at it, but I also haven't read
through the code in a month-plus.
On Thu, Dec 22, 2016 at 6:51 PM, Kay C Lan wrote:
> On Thu, Dec 22, 2016 at 10:45 PM, Mike Kerner
> wrote:
> >
On 23/12/2016 3:46 AM, Richard Gaskin wrote:
J. Landman Gay wrote:
> I did write about it but I hadn't tried it yet. You were right on
> the nose, that fixes it. I had to allow a short wait. This fails
> as before:
>
>tsNetClose
>quit
>
> But this works:
>
>tsNetClose
>wait 1 wi
14 matches
Mail list logo
