flexcppbridge - Project Hosting on Google Code

Last 30 days Dec 09, 2009 BuildInstructions (Building the source.) Wiki page commented on by anirudhsasikumar - @hanzo852 - FlexVCBridge is at http://code.google.com/p/flexcppbridge/source/browse/trunk/flex/flexvcbridge/FlexVCBridge.mxml. Include that MXML file in your src folder and it should compile. @hanzo852 - FlexVCBridge is at http://code.google.com/p/flexcppbridge/source/browse/trunk/flex/flexvcbridge/FlexVCBridge.mxml. Include that MXML file in your src folder and it should compile. Dec 08, 2009 BuildInstructions (Building the source.) Wiki page commented on by hanzo852 - I have compiled the vc project, it works. but when I try to compile the mxml and as file, the error message is "can't recognize the FlexVCBridge" in "public function testAlert(str:String, str1:String, obj1:Object, bidge:FlexVCBridge):FlexVCBridge" could you give me the way to overcome that? I have compiled the vc project, it works. but when I try to compile the mxml and as file, the error message is "can't recognize the FlexVCBridge" in "public function testAlert(str:String, str1:String, obj1:Object, bidge:FlexVCBridge):FlexVCBridge" could you give me the way to overcome that? Older Aug 12, 2009 BuildInstructions (Building the source.) Wiki page commented on by ramvara - hi anirudh, can u add FlexScan.mxml file for FlexScan project. Or can you send SWF file for the same. hi anirudh, can u add FlexScan.mxml file for FlexScan project. Or can you send SWF file for the same. Mar 30, 2009 issue 2 (Boolean return values were not coming correctly to the C++ s...) reported by anirudhsasikumar - What steps will reproduce the problem? 1. Call any getter / function that returns a boolean. 2. The boolean value was not received on the C++ side. What is the expected output? What do you see instead? An ASOBJECT of type ASOBJECT_BOOLEAN should be returned. --------- This issue was fixed for the 0.2 release. What steps will reproduce the problem? 1. Call any getter / function that returns a boolean. 2. The boolean value was not received on the C++ side. What is the expected output? What do you see instead? An ASOBJECT of type ASOBJECT_BOOLEAN should be returned. --------- This issue was fixed for the 0.2 release. Mar 30, 2009 issue 1 (At times, event object passed to C++ from Flex is NULL) commented on by anirudhsasikumar - Ideally, the first parameter obj should point to the event instance. But due to the asynchronous nature of the C++ bridge, there are times where the Flex instance for the event would get GCed because FABridge.as expects the other side to work synchronously. Here's the fix for that bug (or unfortunate side effect): In http://code.google.com/p/flexcppbridge/source/browse/trunk/flex/bridge/FABridge.as, at line 675, change releaseRef() to: if ( serializedArgs[i].type == TYPE_ASINSTANCE ) incRef(serializedArgs[i].value); Similiarly change line 694: if ( serializedArgs[i].type == TYPE_ASINSTANCE ) incRef(serializedArgs[i].value); This fix comes at a cost: All event objects passed to C++ will never get GCed on the Flex side. You can offset this cost by explicitly having a function on the Flex side that calls bridgeid.releaseRef(instanceidofeventobj) and originally gets called from your C++ code once you are done with the event object. Ideally, the first parameter obj should point to the event instance. But due to the asynchronous nature of the C++ bridge, there are times where the Flex instance for the event would get GCed because FABridge.as expects the other side to work synchronously. Here's the fix for that bug (or unfortunate side effect): In http://code.google.com/p/flexcppbridge/source/browse/trunk/flex/bridge/FABridge.as, at line 675, change releaseRef() to: if ( serializedArgs[i].type == TYPE_ASINSTANCE ) incRef(serializedArgs[i].value); Similiarly change line 694: if ( serializedArgs[i].type == TYPE_ASINSTANCE ) incRef(serializedArgs[i].value); This fix comes at a cost: All event objects passed to C++ will never get GCed on the Flex side. You can offset this cost by explicitly having a function on the Flex side that calls bridgeid.releaseRef(instanceidofeventobj) and originally gets called from your C++ code once you are done with the event object. Mar 30, 2009 issue 1 (At times, event object passed to C++ from Flex is NULL) reported by anirudhsasikumar - What steps will reproduce the problem? 1. Register a C++ function as an event handler. 2. When the event is called, the event object on C++ side is null. What is the expected output? What do you see instead? The actual event object should be there. Flex C++ Bridge getting event object in the C++ event handler. What steps will reproduce the problem? 1. Register a C++ function as an event handler. 2. When the event is called, the event object on C++ side is null. What is the expected output? What do you see instead? The actual event object should be there. Flex C++ Bridge getting event object in the C++ event handler. Nov 10, 2008 flexcppbridge-0.2-staticlib.zip (FlexCPPBridge Static library and one example) file uploaded by anirudhsasikumar - Labels: Featured Type-Source Labels: Featured Type-Source Nov 10, 2008 r17 (Bug reported by Supun - Boolean return values come back as A...) committed by anirudhsasikumar - Bug reported by Supun - Boolean return values come back as ASOBJECT_NONE. This was because the parsing logic expected all primitive return XML nodes to have a node value. This is not true for boolean since the node name (<true/>) itself is the value. Added another if case to check this. Bug reported by Supun - Boolean return values come back as ASOBJECT_NONE. This was because the parsing logic expected all primitive return XML nodes to have a node value. This is not true for boolean since the node name (<true/>) itself is the value. Added another if case to check this.

issue 1 (At times, event object passed to C++ from Flex is NULL) commented on by anirudhsasikumar - Ideally, the first parameter obj should point to the event instance. But due to the asynchronous nature of the C++ bridge, there are times where the Flex instance for the event would get GCed because FABridge.as expects the other side to work synchronously. Here's the fix for that bug (or unfortunate side effect): In http://code.google.com/p/flexcppbridge/source/browse/trunk/flex/bridge/FABridge.as, at line 675, change releaseRef() to: if ( serializedArgs[i].type == TYPE_ASINSTANCE ) incRef(serializedArgs[i].value); Similiarly change line 694: if ( serializedArgs[i].type == TYPE_ASINSTANCE ) incRef(serializedArgs[i].value); This fix comes at a cost: All event objects passed to C++ will never get GCed on the Flex side. You can offset this cost by explicitly having a function on the Flex side that calls bridgeid.releaseRef(instanceidofeventobj) and originally gets called from your C++ code once you are done with the event object.

Ideally, the first parameter obj should point to the event instance. But due to the asynchronous nature of the C++ bridge, there are times where the Flex instance for the event would get GCed because FABridge.as expects the other side to work synchronously. Here's the fix for that bug (or unfortunate side effect): In http://code.google.com/p/flexcppbridge/source/browse/trunk/flex/bridge/FABridge.as, at line 675, change releaseRef() to: if ( serializedArgs[i].type == TYPE_ASINSTANCE ) incRef(serializedArgs[i].value); Similiarly change line 694: if ( serializedArgs[i].type == TYPE_ASINSTANCE ) incRef(serializedArgs[i].value); This fix comes at a cost: All event objects passed to C++ will never get GCed on the Flex side. You can offset this cost by explicitly having a function on the Flex side that calls bridgeid.releaseRef(instanceidofeventobj) and originally gets called from your C++ code once you are done with the event object.

Last 30 days

Older