variable window not applying changes

[James Hale via use-livecode]

Hi,

I have been tracing a script and while stepping through notice an error in a 
variable.
I double clicked on the value in the variable list at the bottom of the SE 
window and brought up the variable window.
Made the  correction and clicked "apply".

Nothing happened.

This used to work, didn't it??

James



___
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

Pattern ID bug

[Neville Smythe via use-livecode]

Try setting the backgroundPattern of a button to ID 141, either from a script, 
or by using the Image Library chooser and going to the MetaCard Compatible 
Patterns, look for ID 141 which is small image of dots on the second page.

What you get, at least on my Mac with LC9.6.5, is a pattern of red leaves which 
is image id 236 (tho also weirdly id 277). Similar things happen with id 142 
and others.

I came across this while trying to write an ImagePicker for the 
nsPropertyMapper plugin which would improve on the built -in Image Library 
Chooser, which frankly I thought couldn’t be all that hard. I find I need to 
bypass the way LC finds pattern and icon images when all it has an ID (I guess 
this is a legacy from Hypercard), rather than a full reference to an image; the 
ID is by no means unique even within built-in rev image libraries - though 
actually 141 is unique in this case so that is not the explanation for the bug. 
I had to fool around with behaviors to force the LC search path and thought at 
first I must have corrupted the revIcons or revGeneralPatterns stacks. But I 
get the same bug on a fresh install on a completely different Mac.

Neville
___
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: [ANN] Release 10.0.0 DP-1

[William de Smet via use-livecode]

Been playing all day with LC 10 DP-1 and mostly testing Web/html5 and I can
confirm Firefox is also the fastest in WASM on a remote webserver.
Safari is the slowest. Most people I know use the Chrome browser however.
On Chrome OS speed varies depending on the state of the Chromebook (age).


Op di 23 nov. 2021 om 14:14 schreef Andre Garzia via use-livecode <
use-livecode@lists.runrev.com>:

> Brave, Edge, and Chrome are all using the same engine. They should perform
> the same. IIRC Firefox still has the best WASM performance, mostly because
> it was invented there and they had more time to optimize.
>
> That the way the web browsers works is that "they really hate opening local
> HTML files with file:// protocol". Opening a file like that will switch on
> a lot of protection in the browser and restrict many APIs. The correct way
> to test WASM files is by running a local web server and opening it using
> HTTPS (or HTTP if you must).
>
> Be aware that the most important change regarding performance between WASM
> and the previous ASM.JS based engine will not be visible when running a
> local server. To load an ASM.JS based webapp, the browser needs to fetch
> all the files before loading them into memory and parsing them. The new
> WASM technology allows a browser to load the files while the transfer still
> happening. It is a streaming kind of tech. This means that besides all the
> other benefits, you don't need to deal with the latency of waiting for
> transfers to complete before the app starts to load. When running locally,
> the transfer is so fast that you can see this benefit, but try placing
> those files in a remote server and the difference should be night and day,
> specially for really large builds.
>
> On Tue, 23 Nov 2021 at 09:34, Bernard Devlin via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
> > Thanks Panos. That kind of works. It always opens in the default browser
> > i.e. trying to select another browser as the test target has no effect.
> Is
> > this a known bug?
> >
> > From test/save with browser closed (compile to standalone, then let IDE
> > launch browser):
> > Load time LC 10 - 5 secs
> > Load time LC 9.6.1 - 7 secs
> >
> > Loading same saved stack with browser already open (re-using URL):
> > Load time LC 10 - 2 secs
> > Load time LC 9.6.1 - 5 secs
> >
> > I tested with both Brave and Edge, but couldn't detect any difference in
> > load speed between them.
> >
> > These tests were just wall clock time.
> >
> > On Mon, Nov 22, 2021 at 3:48 PM panagiotis m via use-livecode <
> > use-livecode@lists.runrev.com> wrote:
> >
> > > Hello Bernard,
> > >
> > > Trying to open the local html file will fail due to CORS - Firefox may
> or
> > > may not work - I think it needs some tweaks, and not sure if this is
> > still
> > > possible in the latest versions. We probably need to update this
> lesson.
> > >
> > > The correct way to test is to use the Development -> Test Target ->
> >  > > your browser> and then Development -> Test
> > >
> > > Hope this helps.
> > >
> > > Panos
> > > --
> > >
> > >
> > ___
> > 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
> >
>
>
> --
> https://www.andregarzia.com 
> Want to support me? Buy me a coffee at https://ko-fi.com/andregarzia
> ___
> 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: [ANN] Release 10.0.0 DP-1

[Andre Garzia via use-livecode]

Brave, Edge, and Chrome are all using the same engine. They should perform
the same. IIRC Firefox still has the best WASM performance, mostly because
it was invented there and they had more time to optimize.

That the way the web browsers works is that "they really hate opening local
HTML files with file:// protocol". Opening a file like that will switch on
a lot of protection in the browser and restrict many APIs. The correct way
to test WASM files is by running a local web server and opening it using
HTTPS (or HTTP if you must).

Be aware that the most important change regarding performance between WASM
and the previous ASM.JS based engine will not be visible when running a
local server. To load an ASM.JS based webapp, the browser needs to fetch
all the files before loading them into memory and parsing them. The new
WASM technology allows a browser to load the files while the transfer still
happening. It is a streaming kind of tech. This means that besides all the
other benefits, you don't need to deal with the latency of waiting for
transfers to complete before the app starts to load. When running locally,
the transfer is so fast that you can see this benefit, but try placing
those files in a remote server and the difference should be night and day,
specially for really large builds.

On Tue, 23 Nov 2021 at 09:34, Bernard Devlin via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Thanks Panos. That kind of works. It always opens in the default browser
> i.e. trying to select another browser as the test target has no effect.  Is
> this a known bug?
>
> From test/save with browser closed (compile to standalone, then let IDE
> launch browser):
> Load time LC 10 - 5 secs
> Load time LC 9.6.1 - 7 secs
>
> Loading same saved stack with browser already open (re-using URL):
> Load time LC 10 - 2 secs
> Load time LC 9.6.1 - 5 secs
>
> I tested with both Brave and Edge, but couldn't detect any difference in
> load speed between them.
>
> These tests were just wall clock time.
>
> On Mon, Nov 22, 2021 at 3:48 PM panagiotis m via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
> > Hello Bernard,
> >
> > Trying to open the local html file will fail due to CORS - Firefox may or
> > may not work - I think it needs some tweaks, and not sure if this is
> still
> > possible in the latest versions. We probably need to update this lesson.
> >
> > The correct way to test is to use the Development -> Test Target ->
>  > your browser> and then Development -> Test
> >
> > Hope this helps.
> >
> > Panos
> > --
> >
> >
> ___
> 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
>


-- 
https://www.andregarzia.com 
Want to support me? Buy me a coffee at https://ko-fi.com/andregarzia
___
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: [ANN] Release 10.0.0 DP-1

[Bernard Devlin via use-livecode]

Thanks Panos. That kind of works. It always opens in the default browser
i.e. trying to select another browser as the test target has no effect.  Is
this a known bug?

>From test/save with browser closed (compile to standalone, then let IDE
launch browser):
Load time LC 10 - 5 secs
Load time LC 9.6.1 - 7 secs

Loading same saved stack with browser already open (re-using URL):
Load time LC 10 - 2 secs
Load time LC 9.6.1 - 5 secs

I tested with both Brave and Edge, but couldn't detect any difference in
load speed between them.

These tests were just wall clock time.

On Mon, Nov 22, 2021 at 3:48 PM panagiotis m via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Hello Bernard,
>
> Trying to open the local html file will fail due to CORS - Firefox may or
> may not work - I think it needs some tweaks, and not sure if this is still
> possible in the latest versions. We probably need to update this lesson.
>
> The correct way to test is to use the Development -> Test Target ->  your browser> and then Development -> Test
>
> Hope this helps.
>
> Panos
> --
>
>
___
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