[flexcoders] Flex 4.1 scrolling problem
I'm committed to using a spark container because I need to use the spark states model. I would like to create my own component that would automatically scroll as necessary and appropriately adjust the scrollbar on a browser window resize. This generic scrolling container may be included in a tabnavigator or other containers (that should not scroll) to get the desired layout. It look like all I need to do is wrap the spark container in a Scroller or link a Scroller to the container. My problem is that AFAIK you cannot add elements to a custom mxml component if you've already added a component (like a s:Group ) to the component defnition. I.e. I cannot use mxml to define a custome component that is an s:Group inside a Scroller. So I guess the approch is to create a custom actionscript component. I'm hoping somebody has already solved this problem and can point me toward a link or provide a snippet. I plan to upgrade to Flex 4.5 in a few months if that's relevant.
[flexcoders] Re: Flex 3 - 4 migration and s:States - SOLUTION
OK, I think I've got it although I don't really know why. The base mxml component and all of its children are in a package/directory called sections so the code needs to be in EACH child as follows: sections:_section xmlns:fx=http://ns.adobe.com/mxml/2009; xmlns:s=library://ns.adobe.com/flex/spark xmlns:mx=library://ns.adobe.com/flex/mx xmlns:com=components.* xmlns:sections=sections.* xmlns:mds=mds.* creationComplete=_section1_creationCompleteHandler(event) sections:states s:State id=Oct2010 name=Oct2010/ s:State id=Oct2011 name=Oct2011/ s:State id=Apr2012 name=Apr2012/ s:State id=Everything name=Everything/ /sections:states FYI, I have different versions of this app that must be supported simultaneously and based on a few fields in the app, the actual version can change in mid stream. Everything is just there to help me with initial debugging.
[flexcoders] Flex 3 - 4 migration and s:States
I'm migrating a flex 3.0 application to 4.0 (or 4.5, doesn't matter much) and I want to use the new state features of includeIn and excludeFrom. I have a user defined base class in mxml and i inherit from that for my 'working' classes. I have this code in my baseclass mx:TitleWindow xmlns:fx=http://ns.adobe.com/mxml/2009; xmlns:s=library://ns.adobe.com/flex/spark xmlns:mx=library://ns.adobe.com/flex/mx xmlns:com=components.* currentState=Oct2010 mx:states s:State id=Oct2010 name=Oct2010/ s:State name=Oct2011/ s:State name=Apr2012/ /mx:states . . . - working class contains - mx:FormItem includeIn=Apr2012 ... /mx:FormItem and the error is State 'Apr2012' was referenced without being declared. A.mxml line 66 /MdsClientBeta1/src/sectionsFlex Problem --- comments I tried s:states rather than mx:states but it could not resolve name Must s:states be used only in s: components or can they be used in mx components?
[flexcoders] mx:Datagrid nowto detect drop column
I would like to move cell contents around in a datagrid (or AdvancedDatagrid if necessar) but so far all I can do is detect the row of the drop target. II need to get both the row and column index of the source and destination of the drag-n-drop action. Any suggestions please???
[flexcoders] Re: Mail Merge...
FWIW FOP from Apache's XML project group does a pretty good job of generating PDF. It would of course have to run strictly on the server. I appreciate all your advice on Print bugs, I thought I was just experiencing noobie pains. I guess I'll just settle on displaying an HTML page and let them print that. It's too bad, printing a single page is really nice in flex, but if it goes downhill, as many have said, with multi-page grids, screw it! I don't have the time to make it work.