BlogJava-This Is A FineDay-随笔分类-FLEX

Flex 父子窗口通信的问题收藏

Peter Pan — Fri, 20 Feb 2009 06:22:00 GMT

假设有父窗体P，在父窗体中弹出子窗体C,进行必要的操作后，返回父窗体。
1、弹出子窗体
var c:ChildForm = new ChildForm (); // 新建子窗体对象
PopUpManager.addPopUp(c, this, true); // 将子窗体加入PopUpManager中
c.studentId = ""; // 向子窗体传递参数
c.callbackFunction = this.refresh; // 子窗体中可以调用的父窗体函数（这里是子窗体关闭时，用来刷新父窗体的内容
PopUpManager.centerPopUp(c); // 子窗体弹出，居中
2、子窗体关闭时，调用父窗体
public var callbackFunction:Function; //回调函数
public var studentId:String = "";
public function doClose():void {
PopUpManager.removePopUp(this);
if (isUpdate) { callbackFunction.call(parent); // 调用父窗体的刷新函数
}
}

Peter Pan 2009-02-20 14:22 发表评论

flex Repeater click收藏

Peter Pan — Fri, 20 Feb 2009 06:20:00 GMT

                            showNewWindow(event.currentTarget.getRepeaterItem().id);"
                                      mouseOut="labelMouseOut(event);" mouseOver="labelMouseOver(event);"/>

Peter Pan 2009-02-20 14:20 发表评论

flex sdk 3.2 RemoteObject问题

Peter Pan — Fri, 20 Feb 2009 02:47:00 GMT

TypeError: Error #1034: 强制转换类型失败:无法将Object@3b3a1a1转换为 mx.messaging.messages.IMessage。

需要在Application里面增加
import flash.net.registerClassAlias;
import mx.messaging.messages.RemotingMessage;

registerClassAlias("flex.messaging.messages.RemotingMessage", RemotingMessage);

Peter Pan 2009-02-20 10:47 发表评论

Repeater remote 嵌套

Peter Pan — Thu, 15 Jan 2009 03:20:00 GMT

Repeater remote object 嵌套似乎又是flex的一个Bug，郁闷了一天
最终解决方法用Script初始化数据

<mx:Label text="{new2.currentItem.@label2}" /> OK
<mx:Label text="{ppt.currentItem.typeName}" /> NOK
<mx:Label text="{ppt.currentItem.typeName}" creationComplete="accChildCreationComplete(event);" width="100%"/> OK

1<mx:XMLListCollection id="xmlListColl">
2        <mx:source>
3            <mx:XMLList>
4                <node label="One">
5                    <node2 label2="One.1" />
6                    <node2 label2="One.2" />
7                    <node2 label2="One.3" />
8                node>
9                <node label="Two">
10                    <node2 label2="Two.1" />
11                    <node2 label2="Two.2" />
12                    <node2 label2="Two.3" />
13                node>
14            mx:XMLList>
15        mx:source>
16    mx:XMLListCollection>
17    <mx:Accordion id="accoridLeft"
18                  resizeToContent="true"
19                  width="100%">
20           <mx:Repeater id="news" dataProvider="{xmlListColl}">
21            <mx:VBox label="{news.currentItem.@label}">
22                <mx:VDividedBox horizontalAlign="left" paddingLeft="15">
23                         <mx:Repeater id="new2" dataProvider="{news.currentItem.node2}">
24                        <mx:VBox label="{new2.currentItem.@label2}">
25                            <mx:Label text="{new2.currentItem.@label2}" click="onClick1(event);"/>
26                        mx:VBox>
27                     mx:Repeater>
28                mx:VDividedBox>
29            mx:VBox>
30        mx:Repeater>
31    mx:Accordion>

    <mx:Script>

        import mx.rpc.events.ResultEvent;
        import mx.events.FlexEvent;
        import mx.utils.ArrayUtil;
        import mx.collections.ArrayList;
        import mx.collections.ArrayCollection;
        import mx.controls.Alert;
        import mx.effects.easing.*;

        public function init():void {
            pts.getProductTypeMenu();
        }

        public function accChildCreationComplete(event:FlexEvent):void{
            event.target.text = String(event.currentTarget.getRepeaterItem().typeName);
        }

        ]]>
    mx:Script>
    <mx:RemoteObject id="pts" destination="productTypeService">
    mx:RemoteObject>
    <mx:Accordion id="accoridLeft"
                  resizeToContent="true"
                  width="100%">
        <mx:Repeater dataProvider="{pts.getProductTypeMenu.lastResult}" id="pt">
            <mx:VBox label="{pt.currentItem.typeName}" width="100%">
                <mx:Repeater dataProvider="{pt.currentItem.productTypes}" id="ppt">
                    <mx:Label text="{ppt.currentItem.typeName}" creationComplete="accChildCreationComplete(event);" width="100%"/>
                mx:Repeater>
            mx:VBox>
        mx:Repeater>
    mx:Accordion>

Peter Pan 2009-01-15 11:20 发表评论

cannot convert mx.managers::HistoryManagerImpl@2403de71 to mx.managers.IHistoryManager.

Peter Pan — Sun, 04 Jan 2009 08:35:00 GMT

又一个flex bug汗了半天

Actual Results:
TypeError: Error #1034: Type Coercion failed: cannot convert mx.managers::HistoryManagerImpl@2403de71 to mx.managers.IHistoryManager.
at mx.managers::HistoryManager$/get impl()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\managers\HistoryManager.as:96]
at mx.managers::HistoryManager$/unregister()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\managers\HistoryManager.as:144]
at mx.containers::ViewStack/commitProperties()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\containers\ViewStack.as:651]
at mx.containers::TabNavigator/commitProperties()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\containers\TabNavigator.as:504]
at mx.core::UIComponent/validateProperties()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\core\UIComponent.as:5670]
at mx.managers::LayoutManager/validateProperties()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:519]
at mx.managers::LayoutManager/doPhasedInstantiation()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\managers\LayoutManager.as:639]
at Function/http://adobe.com/AS3/2006/builtin::apply()
at mx.core::UIComponent/callLaterDispatcher2()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\core\UIComponent.as:8460]
at mx.core::UIComponent/callLaterDispatcher()[E:\dev\3.0.x\frameworks\projects\framework\src\mx\core\UIComponent.as:8403]

Adding the following code to your main app may resolve the problem. It did for me:

import mx.managers.HistoryManager;
private var hist:HistoryManager;

See:

https://bugs.adobe.com/jira/browse/SDK-13121
http://bugs.adobe.com/jira/browse/SDK-12218

I'm not sure that I agree that it's "Not a Bug" (see Resolution of SDK-12218). I would hardly classify the code given by Rodrigo as unusual or buggy. If the default behaviour of modules is to share managers with the main app (if I understand the problem correctly), then they should be able to clean up after themselves during the unload process gracefully.

Peter Pan 2009-01-04 16:35 发表评论

flex 中module之间参数传递

Peter Pan — Sun, 04 Jan 2009 08:30:00 GMT

试了半天没出来原来是flex的bug，汗啊！

Steps to reproduce:
1. Create an application which loads a module.
2. Pass url-encoded variables along the query string while loading the module. For example:
[code]
<mx:ModuleLoader url="modules/modules/Module2.swf?name=jerry&flavor=chunky%20monkey" />
[/code]

3. Try and get the "name" and "flavor" parameters from the loaded module.

Actual Results:
From within the module, the "this.loaderInfo.parameters" object is empty, even though you passed values along the query string. you can get the values, but it involves a weird mix of RegEx class, URLUtil or URLVariables classe, or writing all your own parsing logic.

Expected Results:
this.loaderInfo.parameters should parse the "url" variable for you and create all the variables.

Workaround (if any):
Parse the URL from within the module and use regular expressions to remove everything up to (and including) the question mark. Next, parse the url-encoded name/value pairs using the URLUtil class or the URLVariables class, like so:

[code]
private function init():void {
// discard everything up to, and including, the question mark (?) in the URL.
var re:RegExp = /.*\?/;
var urlStr:String = (this.loaderInfo.url).replace(re, "");

// Use the URLUtil.stringToObject() method to parse the query-string.
var str2:Object = URLUtil.stringToObject(urlStr, "&");
nameLbl.text = "name=" + str2.name;

// Use the URLVariables class to parse the query-string.
var urlV:URLVariables = new URLVariables(urlStr);
flavorLbl.text += "flavor=" + urlV.flavor;
}
[/code]

The Flex documentation uses for loops and String.split() and rewrites most of the logic themselves, but that solution is a bit overkill considering the two solutions above work (and with a lot less code)

Peter Pan 2009-01-04 16:30 发表评论