Archive for December, 2008

Probable Text woes and their resolution in Fireworks CS4

Below are some of the scenarios with respect to text shifting on the canvas. The user lands in a situation similar to one shown below from all the 4 scenarios.

Text and the bounding box mis-alignment
  1. Scenario: Selecting/de-selecting the text object and trying to move it on the canvas using keyboard arrow keys.
    Problem description: The text within a textbox in Fireworks CS4 on a Mac will move within the textbox and even move out of the textbox if you select and deselect the textbox multiple times while moving the textbox with the keyboard arrow keys each time.
    Temporary workaround: When ever you see a text image going out of sync with its bounding box, just re-adjust the text or double click inside the bounding box. This will make the text object to correct itself.
  2. The above scenario can be seen visually from the video. The video has been provided by

  3. Scenario: Trying to align text elements using mouse either against other objects present on the canvas or a guide, using the cues from smart guides.
    Problem description: When ever we have grids enabled and we try to align a text element against other objects on the canvas using the cue from smart guides, sometimes the text bounding box shifts away from the text image on releasing the mouse.
    It seems this shift in the bounding box is happening when the bounding box tends to snap to the nearest grid pixel and we release the mouse at half pixel less.
    Temporary workaround: Try to align text elements with the following settings turned off. (i)View->Grid->Snap to Grid and (ii)View->Smart Guides->Snap to Smart Guides
  4. Scenario: Range Kerning/Kerning value in CS3 is not the same in CS4.
    Problem description: Range Kerning value applied in CS3 does not give the same appearance when opened in CS4 and updated. The look of the text block totally changes and we need to manually enter the new value to get back the desired effect.
    Temporary workaround: Range Kerning control present in the UI has now been changed to Tracking in FWCS4. Tracking control works the same way as that present in apps such as Adobe Illustrator or Photoshop. To apply tracking, a range of characters has to be selected first, unlike kerning control wherein, just keeping the cursor between 2 characters we could apply kerning.
    For a value of Kerning applied in CS3, if we set approximately 10 times the value of Tracking in CS4, we can get similar looking text element. Ex: if the Kerning value which was set in CS3 for a text element was 10, then around 100 could be the Tracking value which we will have to set in CS4 so that we can get similar looking result.
  5. Scenario: 2 pixel shift in text glyphs when we change area/frame text to point text and vice a versa.
    Problem description: When we change the area text (drawn by click dragging on the canvas using the text tool such that we get an area bounding box) into a point text (drawn by just click once on the canvas using text tool) by double clicking the top right handle or vice-versa, we can see that there is a 2-px shift in glyphs on the canvas.
    In ATE, bounding box of a point text is different than the area text. The area text has a small gap between the glyphs and the bounding box, thus currently when we do such a change; there is a slight shift of the glyphs either upwards or downwards depending upon the point or area text change done.
    Temporary workaround: Create either an area text or point text depending upon your requirement and don’t shift or change from one type to the other. Note that when you convert area text to point text, the glyphs shift 2 px downwards and when we convert a point text into an area text, glyphs shift 2 px upwards.
  6. Scenario: Trying to 9-slice scale a custom symbol or common library element, sometimes the text jumps away.
    Problem description: When we try to apply 9slice scaling on common library element such as a button etc, sometimes the text jumps away from its location. 9-slice scaling when applied to a text bounding box changes it to an area text if it’s a point text which makes the glyphs to shift 2 px from their original location. Moreover in situations where in 9-slice scaling is used to scale the button element, after some point the text tends to break away from its original location.
    Temporary workaround: If a symbol or custom component has text contained inside, then make sure that the text object is placed well inside the 9-slice guides and they are not overlapping. More importantly, make sure that the text element is an area text box (if it’s not then convert it by dragging the lower right corner of the bounding box) and not a point text box.

Share on Facebook