Re: Purge a stack from memory

2019-07-26 Thread doc hawk via use-livecode

On Jul 26, 2019, at 3:40 PM, Bob Sneidar via use-livecode 
 wrote:
> 
> K!

Don’t be scared.

Be *very* scared . . .

There is something wonky about the whole  in and out of memory thing.

My  project is (during development) a bunch of   main s tacks,   with an mcp  
to  rule  them all .  . .

Anyway, when I bump the version of one of them that has already been used,  
something seems to stick around, so that I get an endless cycle of the two  
stacks causing popups asking what to do with the other.

I’ve taking to quitting livecode after bumping and just plain reloading . . .


___
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

Re: Purge a stack from memory

2019-07-26 Thread Bob Sneidar via use-livecode
K!

Bob S


> On Jul 26, 2019, at 13:25 , J. Landman Gay via use-livecode 
>  wrote:
> 
> The word you want is "delete" but you will have to be careful. If you delete 
> an open mainstack, it is purged from memory without saving, but the file 
> remains intact on disk. However if you delete a substack, it is removed from 
> the mainstack and if you subsequently save its mainstack the substack is gone 
> forever. So you will need to delete the mainstack first before opening the 
> mainstack B that contains substack X.
> 
> If they are both open at the same time who knows which one will be targeted 
> for deletion.
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com


___
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


Re: Purge a stack from memory

2019-07-26 Thread J. Landman Gay via use-livecode
The word you want is "delete" but you will have to be careful. If you 
delete an open mainstack, it is purged from memory without saving, but the 
file remains intact on disk. However if you delete a substack, it is 
removed from the mainstack and if you subsequently save its mainstack the 
substack is gone forever. So you will need to delete the mainstack first 
before opening the mainstack B that contains substack X.


If they are both open at the same time who knows which one will be targeted 
for deletion.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On July 26, 2019 2:09:59 PM Paul Dupuis via use-livecode 
 wrote:



I know this comes up again and again, is there some counterpart to
"revLoadedStacks(application)" that can PURGE a stack from memory?

If you have a stack open, say stack "A" and you open a different stack
file with a stack called "A", the IDE presents a message about stacks
with the same name and what do you want to do with essentially "Cancel"
(opening the new stack) or "Purge" (the old stack without saving) or
"Save" (the old stack and purge)

What does the IDE do to purge a stack?

I ask as I have the following case:

I have a stack open in the IDE (Call it "A") that uses another stack
(not a substack), call it "X" as a library stack. That stack needs to
make a scripted change to another mainstack (call it "B") with a
substack, also  it "X", with the same name as the library stack (yes,
the naming could have been better, but these are old stack made by
different people and renaming stuff would be a real pain in the butt)

I have tried:
stop using stack "X"
set the destroyStack of stack "X" to true
close stack "X"
wait 0 with messages -- give time to close and remove the stack from memory

-- then open the other stack "X"
-- and do what I need

Yet when I try this, I get the IDE message about stacks of the same name.

Any tips on how to positively, absolutely purge a stack from memory?

___
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





___
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


Purge a stack from memory

2019-07-26 Thread Paul Dupuis via use-livecode
I know this comes up again and again, is there some counterpart to 
"revLoadedStacks(application)" that can PURGE a stack from memory?


If you have a stack open, say stack "A" and you open a different stack 
file with a stack called "A", the IDE presents a message about stacks 
with the same name and what do you want to do with essentially "Cancel" 
(opening the new stack) or "Purge" (the old stack without saving) or 
"Save" (the old stack and purge)


What does the IDE do to purge a stack?

I ask as I have the following case:

I have a stack open in the IDE (Call it "A") that uses another stack 
(not a substack), call it "X" as a library stack. That stack needs to 
make a scripted change to another mainstack (call it "B") with a 
substack, also  it "X", with the same name as the library stack (yes, 
the naming could have been better, but these are old stack made by 
different people and renaming stuff would be a real pain in the butt)


I have tried:
stop using stack "X"
set the destroyStack of stack "X" to true
close stack "X"
wait 0 with messages -- give time to close and remove the stack from memory

-- then open the other stack "X"
-- and do what I need

Yet when I try this, I get the IDE message about stacks of the same name.

Any tips on how to positively, absolutely purge a stack from memory?

___
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

Re: 9.5 rc1 copy file lag

2019-07-26 Thread Dar Scott Consulting via use-livecode
I seem to be getting silent failures with externals and "unexpected libffi 
error" with LiveCode Builder libraries that use foreign functions.

I wonder if we are doing something wrong with 64-bit LiveCode.


> On Jul 26, 2019, at 11:00 AM, Stephen MacLean via use-livecode 
>  wrote:
> 
> Hi All,
> 
> Just downloaded the LC 9.5 RC1 (Business) 64 bit yesterday and am now seeing 
> a lot of lagging or hanging when using revCopyFile that I haven’t seen in 
> past releases. It’s really noticeable when I have this running in the 
> background in the IDE, and doing something else in the foreground.
> 
> Once the current run is complete, I’ll try 9.05 RC1 as well. This wasn’t an 
> issue with 9.02.
> 
> If you’ve seen this as well, please let me know.
> 
> Best,
> 
> Steve MacLean
> ___
> 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
> 


___
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

9.5 rc1 copy file lag

2019-07-26 Thread Stephen MacLean via use-livecode
Hi All,

Just downloaded the LC 9.5 RC1 (Business) 64 bit yesterday and am now seeing a 
lot of lagging or hanging when using revCopyFile that I haven’t seen in past 
releases. It’s really noticeable when I have this running in the background in 
the IDE, and doing something else in the foreground.

Once the current run is complete, I’ll try 9.05 RC1 as well. This wasn’t an 
issue with 9.02.

If you’ve seen this as well, please let me know.

Best,

Steve MacLean
___
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

Re: OSX High Sierra and Mojave Double Titlebars or Menubars?

2019-07-26 Thread Paul Dupuis via use-livecode

https://quality.livecode.com/show_bug.cgi?id=22267

We have a screen recording showing the issue (but not what triggered 
it!) that, when I can get it form the QA person who recorded it, I will 
post to the bug report.


In a strange way it is comforting to know some one else is seeing this 
issue too.



On 7/26/2019 11:38 AM, J. Landman Gay via use-livecode wrote:
I don't see the problem either but my client does. She can't work with 
our stacks and we probably shouldn't ship if it's a widespread issue. 
Her symptoms are identical to what you describe.


Please write up a bug report and if I can get more info from her I'll 
add to it. We have a hard deadline in about 3 weeks.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On July 26, 2019 9:16:10 AM Paul Dupuis via use-livecode 
 wrote:



On 7/26/2019 12:17 AM, Trevor DeVore via use-livecode wrote:

On Thu, Jul 25, 2019 at 4:05 PM Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:


I recall a recent (last year/this year - I think) bug where under OSX
High Sierra or Mojave you could end up with double titlebars in your
windows or perhaps it was double menubars?

I have spent a big chunk of time searching the Livecode Quality Center
and can not find this bug.

Am I delusional, or was there such a bug and if, so can someone 
point me

to it?


This? https://quality.livecode.com/show_bug.cgi?id=20923



Yes, thank you. In LiveCode 905rc1 in Standalones on OSX High Sierra we
are seeing an odd behavior where -- something happens -- and the mouse
position in a window (or a multi-window standalone) is displaced
vertically. When you click or drag, LiveCode thinks - just in the window
- that the mouse is about 20-30 px above where it currently is.

If you move the mouse out of the affected window to another window, it
is fine. But if you move it back into the effected window, it is still
displaced. If you move the window (aligned by default just under the
menubar) down by the displacement amount, the displacement goes away.
Move the window back up, the displacement returns.

Restart the app and it goes away -- until it occurs again.

It is not in our code and happen in different windows at different
times. It is definitely an LiveCode bug, but we can not create/discover
a recipe for what triggers the bug. It has been suggested that it might
be related to the double titlebars bug or to a bug where the LiveCode
IDE menubar/pallete cause an similar displacement in the IDE. However,
this is in a standalone.

It's driving us batty since we can't ship our app with this bug and
can't get LiveCode to even consider fixing it until we can produce a
test stack with a recipe to reproduce it!



___
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





___
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




___
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


Re: OSX High Sierra and Mojave Double Titlebars or Menubars?

2019-07-26 Thread Paul Dupuis via use-livecode

On 7/26/2019 11:22 AM, Trevor DeVore via use-livecode wrote:

On Fri, Jul 26, 2019 at 9:14 AM Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:


Yes, thank you. In LiveCode 905rc1 in Standalones on OSX High Sierra we
are seeing an odd behavior where -- something happens -- and the mouse
position in a window (or a multi-window standalone) is displaced
vertically. When you click or drag, LiveCode thinks - just in the window
- that the mouse is about 20-30 px above where it currently is.


Do you know if the window opens up with the vertical displacement issue or
is the user interacting with the window without issue and then the vertical
displacement is somehow triggered?



The windows are open and then the problem is some how triggered. 
Sometime it happens soon after a window is open and sometime much later.




___
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


Re: OSX High Sierra and Mojave Double Titlebars or Menubars?

2019-07-26 Thread J. Landman Gay via use-livecode
I don't see the problem either but my client does. She can't work with our 
stacks and we probably shouldn't ship if it's a widespread issue. Her 
symptoms are identical to what you describe.


Please write up a bug report and if I can get more info from her I'll add 
to it. We have a hard deadline in about 3 weeks.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On July 26, 2019 9:16:10 AM Paul Dupuis via use-livecode 
 wrote:



On 7/26/2019 12:17 AM, Trevor DeVore via use-livecode wrote:

On Thu, Jul 25, 2019 at 4:05 PM Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:


I recall a recent (last year/this year - I think) bug where under OSX
High Sierra or Mojave you could end up with double titlebars in your
windows or perhaps it was double menubars?

I have spent a big chunk of time searching the Livecode Quality Center
and can not find this bug.

Am I delusional, or was there such a bug and if, so can someone point me
to it?


This? https://quality.livecode.com/show_bug.cgi?id=20923



Yes, thank you. In LiveCode 905rc1 in Standalones on OSX High Sierra we
are seeing an odd behavior where -- something happens -- and the mouse
position in a window (or a multi-window standalone) is displaced
vertically. When you click or drag, LiveCode thinks - just in the window
- that the mouse is about 20-30 px above where it currently is.

If you move the mouse out of the affected window to another window, it
is fine. But if you move it back into the effected window, it is still
displaced. If you move the window (aligned by default just under the
menubar) down by the displacement amount, the displacement goes away.
Move the window back up, the displacement returns.

Restart the app and it goes away -- until it occurs again.

It is not in our code and happen in different windows at different
times. It is definitely an LiveCode bug, but we can not create/discover
a recipe for what triggers the bug. It has been suggested that it might
be related to the double titlebars bug or to a bug where the LiveCode
IDE menubar/pallete cause an similar displacement in the IDE. However,
this is in a standalone.

It's driving us batty since we can't ship our app with this bug and
can't get LiveCode to even consider fixing it until we can produce a
test stack with a recipe to reproduce it!



___
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





___
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


Re: OSX High Sierra and Mojave Double Titlebars or Menubars?

2019-07-26 Thread Trevor DeVore via use-livecode
On Fri, Jul 26, 2019 at 9:14 AM Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:

>
> Yes, thank you. In LiveCode 905rc1 in Standalones on OSX High Sierra we
> are seeing an odd behavior where -- something happens -- and the mouse
> position in a window (or a multi-window standalone) is displaced
> vertically. When you click or drag, LiveCode thinks - just in the window
> - that the mouse is about 20-30 px above where it currently is.


Do you know if the window opens up with the vertical displacement issue or
is the user interacting with the window without issue and then the vertical
displacement is somehow triggered?

-- 
Trevor DeVore
ScreenSteps

>
___
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


Re: OSX High Sierra and Mojave Double Titlebars or Menubars?

2019-07-26 Thread Paul Dupuis via use-livecode

On 7/26/2019 12:17 AM, Trevor DeVore via use-livecode wrote:

On Thu, Jul 25, 2019 at 4:05 PM Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:


I recall a recent (last year/this year - I think) bug where under OSX
High Sierra or Mojave you could end up with double titlebars in your
windows or perhaps it was double menubars?

I have spent a big chunk of time searching the Livecode Quality Center
and can not find this bug.

Am I delusional, or was there such a bug and if, so can someone point me
to it?


This? https://quality.livecode.com/show_bug.cgi?id=20923



Yes, thank you. In LiveCode 905rc1 in Standalones on OSX High Sierra we 
are seeing an odd behavior where -- something happens -- and the mouse 
position in a window (or a multi-window standalone) is displaced 
vertically. When you click or drag, LiveCode thinks - just in the window 
- that the mouse is about 20-30 px above where it currently is.


If you move the mouse out of the affected window to another window, it 
is fine. But if you move it back into the effected window, it is still 
displaced. If you move the window (aligned by default just under the 
menubar) down by the displacement amount, the displacement goes away. 
Move the window back up, the displacement returns.


Restart the app and it goes away -- until it occurs again.

It is not in our code and happen in different windows at different 
times. It is definitely an LiveCode bug, but we can not create/discover 
a recipe for what triggers the bug. It has been suggested that it might 
be related to the double titlebars bug or to a bug where the LiveCode 
IDE menubar/pallete cause an similar displacement in the IDE. However, 
this is in a standalone.


It's driving us batty since we can't ship our app with this bug and 
can't get LiveCode to even consider fixing it until we can produce a 
test stack with a recipe to reproduce it!




___
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


Re: OSX High Sierra and Mojave Double Titlebars or Menubars?

2019-07-26 Thread Trevor DeVore via use-livecode
On Thu, Jul 25, 2019 at 4:05 PM Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:

> I recall a recent (last year/this year - I think) bug where under OSX
> High Sierra or Mojave you could end up with double titlebars in your
> windows or perhaps it was double menubars?
>
> I have spent a big chunk of time searching the Livecode Quality Center
> and can not find this bug.
>
> Am I delusional, or was there such a bug and if, so can someone point me
> to it?
>

This? https://quality.livecode.com/show_bug.cgi?id=20923

-- 
Trevor DeVore
ScreenSteps
www.screensteps.com
___
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


Re: Time-outs in LC Server?

2019-07-26 Thread Alex Tweedly via use-livecode
Great!  So glad you got to a successful conclusion.
Alex 

Sent from my iPhone

> On 25 Jul 2019, at 17:12, Rick Harrison via use-livecode 
>  wrote:
> 
> Hi Alex,
> 
> The solution turned out to be easier with no time checks involved.
> 
> I noticed that one of my variables ends up being blank when the
> server times out.  So when the user attempts to do something,
> the destination webpage performs a check at the beginning of 
> the code to see if the variable is blank.  If it’s blank, I have
> alternate code appear that tells the user they have been logged
> out due to inactivity, and offers a dismiss message button that
> links back to the login page.  It works quite nicely, and
> I don’t have to check for every transaction in every format file.
> 
> Enjoy your day!
> 
> Rick
> 
> 
> 
>> On Jul 19, 2019, at 9:47 PM, Alex Tweedly via use-livecode 
>>  wrote:
>> 
>> 
>>> On 19/07/2019 14:28, Rick Harrison via use-livecode wrote:
>>> The following is a link to the javascript stuff I had referred
>>> to before.  I just want a clean LC way to do the same thing.
>>> 
>>> https://stackoverflow.com/questions/9564602/how-to-know-browser-idle-time?noredirect=1&lq=1
>>> 
>> Sorry to be the bearer of bad news, but there is no such thing, and indeed, 
>> there cannot be!
>> 
>> That javascript code runs *in the user's browser", and so can easily keep 
>> track of idle time. or remaining time
>> 
>> Your LC code can only run on the server. And on the server, all you can do 
>> is - at the start of responding to a request - check how long it has been 
>> since the previous request from same user.
>> 
>> So that requires some storage between requests - whether in a database, or 
>> via cookie / session variable.
>> 
>> Alex.
>> 
>> 
>> ___
>> 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
> 
> 
> ___
> 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


___
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