DP13 breaks GLX framework

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

DP13 breaks GLX framework

jameshale
Hopefully there are people out there who have a more intimate knowledge of the GLX framework than I.
Opening a GLX based app with DP13 hits a snag in the last handler just before the launcher is dismissed.
Consequently no preopenwindow handler makes it to the main app stack and necessary set up routines do not happen.
All versions of LC8 up until this point have proceeded without incident.
Something has changed in DP13.
Reply | Threaded
Open this post in threaded view
|

Re: DP13 breaks GLX framework

jameshale
ok, the error I am getting is"
button "glxappManagedEngineMessages": execution error at line 7342 (Chunk: can't find background), char 9

I can of course not find a line 7342 in a script that has only 279 lines.
The button referred to is in the 'scripts' card in a group 'frontscripts' of the 'glxapplicationframework.dat' stack.

The calling chain is...
glxApplicationFramework ->glxapp_loadApplication
application->glxapp_openApplication
glxappManagedEngineMessages->preopenstack

I have tried tracing the path but it seems to be all ok. I can't find any error, but see below.

If I launch and kill the handler when the script debugger comes up and then call my "PreOpenWindow" handler (which resides in my main stack "program") then my app completes its correct loading sequence and all is fine.
Note: before I do this my main stack has opened, it is just not initialised.
Running the preopenwindow handler completes the initialisation.

While tracing the launch progress there are many 'try..catch..end try' blocks.
They are all quite simple and of the form..
       try
          some handler or function call
       catch e
          ThrowError e
       end TRY

In almost quite a few cases I would go to the "ThrowError e" line and into the 'ThrowError' handler.
However nothing is in the 'e' parameter, at least nothing until the end.
Reply | Threaded
Open this post in threaded view
|

Re: DP13 breaks GLX framework

Trevor DeVore
On Thursday, January 14, 2016, jameshale <[hidden email]> wrote:

> ok, the error I am getting is"
> button "glxappManagedEngineMessages": execution error at line 7342 (Chunk:
> can't find background), char 9
>
> I can of course not find a line 7342 in a script that has only 279 lines.
> The button referred to is in the 'scripts' card in a group 'frontscripts'
> of
> the 'glxapplicationframework.dat' stack.
>

James,

Does your stack (or card) script have a line 7342? Look and see if that
line is trying to reference an object that doesn't exist.

--
Trevor DeVore
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: DP13 breaks GLX framework

Ali Lloyd-2
In reply to this post by jameshale
I can confirm this is a DP 13 regression, caused by the fix to bug 16351 (
https://github.com/livecode/livecode/pull/3448)

The error is occurring in the data grid behavior.

I think problem is something to do with 'the target' and 'me' evaluating to
different things in a context where they should evaluate to the same thing.

On Thu, Jan 14, 2016 at 1:20 PM jameshale <[hidden email]> wrote:

> ok, the error I am getting is"
> button "glxappManagedEngineMessages": execution error at line 7342 (Chunk:
> can't find background), char 9
>
> I can of course not find a line 7342 in a script that has only 279 lines.
> The button referred to is in the 'scripts' card in a group 'frontscripts'
> of
> the 'glxapplicationframework.dat' stack.
>
> The calling chain is...
> glxApplicationFramework ->glxapp_loadApplication
> application->glxapp_openApplication
> glxappManagedEngineMessages->preopenstack
>
> I have tried tracing the path but it seems to be all ok. I can't find any
> error, but see below.
>
> If I launch and kill the handler when the script debugger comes up and then
> call my "PreOpenWindow" handler (which resides in my main stack "program")
> then my app completes its correct loading sequence and all is fine.
> Note: before I do this my main stack has opened, it is just not
> initialised.
> Running the preopenwindow handler completes the initialisation.
>
> While tracing the launch progress there are many 'try..catch..end try'
> blocks.
> They are all quite simple and of the form..
>        try
>           some handler or function call
>        catch e
>           ThrowError e
>        end TRY
>
> In almost quite a few cases I would go to the "ThrowError e" line and into
> the 'ThrowError' handler.
> However nothing is in the 'e' parameter, at least nothing until the end.
>
>
>
> --
> View this message in context:
> http://runtime-revolution.278305.n4.nabble.com/DP13-breaks-GLX-framework-tp4700166p4700169.html
> Sent from the Revolution - User mailing list archive at Nabble.com.
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: DP13 breaks GLX framework

jameshale
Aha.
Thanks Ali.
Does a bug report need to be generated?
(Well, actually will you be entering one given you know what it is?)
Reply | Threaded
Open this post in threaded view
|

Re: DP13 breaks GLX framework

Jim L.

I don’t know if this is related but I’m seeing both a tree view widget and a browser widget disappear from my application on startup in the IDE.  

Jim L


On Jan 14, 2016, at 7:00 AM, jameshale <[hidden email]> wrote:

> Aha.
> Thanks Ali.
> Does a bug report need to be generated?
> (Well, actually will you be entering one given you know what it is?)
>
>
>
> --
> View this message in context: http://runtime-revolution.278305.n4.nabble.com/DP13-breaks-GLX-framework-tp4700166p4700176.html
> Sent from the Revolution - User mailing list archive at Nabble.com.
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Widgets Disappear in DP13

Jim L.

Using 8.0 DP13 on a Mac, a Tree View widget and a Browser widget disappear when the app is saved and then re-opened in the IDE.  I’ve just confirmed this with a new test stack.  I saw this yesterday in the regular app that I’m working on.  The widgets are no longer present in the Project Browser either.  

Jim L

 
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Widgets Disappear in DP13

Peter TB Brett
On 2016-01-14 22:46, James Little wrote:
> Using 8.0 DP13 on a Mac, a Tree View widget and a Browser widget
> disappear when the app is saved and then re-opened in the IDE.  I’ve
> just confirmed this with a new test stack.  I saw this yesterday in
> the regular app that I’m working on.  The widgets are no longer
> present in the Project Browser either.

Hmm, yes, this sounds like it's probably my bug -- I think your stack
might be getting saved in 7.0 stack format, which doesn't know how to
store widgets.

Could you please file a bug report with the steps to reproduce (and the
affected stack, if possible?)

As a workaround, you could try using:

     save the mousestack with newest format

in the message box (with your mouse over the stack in question) to force
it to be saved in 8.0 stack format.

                                        Peter

--
Dr Peter Brett <[hidden email]>
LiveCode Open Source Team

LiveCode on reddit! <https://reddit.com/r/livecode>

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: DP13 breaks GLX framework

jameshale
In reply to this post by Trevor DeVore
Hi Trevor,
The only script I can see over 7000 lines is sqlYoga.
All my calls to this library take place after my preopenwindow handler and as mentioned, when run from the message box it goes without issue. The app seems to function fine from this point with functions that use sqlYoga working as expected.
I feel Ali might be able n the right track as while tracing through the GLX routines I noticed they relied heavily on the 'target'.
Reply | Threaded
Open this post in threaded view
|

Re: Widgets Disappear in DP13

Peter TB Brett
In reply to this post by Jim L.


On 14/01/2016 22:46, James Little wrote:
>
> Using 8.0 DP13 on a Mac, a Tree View widget and a Browser widget disappear when the app is saved and then re-opened in the IDE.  I’ve just confirmed this with a new test stack.  I saw this yesterday in the regular app that I’m working on.  The widgets are no longer present in the Project Browser either.
>

Hi Jim,

I'm looking into this at the moment.  Unfortunately, I haven't been able
to reproduce the problem.  I used the following steps:

1. Install LiveCode 8.0.0 DP 13 Community Edition, on Mac OS X 10.11.2.

2. Open the IDE, and create a new stack

3. Drag a treeview widget onto the stack

4. Save the stack as "SaveTest.livecode"

5. Close the IDE, and reopen it.

6. Open "SaveTest.livecode"

When I do that, the treeview widget is still present.  Have I missed
something?  I'd really like to fix this for you. :-)

                                   Peter

--
Dr Peter Brett <[hidden email]>
LiveCode Open Source Team

LiveCode on reddit: https://reddit.com/r/livecode

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Widgets Disappear in DP13

Peter TB Brett
In reply to this post by Jim L.


On 14/01/2016 22:46, James Little wrote:
>
> Using 8.0 DP13 on a Mac, a Tree View widget and a Browser widget disappear when the app is saved and then re-opened in the IDE.  I’ve just confirmed this with a new test stack.  I saw this yesterday in the regular app that I’m working on.  The widgets are no longer present in the Project Browser either.

This is an engine bug which occurs when you have a widget in a substack,
but no widget in the main stack.

http://quality.livecode.com/show_bug.cgi?id=16738

You can work around it by adding a widget to the main stack and making
it invisible.

                                 Peter


--
Dr Peter Brett <[hidden email]>
LiveCode Open Source Team

LiveCode on reddit: https://reddit.com/r/livecode

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode