
Registered since September 28th, 2017
Has a total of 4281 bookmarks.
Showing top Tags within 4 bookmarks
howto information development guide reference administration design website software solution online service product business uk tool company linux code server application system web list video marine create data experience tutorial description explanation learn technology build article blog world project boat download windows lookup security free performance javascript technical london beautiful control network tools support course file research purchase image library programming youtube example php construction install opensource community html quality computer feature profile power browser music platform process mobile work user share manage professional database hardware buy industry advice internet dance developer installation search 3d camera customer access travel material standard money test develop documentation review css engineering photography webdesign engine device digital speed event api source management question program client phone discussion content simple story water marketing yacht app account setup interface package idea fast communication compare cheap script market study easy live google resource operation demonstration contact startup
Tag selected: mxml.
Looking up mxml tag. Showing 4 results. Clear
Saved by uncleflo on September 9th, 2011.
Flex doesn’t support adding child components to containers at multiple levels. I.e. it’s not possible to create an mxml component of type HBox with some components declared in mxml inside it, and then use that component somewhere else and put another set of components inside it there also. If you try to do this then you get a runtime error saying: “Multiple sets of visual children have been specified for this component” The reason that this isn’t supported in flex is that there’s not really any way for the mxml compiler to know what to do with the additional components. Any option taken would result in numerous possible conflicts and special cases.
flex components mxml custom programming component development container children adobe solution propagation
Saved by uncleflo on September 6th, 2011.
In general, you should use an FXG document as a standalone component in your applications. This gives you the greatest amount of memory optimization, and lets you reuse your FXG files in other parts of the same application, or in other applications. In addition, by keeping the FXG document separate from the application, you can edit and export the FXG again from a graphics tool. One disadvantage to using an FXG file as a standalone component is that you cannot get a reference to individual elements in it. The FXG component itself is a “black box”; you cannot interact with individual elements from your application or other components. You can, however, still apply effects, resize, position, and trigger events from interaction with the FXG component itself. In some cases, you might want to add the FXG output directly into your application. You can do this, but you must convert the FXG syntax to MXML graphics.
flex document component application memory convert fxg mxml integrations export output xml manual syntax
Saved by uncleflo on September 6th, 2011.
Ok, apparently setChildIndex() only sets the display index number of the item in the container (item #1 to display, item #2 to display, etc.), but doesn't have anything to do with z-index (i.e., layering items on top of one another)? This is exactly what it does!
flex actionscript solution order mxml layer z-index stack display development object howto feedback forum
Saved by uncleflo on September 6th, 2011.
Adding graphics to your applications can make them more attractive and usable. In many cases, you might want to add graphics that are vector-based, and not import images that don’t scale well. You can create vector based graphics in Flex by using one of the following APIs: FXG, MXML graphics, FXG is a declarative syntax for defining static graphics. You typically use a graphics tool such as Adobe Illustrator to export an FXG document, and then use the FXG document as an optimized component in your application. FXG graphics are used by the mobile skin classes because they are so lightweight.
fxg mxml adobe format information compatibility graphic illustrator development api syntax xml skin effect shape text bitmap
No further bookmarks found.