1 Reply Latest reply on Sep 16, 2007 7:06 PM by Ansury

    Support for different fonts in design mode

    Ansury Level 3
      It's very difficult figuring out where to place components in design mode when special fonts are used. Because they take up more/less space than the default font (used in design mode), the actual sizes of components when the app actually runs is never the same as they were in design mode.

      Basically if you're using special fonts, design mode becomes half useless. Is there a way around this problem? Can we at least change the font that design mode uses somehow?
        • 1. Support for different fonts in design mode
          Ansury Level 3
          Heh, just noticed it DOES work on my highest level mxml file (application tag mxml), but not the others. Still experimenting... seems to be a bug of some kind, I guess.

          It seems that if you specifically include the style tag:

          <mx:Style source="../../../css/yourCssFile.css"/>

          It works fine, even for mxml nested in sub folders. Of course, this is ugly- I had to put a bunch of ../'s just to reach the css file I need, AND "refresh" the design view for it to work...

          And why this annoying warning message when I specifically include the CSS into an mxml I want to use design view on?
          "CSS type selectors are not supported in components."