Pulling the fullclipboarddata could end up doing a bit of work depending on
what is on it. You would probably be better off using the rawclipboarddata to
avoid LC doing any processing just so you can detect changes.
Under normal circumstances, the various flavors of content will reflect the
update on this the memory consumption is definately to do with one of
the messages that checks for changes in the clipboard every 333
milliseconds.. but does not retain what it finds.
there is nothing else going on the computer and as far as i know the
clipboard ISN't changingdoes
:-)
> On Jul 9, 2018, at 08:30 , Tom Glod via use-livecode
> wrote:
>
> Hey BobI rarely do anything without waiting 0 milliseconds. :P
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe
Hey BobI rarely do anything without waiting 0 milliseconds. :P
On Mon, Jul 9, 2018 at 11:04 AM, Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:
> It may help to put a wait x milliseconds with messages in the repeat loop.
> This will give the engine a chance to do
It may help to put a wait x milliseconds with messages in the repeat loop. This
will give the engine a chance to do housecleaning.
Bob S
> On Jul 7, 2018, at 16:15 , Tom Glod via use-livecode
> wrote:
>
> Hi folks,
>
> I have a stack that has 2 or 3 self perpetuating messages which do a
Hi Douglas and Jaquie thank you for your input..I have double checked
my code and indeed my loop is safe from overlapping messagesI've been
working with schedulers for a while... still not sure what could be
causing it..but it doesn't seem to get out of hand and clears itself out
On 7/8/18 12:06 PM, Mike Bonner via use-livecode wrote:
Or alternatively, check the pendingmessages and only send if there is not
already a message for the handler in question in queue.
Like you, this is something I always do:
if "myMsg" is not in the pendingMessages then
send "myMsg" to me
Or alternatively, check the pendingmessages and only send if there is not
already a message for the handler in question in queue.
I've had situations (in my case, bad coding) where I thought I was starting
a looping handler once ,but had left a call to that handler elsewhere
accidentally during
To help determine if Brian's suggestion is occurring, you could put the
following line in your "self perpetuating" code (assuming you're not running
the code on a Mobile device which have no "messsage box") just before the
"send... in x time ":
put the pendingmessages
If you see ANY output,
Is it possible that multiple overlapping messages are being spawned?
You mention that the checks happen every 250ms... are you doing a send in time
at the end of the check or at the start?
Thanks,
Brian
On Jul 7, 2018, 7:21 PM -0400, Tom Glod via use-livecode
, wrote:
> So i've been watching
So i've been watching this running standalone a while and it seems to
have stopped for now...I'm going to keep it running and see how high up it
gets.
Its like the engine is caching system events or something I'll post
again in a few hours to see if its gotten any higher than this.
Hi folks,
I have a stack that has 2 or 3 self perpetuating messages which do a few
checks and the likethey run every 250 milliseconds or so.
There is no input data into the program unless I specifically send it there.
but while my program is sitting there repeating its loops and checks
12 matches
Mail list logo
