Welcome to Axure Community Site Sign in | Join | Help
in Search

When are pixels not really pixels?

Last post 11-30-2008, 6:24 PM by Custa. 2 replies.
Sort Posts: Previous Next
  •  11-27-2008, 8:57 PM 3770

    When are pixels not really pixels?

    I noticed that in the 5.1 version of Axure that we have the choice on output to use  either px or pt as a unit of measurements. Unfortunately I don't think this really belongs there  as it is a little hard to decipher in the design surface. In the Style Editor when I am crerating styles I would expect to be able to input there the same units of measurements as I would get in my output but instead I have to do a conversion of my outputted type back to pt's to get the  desired look that I need to make my wireframes fill space as I would expect in the browser.

     

    I did find a nice little resource that helps me though but it would be nice if we could set the unit of measurement (pt, px, em, etc..) in the document and have it apply to both the design surface and the ouput. For those that are also struggling with this you should print this page.


    Mark Johnston
  •  11-28-2008, 4:54 PM 3772 in reply to 3770

    Re: When are pixels not really pixels?

    The font sizes in the wireframes are stored in pts. The size of the text on the screen is then dependent on the DPI setting. Axure RP 5 assumes 96 dpi by default regardless of the dpi setting on your computer. This can be changed in Wireframe->Grid. The reason is so that the text size remains consistent across computers.

    This is also the reason for the option to generate to pixel sizes for the prototype. This way regardless of the computer where the prototype is being viewed the text size will remain consistent.

    We're considering an option to use pixel sizes instead of pts in the designer.

  •  11-30-2008, 6:24 PM 3775 in reply to 3772

    Re: When are pixels not really pixels?

    Ideally the document should have the ability to set the size and those settings are respected at prototype export. Ideally the use of px, pt, em, and percent should be available. I really don't feel that the option between 120dpi and 96dpi really adds any value here to me. 96dpi is the defacto standard on modern OS's and no matter what I choose a pixel is a pixel. pt's really are a print measurement and to me really don't belong in the software industry, otherwise you'd also have a 72dpi which is where the measurement was derviced from.

    To keep things consistent across all machines it doesn't matter what unit is used so long as the designer is fully aware of what they are doing and at this point to do that, I need a cheat sheet next to my keyboard to make the conversions.

     

    I look forward to some cleanup on this to stop some confusion.


    Mark Johnston
View as RSS news feed in XML