Jump to content

Search the Community

Showing results for tags 'accuracy'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer
    • Report a Bug in Affinity Photo
    • Report a Bug in Affinity Publisher
    • (Pre 1.7) Affinity Range Bugs Forums
  • Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 5 results

  1. I was going to post this as a Feature Request but I thought I see what people thought about it first. We often get questions about problems that are eventually grounded in the fact that the numerical input fields don’t always show a totally accurate value, sometimes because the Preferences have been set to show too few decimal places. For example, a rotation field may show 10 degrees when the actual value is 10.3. What I suggest is that the numerical input fields have some kind of indication to show that the value displayed in the field is not the same as the (internal) actual value. There are probably a few ways to do this and some are more obtrusive than others. * One way could be to display values that were not shown accurately in a different colour, but that might not be good for people who want an uncoloured UI. * Another way could be to have an extra coloured ‘flag’ at the end of the field to show where the full value was not being shown but, again, that’s probably not good for an uncoloured UI. * My personal favourite, at the moment, is having a line at the top or bottom of the field (maybe all the way along, or just part-way) that shows whether the value in the field is actually higher (line at top) or lower (line at bottom) than the actual value. My attached image shows these three options, all showing that the Y value is actually higher than the displayed value. What does anyone think?
  2. How is it possible that if I have a 3x3 mm cell grid set it doesn't fit with a 15x3 mm rectangle? It is just an example, it happens with any other guide and object configuration. Attached screenshot so you can see what I am telling you (I have it configured in Spanish, but I think it is clearly understood) Thank you and health for all. P.S. I really like your program, but it is impossible to work correctly with this bug.
  3. The area covered by the tap of a fingertip, and the one of the tip of ApplePencil, are too big, so that it is difficult to select a handle or an object if those are little enough. So the intention to move an object after selecting it, frequently results in changing its size, or viceversa. When "seeing" the area covered by the tap (vía preferences) this is TOO big in radius (I know, its visible size is probably artefactual). The real result is extreme difficulty to either select or resize when you want (in not-so-big objects) Could be problem of System features (iOS) or of Designer features (if is this, then is a bug, or if iOS is guilty is a problem to solve) Emilio
  4. Hi, When I freehand sketch ('Draw Persona'), Designer makes certain choices when interpreting my Vector Brush-ed or Pencil-ed lines into vectors. ¿¿ Is there a preference or settings dialog to control how accurate the resulting sketched path is?? Like: many nodes for 'Accurate', fewer nodes for 'Simplified, etc.? thanks, - pbass
  5. I bought Affinity Photo and Designer and want to support a great competitor to Adobe. I have run into a problem .. I wonder if you can help? I have an original design in Adobe Illustrator format - attached. backprop_error_example2.ai I have an export to PNG from Adobe ... also attached. Then I have a PNG export from Affinity Designer after it loads the AI file - also attached. You can see that: the quality of the text rendering is not as good the colours are not accurate (see the big rectangular blocks) the brushes (object outlines) are not that accurately reflected, they are too "heavy / bold" When importing I made sure "favour editable text over fidelity" is NOT ticked. I want fidelity. Not sure what this actually dees. On export I selected Lanczos not bilinear to improve partially the rendering. Some have said elsewhere that text should be converted to curves .. which I don't really want to do .. but as a test I did. The image is attached. converting text to curves (Layer -> Convert to Curves) then exporting as PNG has no significant effect. Any ideas? Going forward I'd like to start new designs with Designer but unfortunately I have a legacy of AI files and I need their output to be consistent with previous exports. Thanks in advance.
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.