Jump to content

Search the Community

Showing results for tags 'field'.



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 9 results

  1. Is it possible to have a frame text copy text from another? Almost like Fields, where you have a text frame copy from fields, but instead copy from another text.
  2. 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?
  3. Sometimes, when using some mathematical functions in input fields, the Unit Of Measure needs to be given for the expression to be calculated. For example, when I enter “+=cos(30)*10” (without the quotes) into the X field of the Transform Panel there is no effect, but entering “+=cos(30)*10 mm” (with the UOM) moves the selected layer as expected. Also, entering “x+cos(30)*10” (no UOM) into the X field yields no movement while entering “x+cos(30)*10 mm” (with UOM) also yields no movement, so providing the UOM is no guarantee of an expected result. However, entering “x+fraction(2.5)” (no UOM) does produce a movement. This behaviour is inconsistent. This happens on both Windows and OS X (no reports so far for iPad so I don’t know what happens there). This has only been checked in Designer (as far as I know) but all apps need testing, with expressions of differing complexity. Also, the Help for this needs to be expanded with better explanations of what each function does and example usage. For example, the Help lists “cos(t)” as a function but doesn’t say whether “t” should be in degrees or radians. Most functions don’t even have a description, which is a bit limiting. Basically the Help for this should contain much more information but the most important thing (in this case) is to get the functions working consistently. See the discussion (with a small test result table) here: https://forum.affinity.serif.com/index.php?/topic/104444-transforming-an-object-relative-to-its-position/&
  4. Give a new Publisher file the name "A". Save it. Close it. Open file "A" and save it as "B". Open "Fields" in saved document "B" and under "Document Information" the "Title" field will read "A", which is what the name of what the file WAS, not what it IS now. There is a title-filename mismatch that persists. Even if you close the app down and start afresh, the mismatch persists. See attachment. Yes I know, I can manually change the Title field but a) that's not productive and b) it doesn't stick. The title field in "B" reverts to the first document's filename. I could hard wire it, but that defeats the purpose of a field doesn't it? The field seem unable to update itself automatically and there is no manual key for doing so. Win 64, AP 1.7.1.404.
  5. I would like to request that a new field be added to capture the Section or Chapter number. When building Figure and Table captions, our standard is to combine the Chapter number with the sequential item number. Examples: Figure 2.1 The Workflow Process Table 4.5 Parts and Function of the Spread Dialog.
  6. Is the functionality associated with Text Fields working as expected? I'm trying to insert a field into the text frame I added to one of my master pages, and there doesn't seem to be any Menu item to allow me to insert the field into the text frame.
  7. Hello Is this possible in Affinity Designer? I can't find any settings. Thank you.
  8. OK, I'm hitting this bug (or UI gremlin) constantly. My example is for a stroke width, but it seems to apply to all numerical value fields (e.g. opacity). 1. select a stroke 2. click into the stroke width slider numerical field in the stroke panel 3. type to change the stroke width (any value) 4. hit 'enter' to commit the stroke width change 5. hit 'v' key to change the cursor to the move tool (or any other tool keyboard shortcut) RESULT: the stroke is 'zeroed' in the field by the tool keyboard shortcut press, the stroke width change is cancelled, and the stroke width is set to 0 and becomes invisible. EXPECTED: the width change is committed after the enter key is pressed, and the cursor is changed to the move tool by the subsequent 'v' keypress. The expected behaviour works if I substitute a tab keypress for the enter keypress above - I think it's reasonable to expect that the 'enter' key should commit the field change in the same way, right?
  9. Try this: 1. New document. 2. Click once on the Rectangle Tool (or type "M") 3. Click the square to the right of "Fill:" in the upper left corner of the window. 4. Click on the "Gradient" tab. 5. Note there is no field to set the ANGLE. Please add that. Why? Because Illustrator has one and for good reason. Yes, you can set the angle by going outside the Gradient panel, choosing the gradient tool and then manually doing it. But if one is already working inside the Gradient tab (especially for matters of precision), it is only logical that an ANGLE setting should be in there too. Thanks!
×
×
  • 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.