where is "Function sWindowsA"

[James Hale]

Hi Trevor,

While debugging some of my handlers I turned to the message watcher to try and see what was going on.

Whenever I go to another card in my stack I see that the framework executes the following two handlers:

window_isManaged

window_isCardInit

Invariably following this there is either 1 or 2 "ThrowError" messages.

Looking at the handlers in question I placed a "put e" in the "window_isCardInit" handler.

it was #573, "Handler: can't find handler"

So I went back to have a look at "window_isCardInit" and the only handler being called is the function "sWindowsA".

I then did a global (all open stack files) search and came up with nothing.

I also manually opened every script I could find in the framework and still couldn't see it.

It seems this function doesn't exist.

The ThrowError messages do not seem to cause any problem but I am just wondering if this function is indeed missing, if it is required or perhaps has its name been changed and this line was missed.

Do I need to be concerned?

James

[Trevor DeVore]

On Sat, Mar 29, 2014 at 9:39 AM, James Hale <ja...@thehales.id.au> wrote:

Whenever I go to another card in my stack I see that the framework executes the following two handlers:

window_isManaged

window_isCardInit

Invariably following this there is either 1 or 2 "ThrowError" messages.

Looking at the handlers in question I placed a "put e" in the "window_isCardInit" handler.

it was #573, "Handler: can't find handler"

So I went back to have a look at "window_isCardInit" and the only handler being called is the function "sWindowsA".

sWindowsA is a script local variable, not a function.

Are you sure the error is in window_isCardInit()? Do you have OpenView, PreOpenView, Resizeview, etc. handlers defined in your card or stack script that could be triggering the error? If you add breakpoints to the glxappManagedEngineMessages frontscript then may be able to step through the code to get a better idea of where the error is.

-- 

Trevor DeVore

Blue Mango Learning Systems

www.screensteps.com    -    www.clarify-it.com 

[James Hale]

OK.

Since posting I have been reexamining my code.

I had preopencard handlers which might be the source if the error.

I had placed in them some scripts that basically took changes from other cards and initialized the card in question to reflect what has been happening. Some of this initialization modified globals which were used in other places of the stack. Hence my wanting to run them.

As my stack got more complicated rather than modifying these scripts I just left them in situ and called the preopen handlers to run them but without actually going to the card.

I suspect this is my error.

I removed all but the actual scripts required when the card is really being opened out of the preopen handler and called them from within it.

Then on my other cards/scripts I simply called these now external handlers so that I was not sending a bogus preopen to the card.

I haven't seen the error popup since. 

It doesn't quite explain the nature of the error "Can't find handler" but, as I said, it went away once I did the rearrangement.

Thanks for the reply.

James

[Trevor DeVore]

On Mon, Mar 31, 2014 at 9:13 AM, James Hale <ja...@thehales.id.au> wrote:

It doesn't quite explain the nature of the error "Can't find handler" but, as I said, it went away once I did the rearrangement.

I'm glad you got it working. I don't know that error reporting is always as accurate as it should be when using "send", which is what the front script does.