0
Fixed

Error when clicking on an element

Ranco 11 years ago updated by Inna Komarovsky 10 years ago 5
Many times, after moving from Iteract to Design, clicking any element will generate the following error (only restarting or moving back to "Manage" will solve the issue):
InteractBuilder Version: 3.3 Build 325
Device: System Product Name
Processor: 1 Processor(s) Installed.
[01]: x64 Family 6 Model 23 Stepping 10 GenuineIntel ~1999 Mhz
Memory: 3,327 MB
System: NT 6.1
--------------------
An application error occurred while attempting to perform the last action.
Restarting InteractBuilder is recommended.
An application error occurred while attempting to perform the last action.
Restarting InteractBuilder is recommended.
Error: Chunk: can't find background / Chunk: error in object expression / Chunk: can't find object / Object: does not have this property / put: error in expression
Handler: Element_SetBehaviorTarget
Hint:
Location: Line 0, char 1
Object: button id 1004 of card id 1002 of stack "Behaviors" of stack "C:/Program Files/InteractBuilder/Local Components/Data/InteractBuilder.livecode"
87: Line 0 at char 1: Chunk: can't find background
69: Line 6959 at char 58: Chunk: error in object expression ----> group id 8616567 of card id 1139 of stack "C:/Program Files/InteractBuilder/Local Components/Data/InteractBuilder.livecode"
77: Line 6959 at char 58: Chunk: can't find object
456: Line 6959 at char 8: Object: does not have this property
465: Line 6959 at char 1: put: error in expression
241: Line 6959 at char 1: Handler: error in statement ----> Element_SetBehaviorTarget
353: Line 0 at char 0: Object Name: ----> button id 1004 of card id 1002 of stack "Behaviors" of stack "C:/Program Files/InteractBuilder/Local Components/Data/InteractBuilder.livecode"
573: Line 7626 at char 1: Handler: can't find handler ----> Element_SetBehaviorTarget
253: Line 7612 at char 1: if-then: error in statement
587: Line 7609 at char 1: switch: error in statement
253: Line 7608 at char 1: if-then: error in statement
241: Line 7608 at char 1: Handler: error in statement ----> Element_TouchPointSelected
353: Line 0 at char 0: Object Name: ----> button id 1004 of card id 1002 of stack "Behaviors" of stack "C:/Program Files/InteractBuilder/Local Components/Data/InteractBuilder.livecode"
573: Line 7229 at char 1: Handler: can't find handler ----> Element_TouchPointSelected
253: Line 7166 at char 1: if-then: error in statement
253: Line 7152 at char 1: if-then: error in statement
241: Line 7152 at char 1: Handler: error in statement ----> Element_MouseDown
353: Line 0 at char 0: Object Name: ----> button id 1004 of card id 1002 of stack "Behaviors" of stack "C:/Program Files/InteractBuilder/Local Components/Data/InteractBuilder.livecode"
573: Line 44 at char 1: Handler: can't find handler ----> Element_MouseDown
253: Line 43 at char 1: if-then: error in statement
241: Line 43 at char 1: Handler: error in statement ----> mouseDown
353: Line 0 at char 0: Object Name: ----> button id 1020 of card id 1002 of stack "IBElements" of stack "C:/Program Files/InteractBuilder/Local Components/Data/InteractBuilder.livecode"
line 150 of handler "errorDialog" of button "stsErrors_FS" of card id 1002 of stack "libSTSErrors"
line 14245 of handler "DoError" of stack "InteractBuilder" of behavior button "Stack B" of card id 1002 of stack "Behaviors"

Answer

Answer
Under review
Can you give us more information about that element, if it got any behaviors or any specific settings?
Answer
Under review
Can you give us more information about that element, if it got any behaviors or any specific settings?
Well, it's not a specific element, it's every element I click. Nothing special, and it should be quite easy to reproduce because it happens A LOT. (maybe you should try on Windows...)
Ranco
From what I see from the code , I think that one behavior is missing it's target. It doesn't have neither an element as a target neither (self) or (none), it's just blank. Can you check to see if that is the case? 
No, sorry, it's not. Once it happens (when leaving interact mode to Design), no element can be clicked and edited. They all generate the same error.