Jump to content

Search the Community

Showing results for tags 'aw-3198'.



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

  1. After setting up a keyboard shortcut by hitting the a numerical key on the top of a standard querty keyboard in the keyboard shortcuts settings panel, both the numericalkey as well as the numpadkey representing the same number trigger this new shortcut. For example, pressing the '1'-key on the top of the keyboard together with alt to assign a shortcut results in the same keystroke as pressing the 'numpad1'-key together with the same alt-key. This is not what I would expect, because these are two different keys with no technical connection. Treating both keys as the same limits the amount of keystrokes we can assign. It's also errorprone, because we don't expect the alt+'numpad1' to trigger an action we assigned the alt+'1' (1 on the top of the keyboard). So it seems like Affinity doesn't store the key-code, but the key-value to bind a keyboard shortcut. But it should store the key-code instead to assign the right key only. [edit] Another problem caused by this is what I'm facing right now: I have a rotation assigned to Alt+2 (addressing the regular '2' key on the top of the keyboard). But when I'm in a textframe and want to enter a special character by using an alt code sequence (so while holding Alt hitting a code-sequence like numpad-0, numpad-2, numpad-3, numpad-3 to have a 'é'-symbol) the alt-way to enter a symbol doesn't work anymore AND the canvas will rotate. And that's obviously not what should happen here. I wouldn't be surprised if there's a connection between this one and the no-difference-between-alt-keys Issue I reported earlier. Maybe the same solution could fix both? That would be nice! Thanks in advance!
  2. Trying to assign keyboard shortcuts to my character styles, I've discovered that the numeric keyboard input is interpreted as regular numbers. This has been checked against different keyboards (apple and 3rd party) This greatly reduces the availability of keyboard shortcuts to use with styles, as most of numbers are already assigned to other functions, specially on command+number combinations. Command+numeric keyboard is a great way to arrange shortcuts for styles. If this is not a bug, I suggest to allow Publisher to detect the difference between the two types of numbers, as is the case on InDesign, where numeric keyboard numbers are identified as such. (I know, i know, comparisons are not the point here, but…)
  3. I created shortcuts for moving (arranging) layers up/down ctrl+numpad0 and ctrl+numpad1 because I use it for years now in different applications. First problem: the preferences / keyboard shortcuts pane doesn't show if it conflicts with zoom shortcuts !! Second problem: the shortcuts doesn't work at all.
  4. By default the number keys set opacity - which is fine. BUT AD doesn't distinguish between the standard numbers and the numeric keypad, to which I'd really like to assign a bunch of other shortcuts. With 15 keys on the numpad, and at least 3 different modifiers, there are >45 keyboard shortcuts going to waste here! Also, under the current system, if I do set a numeric keypad numeral as a shortcut, it doesn't warn me that there is an existing clash with the opacity function... worst of both worlds! Thanks for your consideration.
×
×
  • 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.