I've run into similar situations before with 3rd party components. For some reason, some of them just utterly break the MXML design mode. I've also done it myself when subclassing the charting components. You just get a big rectangle with a big red X over the whole area.
On Tue, Sep 1, 2009 at 5:46 PM, Fotis Chatzinikos < fotis.chatzini...@gmail.com> wrote: > > > Something wrong probably with your install... > > I do not know what, but here, I 75% of my app is custom and i never had > this problem > (Vista, AND XP) > > Hopefully somebody else can provide some real help thought, and not just > 'it plays here :-)' > > > On Tue, Sep 1, 2009 at 10:30 PM, chigwell23 <chigwel...@yahoo.com> wrote: > >> >> >> This one is starting to really drive me crazy ... placing any one of a >> multitude of custom components on the mxml stops design mode from opening. >> Just grabbed the SteelPotato footerdatagrid to see if it can be seen if it >> is used. Nope - stops design mode. Wanted to try it because our >> implementation of Alex's solution also stops design mode from opening. The >> FlexLib buttons do the same thing - code them into source view and no more >> design view. >> >> How do you deal with this? Our corporate dashboards are starting to get >> very detailed and we need a WYSIWYG view to adjust things. Do we really have >> to compile, run application, view in browser, check, and then go back to >> source mode to increase the width of a button if needed? Any info really >> appreciated. TIA, >> >> Mic. >> >> > > > -- > Fotis Chatzinikos, Ph.D. > Founder, > Phinnovation > fotis.chatzini...@gmail.com, > > -- Jason
