1. When I publish from Flash Studio, I receive the following error message: Quote: 1152: A conflict exists with inherited definition scaleform.clik... in namespace public.
You are receiving this error because an element of the class is defined twice. This error message most often occurs when a .FLA is not set to disable"Automatically Declare Stage Instances" which causes a conflict between any ActionScript definitions and the definitions automatically generated by the .FLA when it is published.
The CLIK architecture requires that this setting be disabled for all the CLIK components to properly function because explicitly defining Stage elements is commonly required (and a best practice) for referencing strongly typed children in ActionScript classes.
You can disable "Automatically Declare Stage Instances" for a .FLA by opening File -> Publish Settings -> "Flash" tab -> Actionscript 3.0 Settings and ensuring that “Automatically declare stage instances” is unchecked. Note that this settings is not a global Flash Studio setting and is only saved to the particular .FLA.
2. I am importing a CLIK component from another .FLA's library. When I place an instance of the component on Stage and change its inspectable properties, I receive the following error: Code: 1046: Type was not found or was not a compile-time constant: ...
This error most commonly occurs due to an improper declaration of your component. You can generally resolve the error using the following steps:
3. I have two components in my Library which derive from the same Base Class. When I publish my .SWF file, I receive the following errors:
Symbol ‘MySymbol’, Layer ‘actions’, Frame 10, Line 1 -- 1024: Overriding a function that is not marked for override. Symbol ‘MySymbol’, Layer ‘actions’, Frame 20, Line 1 -- 1024: Overriding a function that is not marked for override. Symbol ‘MySymbol’, Layer ‘actions’, Frame 30, Line 1 -- 1024: Overriding a function that is not marked for override.
These errors commonly are a result of a Symbol with its Class name identical to its Base Class’s name. For example, a Symbol with Class “Button” and Base Class “scaleform.clik.controls.Button”. This will cause that Symbol’s timeline definitions to be merged with the Base Class. Consequently, any other Symbol that shares the same Base Class will inherit those timeline definitions, causing undesired behavior.
To resolve the issue, check to see if there exists a Base Class with multiple Symbol’s associated with it and then ensure that no Symbol’s Class name matches the name of the Base Class. Changing the Class of the Symbol who shares the same name will resolve the issue.