Re: [flexcoders] Re: FABridge Problem - Please help!
Alex, I thank you for your patience. However, in one of my earlier posts on this thread I did give quite a lot of details about my particular situation (which is almost certainly different, but at the same time, related to, the other posters issue). In my case, I'm using an IFrame component (from http://code.google.com/p/flex-iframe/) to display a credit card data collection processing application (for PCI reasons, we do not wish to have the CC data collected via our main application) What I wish to happen, is for the 'hosted' app to be able to tell the 'hosting' flex app that it has completed its job, so that the flex app can change the ui, to present the main dashboard again, or perhaps a new order builder screen, or whatever. The problem is that my hosted html app (via javascript) is unable to communicate with its host flex app. There is an example of exactly this sort of behavior here ( http://ccgi.arutherford.plus.com/website/flex/iframe/IFrameBridgeTest/ ). FYI, I know for sure that this doesn't work (on Windows) with Chrome of Safari, but it does work with IE, FF, and Opera. What I've done, is to take the flex3 project here( http://code.google.com/p/flex-iframe/source/browse/trunk/examples/IFrameCommTest/ ), and just do a simple conversion of the code to flex4. I've exported my version of the project to facilitate help ( http://www.mediafire.com/file/172448jkkgva4ki/iframeCommTest.fxp ) The issue I'm trying to resolve, is why the code works fine in flex3, but not in flex4, and my best guess as to what is wrong is that its got something to do with swfobject being used in the flex4 version causing a change to the location of the FABridge object in the hosted html pages DOM. Hopefully that clears up some of the confusion. Thanks -- Brian J. Ackermann brian.ackerm...@gmail.com 952.373.1626 -- On Wed, Sep 1, 2010 at 11:36 AM, Alex Harui aha...@adobe.com wrote: So from my perspective, you aren’t being specific enough. You are saying that parent.FABridge doesn’t exist, the OP said something else. There are two DOMs, the JS DOM and the AS DOM. You are now saying you can’t find the object, but you aren’t saying which object. If parent.FABridge is null, then it sounds like a JS setup issue. Either FABridge.js isn’t being loaded or isn’t loaded in the right place. You might try your own test js file to see if you can find objects from your test file. On 9/1/10 6:27 AM, Brian J. Ackermann brian.ackerm...@gmail.com wrote: Yes, I've tried debugging on the JS side of things, exactly as you mentioned (See my email in this thread from Thu, Aug 26, 2010 at 12:45 PM). Nothing. I simply can't find the object. I used a javascript object dump function, to 'scan' the objects I could think of, looking for an occurrence of this object that we need for FABridge to work, but its tucked away somewhere, in a place which is non-trivial to locate. -- Brian J. Ackermann brian.ackerm...@gmail.com 952.373.1626 -- On Wed, Sep 1, 2010 at 8:22 AM, Brian J. Ackermann brian.ackerm...@gmail.com wrote: Alex, I think thats (the swfobject) probably getting pretty close to the right line of thinking, and its something that I'd considered briefly myself, but I am not savvy enough yet to make heads or tails of the issue. -- Brian J. Ackermann brian.ackerm...@gmail.com 952.373.1626 -- On Mon, Aug 30, 2010 at 11:44 PM, Alex Harui aha...@adobe.com wrote: I don’t have time to try it right now. In Flex 4, the tag goes inside the fx:Declarations tag. I took a quick look at the AS code and it uses ExternalInterface so it shouldn’t be sensitive to changes between Flex 3 and 4. Have you tried debugging from both sides? Use a JS debugger or stick a bunch of alerts in the JS code and see what sub-expressions are null (parent, parent.FABridge, parent.FABridge.foo, etc). Then put breakpoints on the AS side like FABridge.as.getRoot(). Are you using a new Flex 4 template that now uses SWFObject instead of AC_OETags.js? It shouldn’t make a difference unless you’re simply not including the right JS in the template. On 8/30/10 2:36 PM, gmbroth gmbr...@hotmail.com http://gmbr...@hotmail.com wrote: Hi, Was this problem resolved? I have Flex 3 MXML that defines: mx:Application ... utils:FABridge bridgeName=foo/ ... /mx:Application In Flex 4, must this statement now appear inside an fx:Declarations element? Even if there's no other fx namespace elements being used in the MXML? On the JavaScript side, I've been referencing the bridge as: FABridge.foo.root() which works fine in Flex 3 but doesn't resolve the bridge in Flex 4. How is the bridge referenced? Thanks, Garry --- In flexcoders@yahoogroups.com http://flexcoders
Re: [flexcoders] Re: FABridge Problem - Please help!
Alex, I think thats (the swfobject) probably getting pretty close to the right line of thinking, and its something that I'd considered briefly myself, but I am not savvy enough yet to make heads or tails of the issue. -- Brian J. Ackermann brian.ackerm...@gmail.com 952.373.1626 -- On Mon, Aug 30, 2010 at 11:44 PM, Alex Harui aha...@adobe.com wrote: I don’t have time to try it right now. In Flex 4, the tag goes inside the fx:Declarations tag. I took a quick look at the AS code and it uses ExternalInterface so it shouldn’t be sensitive to changes between Flex 3 and 4. Have you tried debugging from both sides? Use a JS debugger or stick a bunch of alerts in the JS code and see what sub-expressions are null (parent, parent.FABridge, parent.FABridge.foo, etc). Then put breakpoints on the AS side like FABridge.as.getRoot(). Are you using a new Flex 4 template that now uses SWFObject instead of AC_OETags.js? It shouldn’t make a difference unless you’re simply not including the right JS in the template. On 8/30/10 2:36 PM, gmbroth gmbr...@hotmail.com wrote: Hi, Was this problem resolved? I have Flex 3 MXML that defines: mx:Application ... utils:FABridge bridgeName=foo/ ... /mx:Application In Flex 4, must this statement now appear inside an fx:Declarations element? Even if there's no other fx namespace elements being used in the MXML? On the JavaScript side, I've been referencing the bridge as: FABridge.foo.root() which works fine in Flex 3 but doesn't resolve the bridge in Flex 4. How is the bridge referenced? Thanks, Garry --- In flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.comflexcoders%40yahoogroups.com , Brian J. Ackermann brian.ackerm...@... wrote: http://code.google.com/p/flex-iframe/source/browse/trunk/examples/IFrameCommTest/src/com/google/code/flexiframe/examples/IFrameCommTest.mxml lines 80 81 in the original example, there was no ID Thanks -- Brian J. Ackermann brian.ackerm...@... 952.373.1626 -- On Thu, Aug 26, 2010 at 3:27 PM, Alex Harui aha...@... wrote: I just noticed you didn't specify an id=FABridge in your fx:Declarations What was the equivalent statement in Flex 3? On 8/26/10 10:45 AM, Brian J. Ackermann brian.ackerm...@... wrote: From my testing, I believe the problem is on the JS side of thing, and that the FABridge doesn't 'live' in the same location in the DOM in flex4, as compared with flex3. But we're both reasonably novice flex developers, so we could be mis-interpreting what we're seeing. In another version of the project, I have added some debugging to a text area on screen, and this.parent.FABridge and parent.FABridge and FABridge all return 'undefined'. Since that used to work just fine in flex3, it seems like maybe I just need to find the new 'path' in the DOM for example: this.parent.foo.bar.blah.FABridge Thanks, Brian -- Brian J. Ackermann brian.ackerm...@... 952.373.1626 -- On Thu, Aug 26, 2010 at 12:38 PM, Alex Harui aha...@... wrote: I don't have time right now to look and I don't deal much with FABridge, but are you now saying that parent.FABridge is now the issue? The OP said it was FABridge.flex. Is this on the JS side or AS side? In Flex 4, a child component's parent is not the main app, they get shoveled down into the skin. It think the document or parentDocument properties or FlexGlobals.topLevelApplication can access the main app. On 8/26/10 9:10 AM, Brian J. Ackermann brian.ackerm...@... http://brian.ackerm...@... wrote: I'm trying to get the IFrameCommTest example (from http://code.google.com/p/flex-iframe/) to work in Flex 4, and, while the IFrame itself works, the communication does not. In particular, I need to get the included HTML page to call functions from the flex app (I already have a way to get the Flex app to talk to the HTML). I've exported the project to facilitate your help. http://www.mediafire.com/file/172448jkkgva4ki/iframeCommTest.fxp The problem, is that the parent.FABridge doesn't exist. My guess is that something in flex4 changed with regard to how things are located in the DOM. (This post is directly related to the original. I just thought this would be a clearer example of the problem. ) Thanks, -- Brian J. Ackermann brian.ackerm...@... http://brian.ackerm...@... 952.373.1626 -- -- Alex Harui Flex SDK Team Adobe System, Inc. http
Re: [flexcoders] Re: FABridge Problem - Please help!
Yes, I've tried debugging on the JS side of things, exactly as you mentioned (See my email in this thread from Thu, Aug 26, 2010 at 12:45 PM). Nothing. I simply can't find the object. I used a javascript object dump function, to 'scan' the objects I could think of, looking for an occurrence of this object that we need for FABridge to work, but its tucked away somewhere, in a place which is non-trivial to locate. -- Brian J. Ackermann brian.ackerm...@gmail.com 952.373.1626 -- On Wed, Sep 1, 2010 at 8:22 AM, Brian J. Ackermann brian.ackerm...@gmail.com wrote: Alex, I think thats (the swfobject) probably getting pretty close to the right line of thinking, and its something that I'd considered briefly myself, but I am not savvy enough yet to make heads or tails of the issue. -- Brian J. Ackermann brian.ackerm...@gmail.com 952.373.1626 -- On Mon, Aug 30, 2010 at 11:44 PM, Alex Harui aha...@adobe.com wrote: I don’t have time to try it right now. In Flex 4, the tag goes inside the fx:Declarations tag. I took a quick look at the AS code and it uses ExternalInterface so it shouldn’t be sensitive to changes between Flex 3 and 4. Have you tried debugging from both sides? Use a JS debugger or stick a bunch of alerts in the JS code and see what sub-expressions are null (parent, parent.FABridge, parent.FABridge.foo, etc). Then put breakpoints on the AS side like FABridge.as.getRoot(). Are you using a new Flex 4 template that now uses SWFObject instead of AC_OETags.js? It shouldn’t make a difference unless you’re simply not including the right JS in the template. On 8/30/10 2:36 PM, gmbroth gmbr...@hotmail.com wrote: Hi, Was this problem resolved? I have Flex 3 MXML that defines: mx:Application ... utils:FABridge bridgeName=foo/ ... /mx:Application In Flex 4, must this statement now appear inside an fx:Declarations element? Even if there's no other fx namespace elements being used in the MXML? On the JavaScript side, I've been referencing the bridge as: FABridge.foo.root() which works fine in Flex 3 but doesn't resolve the bridge in Flex 4. How is the bridge referenced? Thanks, Garry --- In flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.comflexcoders%40yahoogroups.com , Brian J. Ackermann brian.ackerm...@... wrote: http://code.google.com/p/flex-iframe/source/browse/trunk/examples/IFrameCommTest/src/com/google/code/flexiframe/examples/IFrameCommTest.mxml lines 80 81 in the original example, there was no ID Thanks -- Brian J. Ackermann brian.ackerm...@... 952.373.1626 -- On Thu, Aug 26, 2010 at 3:27 PM, Alex Harui aha...@... wrote: I just noticed you didn't specify an id=FABridge in your fx:Declarations What was the equivalent statement in Flex 3? On 8/26/10 10:45 AM, Brian J. Ackermann brian.ackerm...@... wrote: From my testing, I believe the problem is on the JS side of thing, and that the FABridge doesn't 'live' in the same location in the DOM in flex4, as compared with flex3. But we're both reasonably novice flex developers, so we could be mis-interpreting what we're seeing. In another version of the project, I have added some debugging to a text area on screen, and this.parent.FABridge and parent.FABridge and FABridge all return 'undefined'. Since that used to work just fine in flex3, it seems like maybe I just need to find the new 'path' in the DOM for example: this.parent.foo.bar.blah.FABridge Thanks, Brian -- Brian J. Ackermann brian.ackerm...@... 952.373.1626 -- On Thu, Aug 26, 2010 at 12:38 PM, Alex Harui aha...@... wrote: I don't have time right now to look and I don't deal much with FABridge, but are you now saying that parent.FABridge is now the issue? The OP said it was FABridge.flex. Is this on the JS side or AS side? In Flex 4, a child component's parent is not the main app, they get shoveled down into the skin. It think the document or parentDocument properties or FlexGlobals.topLevelApplication can access the main app. On 8/26/10 9:10 AM, Brian J. Ackermann brian.ackerm...@... http://brian.ackerm...@... wrote: I'm trying to get the IFrameCommTest example (from http://code.google.com/p/flex-iframe/) to work in Flex 4, and, while the IFrame itself works, the communication does not. In particular, I need to get the included HTML page to call functions from the flex app (I already have a way to get the Flex app to talk to the HTML). I've exported the project to facilitate your
Re: [flexcoders] FABridge Problem - Please help!
http://code.google.com/p/flex-iframe/source/browse/trunk/examples/IFrameCommTest/src/com/google/code/flexiframe/examples/IFrameCommTest.mxml lines 80 81 in the original example, there was no ID Thanks -- Brian J. Ackermann brian.ackerm...@gmail.com 952.373.1626 -- On Thu, Aug 26, 2010 at 3:27 PM, Alex Harui aha...@adobe.com wrote: I just noticed you didn’t specify an id=”FABridge” in your fx:Declarations What was the equivalent statement in Flex 3? On 8/26/10 10:45 AM, Brian J. Ackermann brian.ackerm...@gmail.com wrote: From my testing, I believe the problem is on the JS side of thing, and that the FABridge doesn't 'live' in the same location in the DOM in flex4, as compared with flex3. But we're both reasonably novice flex developers, so we could be mis-interpreting what we're seeing. In another version of the project, I have added some debugging to a text area on screen, and this.parent.FABridge and parent.FABridge and FABridge all return 'undefined'. Since that used to work just fine in flex3, it seems like maybe I just need to find the new 'path' in the DOM for example: this.parent.foo.bar.blah.FABridge Thanks, Brian -- Brian J. Ackermann brian.ackerm...@gmail.com 952.373.1626 -- On Thu, Aug 26, 2010 at 12:38 PM, Alex Harui aha...@adobe.com wrote: I don’t have time right now to look and I don’t deal much with FABridge, but are you now saying that parent.FABridge is now the issue? The OP said it was FABridge.flex. Is this on the JS side or AS side? In Flex 4, a child component’s parent is not the main app, they get shoveled down into the skin. It think the document or parentDocument properties or FlexGlobals.topLevelApplication can access the main app. On 8/26/10 9:10 AM, Brian J. Ackermann brian.ackerm...@gmail.com http://brian.ackerm...@gmail.com wrote: I'm trying to get the IFrameCommTest example (from http://code.google.com/p/flex-iframe/) to work in Flex 4, and, while the IFrame itself works, the communication does not. In particular, I need to get the included HTML page to call functions from the flex app (I already have a way to get the Flex app to talk to the HTML). I've exported the project to facilitate your help. http://www.mediafire.com/file/172448jkkgva4ki/iframeCommTest.fxp The problem, is that the parent.FABridge doesn't exist. My guess is that something in flex4 changed with regard to how things are located in the DOM. (This post is directly related to the original. I just thought this would be a clearer example of the problem. ) Thanks, -- Brian J. Ackermann brian.ackerm...@gmail.com http://brian.ackerm...@gmail.com 952.373.1626 -- -- Alex Harui Flex SDK Team Adobe System, Inc. http://blogs.adobe.com/aharui
Re: [flexcoders] FABridge Problem - Please help!
I'm trying to get the IFrameCommTest example (from http://code.google.com/p/flex-iframe/) to work in Flex 4, and, while the IFrame itself works, the communication does not. In particular, I need to get the included HTML page to call functions from the flex app (I already have a way to get the Flex app to talk to the HTML). I've exported the project to facilitate your help. http://www.mediafire.com/file/172448jkkgva4ki/iframeCommTest.fxp The problem, is that the parent.FABridge doesn't exist. My guess is that something in flex4 changed with regard to how things are located in the DOM. (This post is directly related to the original. I just thought this would be a clearer example of the problem. ) Thanks, -- Brian J. Ackermann brian.ackerm...@gmail.com 952.373.1626 --
Re: [flexcoders] FABridge Problem - Please help!
From my testing, I believe the problem is on the JS side of thing, and that the FABridge doesn't 'live' in the same location in the DOM in flex4, as compared with flex3. But we're both reasonably novice flex developers, so we could be mis-interpreting what we're seeing. In another version of the project, I have added some debugging to a text area on screen, and this.parent.FABridge and parent.FABridge and FABridge all return 'undefined'. Since that used to work just fine in flex3, it seems like maybe I just need to find the new 'path' in the DOM for example: this.parent.foo.bar.blah.FABridge Thanks, Brian -- Brian J. Ackermann brian.ackerm...@gmail.com 952.373.1626 -- On Thu, Aug 26, 2010 at 12:38 PM, Alex Harui aha...@adobe.com wrote: I don’t have time right now to look and I don’t deal much with FABridge, but are you now saying that parent.FABridge is now the issue? The OP said it was FABridge.flex. Is this on the JS side or AS side? In Flex 4, a child component’s parent is not the main app, they get shoveled down into the skin. It think the document or parentDocument properties or FlexGlobals.topLevelApplication can access the main app. On 8/26/10 9:10 AM, Brian J. Ackermann brian.ackerm...@gmail.com wrote: I'm trying to get the IFrameCommTest example (from http://code.google.com/p/flex-iframe/) to work in Flex 4, and, while the IFrame itself works, the communication does not. In particular, I need to get the included HTML page to call functions from the flex app (I already have a way to get the Flex app to talk to the HTML). I've exported the project to facilitate your help. http://www.mediafire.com/file/172448jkkgva4ki/iframeCommTest.fxp The problem, is that the parent.FABridge doesn't exist. My guess is that something in flex4 changed with regard to how things are located in the DOM. (This post is directly related to the original. I just thought this would be a clearer example of the problem. ) Thanks, -- Brian J. Ackermann brian.ackerm...@gmail.com 952.373.1626 -- -- Alex Harui Flex SDK Team Adobe System, Inc. http://blogs.adobe.com/aharui
Re: [flexcoders] Error #2063: Error attempting to execute IME command.
I've never even heard of it until I started getting this message...
As an update...I've since replaced all the Alert's with traces, and while
they work fine now, the problem isn't limited to Alerts in the apps
creationComplete(), but its affecting all Alert dialogs, regardless of
position.
--
Brian J. Ackermann
brian.ackerm...@gmail.com
952.373.1626
--
On Fri, Aug 20, 2010 at 1:10 AM, Alex Harui aha...@adobe.com wrote:
Do you have IME installed on your system?
On 8/19/10 1:37 PM, Brian J. Ackermann brian.ackerm...@gmail.com
wrote:
Hi,
I'm getting the following error message, from a simple 'Alert.show(foo)'
call, in my mx:Application's creationComplete handler.
I see other examples of this working on the web
Error: Error #2063: Error attempting to execute IME command.
at flash.system::IME$/set enabled()
at
mx.managers::FocusManager/focusInHandler()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\FocusManager.as:642]
at flash.display::Stage/set focus()
at
mx.core::UIComponent/setFocus()[E:\dev\4.x\frameworks\projects\framework\src\mx\core\UIComponent.as:9544]
at
mx.controls.alertClasses::AlertForm/commitProperties()[E:\dev\4.x\frameworks\projects\framework\src\mx\controls\alertClasses\AlertForm.as:265]
at
mx.core::UIComponent/validateProperties()[E:\dev\4.x\frameworks\projects\framework\src\mx\core\UIComponent.as:7933]
at
mx.managers::LayoutManager/validateClient()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:863]
at
mx.managers::PopUpManagerImpl/addPopUp()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\PopUpManagerImpl.as:384]
at
mx.managers::PopUpManager$/addPopUp()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\PopUpManager.as:193]
at
mx.controls::Alert$/show()[E:\dev\4.x\frameworks\projects\framework\src\mx\controls\Alert.as:618]
at
adminTrak::AdminTrak/init()[C:\SVN\webstore\trunk\tmpFlex_RenameMe\Flex\AdminTrak\src\adminTrak\AdminTrak.mxml:60]
at
adminTrak::AdminTrak/___AdminTrak_Application1_creationComplete()[C:\SVN\webstore\trunk\tmpFlex_RenameMe\Flex\AdminTrak\src\adminTrak\AdminTrak.mxml:11]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at
mx.core::UIComponent/dispatchEvent()[E:\dev\4.x\frameworks\projects\framework\src\mx\core\UIComponent.as:12528]
at mx.core::UIComponent/set
initialized()[E:\dev\4.x\frameworks\projects\framework\src\mx\core\UIComponent.as:1627]
at
mx.managers::LayoutManager/doPhasedInstantiation()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:759]
at
mx.managers::LayoutManager/doPhasedInstantiationCallback()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:1072]
in fact, this works:
?xml version=1.0 encoding=utf-8?
s:Application xmlns:fx=http://ns.adobe.com/mxml/2009;
xmlns:s=library://ns.adobe.com/flex/spark
http://ns.adobe.com/flex/spark
xmlns:mx=library://ns.adobe.com/flex/mx http://ns.adobe.com/flex/mx
minWidth=955 minHeight=600 creationComplete=init()
fx:Declarations
!-- Place non-visual elements (e.g., services, value objects) here --
/fx:Declarations
fx:Script
![CDATA[
import mx.controls.Alert;
private function init():void {
Alert.show(Starting the program);
}
]]
/fx:Script
/s:Application
I read up on IME, and I don't see anything in there that I'm the least bit
familiar with. Certainly nothing that I've added to my code.
Any ideas?
--
Brian J. Ackermann
brian.ackerm...@gmail.com
952.373.1626
--
--
Alex Harui
Flex SDK Team
Adobe System, Inc.
http://blogs.adobe.com/aharui
Re: [flexcoders] Error #2063: Error attempting to execute IME command.
I don't recall updating my flash player yesterday.hmm..
Additionally. I've searched my entire project for the string IME, and
nothing is foundI'm not using this little beastie at all.
--
Brian J. Ackermann
brian.ackerm...@gmail.com
952.373.1626
--
On Fri, Aug 20, 2010 at 8:38 AM, Karim Beyrouti ka...@kurst.co.uk wrote:
Had the same problem a while ago - and seem to remember it's got something
to do with FP 10.1...
On 20 Aug 2010, at 13:25, Brian J. Ackermann wrote:
I've never even heard of it until I started getting this message...
As an update...I've since replaced all the Alert's with traces, and while
they work fine now, the problem isn't limited to Alerts in the apps
creationComplete(), but its affecting all Alert dialogs, regardless of
position.
--
Brian J. Ackermann
brian.ackerm...@gmail.com
952.373.1626
--
On Fri, Aug 20, 2010 at 1:10 AM, Alex Harui aha...@adobe.com wrote:
Do you have IME installed on your system?
On 8/19/10 1:37 PM, Brian J. Ackermann brian.ackerm...@gmail.com
wrote:
Hi,
I'm getting the following error message, from a simple 'Alert.show(foo)'
call, in my mx:Application's creationComplete handler.
I see other examples of this working on the web
Error: Error #2063: Error attempting to execute IME command.
at flash.system::IME$/set enabled()
at
mx.managers::FocusManager/focusInHandler()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\FocusManager.as:642]
at flash.display::Stage/set focus()
at
mx.core::UIComponent/setFocus()[E:\dev\4.x\frameworks\projects\framework\src\mx\core\UIComponent.as:9544]
at
mx.controls.alertClasses::AlertForm/commitProperties()[E:\dev\4.x\frameworks\projects\framework\src\mx\controls\alertClasses\AlertForm.as:265]
at
mx.core::UIComponent/validateProperties()[E:\dev\4.x\frameworks\projects\framework\src\mx\core\UIComponent.as:7933]
at
mx.managers::LayoutManager/validateClient()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:863]
at
mx.managers::PopUpManagerImpl/addPopUp()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\PopUpManagerImpl.as:384]
at
mx.managers::PopUpManager$/addPopUp()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\PopUpManager.as:193]
at
mx.controls::Alert$/show()[E:\dev\4.x\frameworks\projects\framework\src\mx\controls\Alert.as:618]
at
adminTrak::AdminTrak/init()[C:\SVN\webstore\trunk\tmpFlex_RenameMe\Flex\AdminTrak\src\adminTrak\AdminTrak.mxml:60]
at
adminTrak::AdminTrak/___AdminTrak_Application1_creationComplete()[C:\SVN\webstore\trunk\tmpFlex_RenameMe\Flex\AdminTrak\src\adminTrak\AdminTrak.mxml:11]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at
mx.core::UIComponent/dispatchEvent()[E:\dev\4.x\frameworks\projects\framework\src\mx\core\UIComponent.as:12528]
at mx.core::UIComponent/set
initialized()[E:\dev\4.x\frameworks\projects\framework\src\mx\core\UIComponent.as:1627]
at
mx.managers::LayoutManager/doPhasedInstantiation()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:759]
at
mx.managers::LayoutManager/doPhasedInstantiationCallback()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:1072]
in fact, this works:
?xml version=1.0 encoding=utf-8?
s:Application xmlns:fx=http://ns.adobe.com/mxml/2009;
xmlns:s=library://ns.adobe.com/flex/spark
http://ns.adobe.com/flex/spark
xmlns:mx=library://ns.adobe.com/flex/mx http://ns.adobe.com/flex/mx
minWidth=955 minHeight=600 creationComplete=init()
fx:Declarations
!-- Place non-visual elements (e.g., services, value objects) here --
/fx:Declarations
fx:Script
![CDATA[
import mx.controls.Alert;
private function init():void {
Alert.show(Starting the program);
}
]]
/fx:Script
/s:Application
I read up on IME, and I don't see anything in there that I'm the least bit
familiar with. Certainly nothing that I've added to my code.
Any ideas?
--
Brian J. Ackermann
brian.ackerm...@gmail.com
952.373.1626
--
--
Alex Harui
Flex SDK Team
Adobe System, Inc.
http://blogs.adobe.com/aharui
Re: [flexcoders] Error #2063: Error attempting to execute IME command.
Hmm...peculiar.
I ran the app in IE, FF, and GC.
IE and FF are both 10.0 installs, and GC is on 10.1 somehow.
IE doesn't work, throws all sorts of IME errors. FF seems to work
perfectly. GC, doesn't throw errors, but also isn't working perfectly. I'm
going to update my all my flashplayers, see what happens.
time passes
IE now works, but now FF(mis) behaves the same way as GC.
Well, at least its some kind of progress, thanks!
--
Brian J. Ackermann
brian.ackerm...@gmail.com
952.373.1626
--
On Fri, Aug 20, 2010 at 8:51 AM, Brian J. Ackermann
brian.ackerm...@gmail.com wrote:
I don't recall updating my flash player yesterday.hmm..
Additionally. I've searched my entire project for the string IME, and
nothing is foundI'm not using this little beastie at all.
--
Brian J. Ackermann
brian.ackerm...@gmail.com
952.373.1626
--
On Fri, Aug 20, 2010 at 8:38 AM, Karim Beyrouti ka...@kurst.co.uk wrote:
Had the same problem a while ago - and seem to remember it's got something
to do with FP 10.1...
On 20 Aug 2010, at 13:25, Brian J. Ackermann wrote:
I've never even heard of it until I started getting this message...
As an update...I've since replaced all the Alert's with traces, and while
they work fine now, the problem isn't limited to Alerts in the apps
creationComplete(), but its affecting all Alert dialogs, regardless of
position.
--
Brian J. Ackermann
brian.ackerm...@gmail.com
952.373.1626
--
On Fri, Aug 20, 2010 at 1:10 AM, Alex Harui aha...@adobe.com wrote:
Do you have IME installed on your system?
On 8/19/10 1:37 PM, Brian J. Ackermann brian.ackerm...@gmail.com
wrote:
Hi,
I'm getting the following error message, from a simple
'Alert.show(foo)' call, in my mx:Application's creationComplete handler.
I see other examples of this working on the web
Error: Error #2063: Error attempting to execute IME command.
at flash.system::IME$/set enabled()
at
mx.managers::FocusManager/focusInHandler()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\FocusManager.as:642]
at flash.display::Stage/set focus()
at
mx.core::UIComponent/setFocus()[E:\dev\4.x\frameworks\projects\framework\src\mx\core\UIComponent.as:9544]
at
mx.controls.alertClasses::AlertForm/commitProperties()[E:\dev\4.x\frameworks\projects\framework\src\mx\controls\alertClasses\AlertForm.as:265]
at
mx.core::UIComponent/validateProperties()[E:\dev\4.x\frameworks\projects\framework\src\mx\core\UIComponent.as:7933]
at
mx.managers::LayoutManager/validateClient()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:863]
at
mx.managers::PopUpManagerImpl/addPopUp()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\PopUpManagerImpl.as:384]
at
mx.managers::PopUpManager$/addPopUp()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\PopUpManager.as:193]
at
mx.controls::Alert$/show()[E:\dev\4.x\frameworks\projects\framework\src\mx\controls\Alert.as:618]
at
adminTrak::AdminTrak/init()[C:\SVN\webstore\trunk\tmpFlex_RenameMe\Flex\AdminTrak\src\adminTrak\AdminTrak.mxml:60]
at
adminTrak::AdminTrak/___AdminTrak_Application1_creationComplete()[C:\SVN\webstore\trunk\tmpFlex_RenameMe\Flex\AdminTrak\src\adminTrak\AdminTrak.mxml:11]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at
mx.core::UIComponent/dispatchEvent()[E:\dev\4.x\frameworks\projects\framework\src\mx\core\UIComponent.as:12528]
at mx.core::UIComponent/set
initialized()[E:\dev\4.x\frameworks\projects\framework\src\mx\core\UIComponent.as:1627]
at
mx.managers::LayoutManager/doPhasedInstantiation()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:759]
at
mx.managers::LayoutManager/doPhasedInstantiationCallback()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:1072]
in fact, this works:
?xml version=1.0 encoding=utf-8?
s:Application xmlns:fx=http://ns.adobe.com/mxml/2009;
xmlns:s=library://ns.adobe.com/flex/spark
http://ns.adobe.com/flex/spark
xmlns:mx=library://ns.adobe.com/flex/mx http://ns.adobe.com/flex/mx
minWidth=955 minHeight=600 creationComplete=init()
fx:Declarations
!-- Place non-visual elements (e.g., services, value objects) here --
/fx:Declarations
fx:Script
![CDATA[
import mx.controls.Alert;
private function init():void {
Alert.show(Starting the program);
}
]]
/fx:Script
/s:Application
I read up on IME, and I don't see anything in there that I'm the least
bit familiar with. Certainly nothing that I've added to my code.
Any ideas?
--
Brian J. Ackermann
brian.ackerm...@gmail.com
952.373.1626
--
--
Alex Harui
Flex SDK Team
Adobe System, Inc.
http
Re: [flexcoders] Error #2063: Error attempting to execute IME command.
Hi Karim, All is well now. I updated the flash debugger to the latest, and after fixing another (unrelated) bug, all three browsers now behave themselves. Updating the flash player to the most recent solved it. I haven't a clue why it suddenly went belly up yesterday, but, at least I'm able to proceed again. -- Brian J. Ackermann brian.ackerm...@gmail.com 952.373.1626 -- On Fri, Aug 20, 2010 at 12:09 PM, Karim Beyrouti ka...@kurst.co.uk wrote: I think it will depend what version of FP you are exporting to... sorry for being so vague - it's been a while since i have had this error... and i cant quite remember how i fixed it... also - some details of Flex / Flash Builder version or are you using FDT?... On 20 Aug 2010, at 16:34, Brian J. Ackermann wrote: Hmm...peculiar. I ran the app in IE, FF, and GC. IE and FF are both 10.0 installs, and GC is on 10.1 somehow. IE doesn't work, throws all sorts of IME errors. FF seems to work perfectly. GC, doesn't throw errors, but also isn't working perfectly. I'm going to update my all my flashplayers, see what happens. time passes IE now works, but now FF(mis) behaves the same way as GC. Well, at least its some kind of progress, thanks! -- Brian J. Ackermann brian.ackerm...@gmail.com 952.373.1626 -- On Fri, Aug 20, 2010 at 8:51 AM, Brian J. Ackermann brian.ackerm...@gmail.com wrote: I don't recall updating my flash player yesterday.hmm.. Additionally. I've searched my entire project for the string IME, and nothing is foundI'm not using this little beastie at all. -- Brian J. Ackermann brian.ackerm...@gmail.com 952.373.1626 -- On Fri, Aug 20, 2010 at 8:38 AM, Karim Beyrouti ka...@kurst.co.ukwrote: Had the same problem a while ago - and seem to remember it's got something to do with FP 10.1... On 20 Aug 2010, at 13:25, Brian J. Ackermann wrote: I've never even heard of it until I started getting this message... As an update...I've since replaced all the Alert's with traces, and while they work fine now, the problem isn't limited to Alerts in the apps creationComplete(), but its affecting all Alert dialogs, regardless of position. -- Brian J. Ackermann brian.ackerm...@gmail.com 952.373.1626 -- On Fri, Aug 20, 2010 at 1:10 AM, Alex Harui aha...@adobe.com wrote: Do you have IME installed on your system? On 8/19/10 1:37 PM, Brian J. Ackermann brian.ackerm...@gmail.com wrote: Hi, I'm getting the following error message, from a simple 'Alert.show(foo)' call, in my mx:Application's creationComplete handler. I see other examples of this working on the web Error: Error #2063: Error attempting to execute IME command. at flash.system::IME$/set enabled() at mx.managers::FocusManager/focusInHandler()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\FocusManager.as:642] at flash.display::Stage/set focus() at mx.core::UIComponent/setFocus()[E:\dev\4.x\frameworks\projects\framework\src\mx\core\UIComponent.as:9544] at mx.controls.alertClasses::AlertForm/commitProperties()[E:\dev\4.x\frameworks\projects\framework\src\mx\controls\alertClasses\AlertForm.as:265] at mx.core::UIComponent/validateProperties()[E:\dev\4.x\frameworks\projects\framework\src\mx\core\UIComponent.as:7933] at mx.managers::LayoutManager/validateClient()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:863] at mx.managers::PopUpManagerImpl/addPopUp()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\PopUpManagerImpl.as:384] at mx.managers::PopUpManager$/addPopUp()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\PopUpManager.as:193] at mx.controls::Alert$/show()[E:\dev\4.x\frameworks\projects\framework\src\mx\controls\Alert.as:618] at adminTrak::AdminTrak/init()[C:\SVN\webstore\trunk\tmpFlex_RenameMe\Flex\AdminTrak\src\adminTrak\AdminTrak.mxml:60] at adminTrak::AdminTrak/___AdminTrak_Application1_creationComplete()[C:\SVN\webstore\trunk\tmpFlex_RenameMe\Flex\AdminTrak\src\adminTrak\AdminTrak.mxml:11] at flash.events::EventDispatcher/dispatchEventFunction() at flash.events::EventDispatcher/dispatchEvent() at mx.core::UIComponent/dispatchEvent()[E:\dev\4.x\frameworks\projects\framework\src\mx\core\UIComponent.as:12528] at mx.core::UIComponent/set initialized()[E:\dev\4.x\frameworks\projects\framework\src\mx\core\UIComponent.as:1627] at mx.managers::LayoutManager/doPhasedInstantiation()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:759] at mx.managers::LayoutManager/doPhasedInstantiationCallback()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:1072] in fact, this works: ?xml version=1.0 encoding=utf-8? s:Application
[flexcoders] Error #2063: Error attempting to execute IME command.
Hi,
I'm getting the following error message, from a simple 'Alert.show(foo)'
call, in my mx:Application's creationComplete handler.
I see other examples of this working on the web
Error: Error #2063: Error attempting to execute IME command.
at flash.system::IME$/set enabled()
at
mx.managers::FocusManager/focusInHandler()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\FocusManager.as:642]
at flash.display::Stage/set focus()
at
mx.core::UIComponent/setFocus()[E:\dev\4.x\frameworks\projects\framework\src\mx\core\UIComponent.as:9544]
at
mx.controls.alertClasses::AlertForm/commitProperties()[E:\dev\4.x\frameworks\projects\framework\src\mx\controls\alertClasses\AlertForm.as:265]
at
mx.core::UIComponent/validateProperties()[E:\dev\4.x\frameworks\projects\framework\src\mx\core\UIComponent.as:7933]
at
mx.managers::LayoutManager/validateClient()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:863]
at
mx.managers::PopUpManagerImpl/addPopUp()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\PopUpManagerImpl.as:384]
at
mx.managers::PopUpManager$/addPopUp()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\PopUpManager.as:193]
at
mx.controls::Alert$/show()[E:\dev\4.x\frameworks\projects\framework\src\mx\controls\Alert.as:618]
at
adminTrak::AdminTrak/init()[C:\SVN\webstore\trunk\tmpFlex_RenameMe\Flex\AdminTrak\src\adminTrak\AdminTrak.mxml:60]
at
adminTrak::AdminTrak/___AdminTrak_Application1_creationComplete()[C:\SVN\webstore\trunk\tmpFlex_RenameMe\Flex\AdminTrak\src\adminTrak\AdminTrak.mxml:11]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at
mx.core::UIComponent/dispatchEvent()[E:\dev\4.x\frameworks\projects\framework\src\mx\core\UIComponent.as:12528]
at mx.core::UIComponent/set
initialized()[E:\dev\4.x\frameworks\projects\framework\src\mx\core\UIComponent.as:1627]
at
mx.managers::LayoutManager/doPhasedInstantiation()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:759]
at
mx.managers::LayoutManager/doPhasedInstantiationCallback()[E:\dev\4.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:1072]
in fact, this works:
?xml version=1.0 encoding=utf-8?
s:Application xmlns:fx=http://ns.adobe.com/mxml/2009;
xmlns:s=library://ns.adobe.com/flex/spark
xmlns:mx=library://ns.adobe.com/flex/mx minWidth=955 minHeight=600
creationComplete=init()
fx:Declarations
!-- Place non-visual elements (e.g., services, value objects) here --
/fx:Declarations
fx:Script
![CDATA[
import mx.controls.Alert;
private function init():void {
Alert.show(Starting the program);
}
]]
/fx:Script
/s:Application
I read up on IME, and I don't see anything in there that I'm the least bit
familiar with. Certainly nothing that I've added to my code.
Any ideas?
--
Brian J. Ackermann
brian.ackerm...@gmail.com
952.373.1626
--
Re: [flexcoders] Re: Could not resolve * to a component implementation.
So, its a class, even thought it doesn't declare a class inside the text? -- Brian J. Ackermann brian.ackerm...@gmail.com 952.373.1626 -- On Thu, Jul 1, 2010 at 10:21 PM, turbo_vb timh...@aol.com wrote: Glad that you were able to resolve the problem. The AS file IS a class, and if it lives in the same package as the mxml component, the compiler will balk; because it doesn't know which one to import elsewhere. Adobe best practice would have you use Uppercase for the first letter of all classes. Renaming the script class to something like FooScript.as or FooModel.as might be a better way to go. Cheers, -TH --- In flexcoders@yahoogroups.com flexcoders%40yahoogroups.com, Brian J. Ackermann brian.ackerm...@... wrote: Here's what the problem was. I had originally had a file called Foo.mxml which contained a lot of ActionScript Code. I decided to create a new ActionScript FILE to contain that script code. I named the file Foo.as, to indicate the correlation with the mxml file. Renaming this new as file to foo.as (lowercase f), resolves the issue. I'm not at all sure why this would have caused a conflict with the compiler, since it wasn't a classbut at least I've resolved the issue. On Thu, Jul 1, 2010 at 7:57 AM, valdhor valdhorli...@... wrote: One other thing to check. Make sure you are not using a reserved name for your component. --- In flexcoders@yahoogroups.com flexcoders%40yahoogroups.comflexcoders% 40yahoogroups.com, turbo_vb TimHoff@ wrote: A couple things that you can check that might help: • Make sure that you have an import statement for the component in the parent class. • If your component is an AS class, make sure that the package, at the top of the class, is correct. • If your component is an AS component make sure that the class name, within the component, is correct. If you are using a constructor check that too. -TH --- In flexcoders@yahoogroups.com flexcoders%40yahoogroups.comflexcoders% 40yahoogroups.com, Brian J. Ackermann brian.ackermann@ wrote: Hi, I'm a wee bit stuck on this, and was hoping you might have some input to help me. I'm getting the Could not resolve * to a component implementation. error message. However, everything I've read about this via Google hasn't helped my case in the slightest. I presume I'm just missing something obvious, but maybe its something more serious. So, to solve this problem, I've tried two things, and both work, as far as they take me. First, I added a new component, of the exact same variety, and then copied the contents of the erroring component into it. I replace the viewstack 'page' with the new component (which as near as I can tell is IDENTICAL, but with a different name), and the compiler error goes away. I can also solve this by simply renaming the original component letting FB4 refactor for me. The error goes away again. But if I then re-rename back to the original name, I get the compiler error again. I've tried to clean the project several times, and that doesn't help. I'd really like to understand what I've done wrong here. What am I missing? Thanks much!
Re: [flexcoders] Re: Could not resolve * to a component implementation.
Here's what the problem was. I had originally had a file called Foo.mxml which contained a lot of ActionScript Code. I decided to create a new ActionScript FILE to contain that script code. I named the file Foo.as, to indicate the correlation with the mxml file. Renaming this new as file to foo.as (lowercase f), resolves the issue. I'm not at all sure why this would have caused a conflict with the compiler, since it wasn't a classbut at least I've resolved the issue. On Thu, Jul 1, 2010 at 7:57 AM, valdhor valdhorli...@embarqmail.com wrote: One other thing to check. Make sure you are not using a reserved name for your component. --- In flexcoders@yahoogroups.com flexcoders%40yahoogroups.com, turbo_vb timh...@... wrote: A couple things that you can check that might help: • Make sure that you have an import statement for the component in the parent class. • If your component is an AS class, make sure that the package, at the top of the class, is correct. • If your component is an AS component make sure that the class name, within the component, is correct. If you are using a constructor check that too. -TH --- In flexcoders@yahoogroups.com flexcoders%40yahoogroups.com, Brian J. Ackermann brian.ackermann@ wrote: Hi, I'm a wee bit stuck on this, and was hoping you might have some input to help me. I'm getting the Could not resolve * to a component implementation. error message. However, everything I've read about this via Google hasn't helped my case in the slightest. I presume I'm just missing something obvious, but maybe its something more serious. So, to solve this problem, I've tried two things, and both work, as far as they take me. First, I added a new component, of the exact same variety, and then copied the contents of the erroring component into it. I replace the viewstack 'page' with the new component (which as near as I can tell is IDENTICAL, but with a different name), and the compiler error goes away. I can also solve this by simply renaming the original component letting FB4 refactor for me. The error goes away again. But if I then re-rename back to the original name, I get the compiler error again. I've tried to clean the project several times, and that doesn't help. I'd really like to understand what I've done wrong here. What am I missing? Thanks much!
[flexcoders] Could not resolve * to a component implementation.
Hi, I'm a wee bit stuck on this, and was hoping you might have some input to help me. I'm getting the Could not resolve * to a component implementation. error message. However, everything I've read about this via Google hasn't helped my case in the slightest. I presume I'm just missing something obvious, but maybe its something more serious. So, to solve this problem, I've tried two things, and both work, as far as they take me. First, I added a new component, of the exact same variety, and then copied the contents of the erroring component into it. I replace the viewstack 'page' with the new component (which as near as I can tell is IDENTICAL, but with a different name), and the compiler error goes away. I can also solve this by simply renaming the original component letting FB4 refactor for me. The error goes away again. But if I then re-rename back to the original name, I get the compiler error again. I've tried to clean the project several times, and that doesn't help. I'd really like to understand what I've done wrong here. What am I missing? Thanks much!
