Jump to content

Search the Community

Showing results for tags 'input'.



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 & Discussions
  • 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 23 results

  1. It's easier to operate on small values, also there will be no need to do math (yay) So let say I want to rotate object clockwise by 67 degrees. That's easy - just enter 67. But when rotating counterclockwise things starts to look more complicated. I must calculate 360-67 to know it's 297... damn 293. See? What about just entering -67, and moving on? (maybe I mixed directions, but general idea still holds up)
  2. I have been working on graphic novels, which has had me regularly hopping from one persona to another, and using a constant input mix of touch screen, surface pen, mouse and touchpad (version 1.7.2 of Photo, Design, Publisher, on Microsoft Surface Laptop with latest W10). Here are some input issues that I have encountered. - Sometimes Publisher just stops taking drags. Can choose layers, objects or menu items, but can not resize, draw lines or move anything that involves a mouse drag. Restarting the program sometimes helps, sometimes I need to restart the computer. - Sometimes when I use a menu item such as the opacity slider, the program takes no further inputs before I click the slider away, as if the slider was a popup window with priority. - Sometimes I can not select a specific object or menu item with a specific input device. I have found no consistency with this, bus basically I try to click on something and it won't register the input, so I try my options of mouse and touch inputs until I find the one that was somehow required. This feels like a hardware issue for all I know, but has not happened in other programs. - Pasting an image from clipboard creates the layer with the intended image, but I can find no trace of the image on the work area. I resolve this by saving the image and placing it from the file. - Placing an image sometimes doesn't give a preview as I drag the mouse to shape the area, and often resizes or even rotates the image. I found no way to help this but readjusting the image. - Not a bug but there is no touch scroll for the Pages view, this has me regularly selecting and throwing pages about with my thumb. Thanks for the otherwise great programs!
  3. Hi there! So with the new version of Designer for the iPad, I am having problems inputting numbers into either the palette of the resize dialogue box. I have a document that's 8.5" X 11" and I am trying to resize the canvas to 8" X 3.5". I am not using artboards. I am using the resize function in the app. When I try to resize to the new size, the file becomes 8" X 3". It disregards the .5" for the height. I have tried multiple times and the same thing happens. I have made sure that the lock icon is not selected and it still doesn't work. I'm wondering if others are having this problem. The experience is similar in the color palette. I will click on a color, like Cyan and change it from 60 to 40. WHen I hit okay, Cyan may jump to 100, not change at all or another neighboring color like Yellow may change its numeric value. Also, for export, there are files that I have that if I select an artboard to export as an image, the app will not recall the size of the artboard. I have to right down the actual size and type it in manually. There have been times that the lock icon doesn't work properly, and if I change the width, the height will not auto adjust to compensate for the new width. These issues around units are barriers for using the iPad 100% without having to switch back to the desktop. And as I've mentioned in earlier posts, adding more after the decimal point and not rounding after one decimal will really help too! Thanks for all you do! Overall, this software blows my mind and really makes being creative a joy!!!!! All the best! Stephen
  4. Temporary input is shown with wrong font, size and position. (IME's default font?) I assume this is because you are using Windows' built-in text display engine but Affinity's for this part unlike Mac version? It's little inconvenient and sometime it will be a problem to guess the final output. I know implementing custom text display logic like Mac version is tough and problematic. But I would like you to implement it like Mac version at some point.
  5. When I type arrow keys(i.e. down then left) while typing Japanese(refer p1), the same sentence I typed will be added next to the sentence I typed.(refer p2) on Japanese input, there are two steps to input text. First, type a sentence I want and this is input preview and the sentence will be highlighted.(means it's temporary and not regular text) Then when I type enter or return, it will be fixed as regular text and highlight on the text will be disappeared. Usually if I type down arrow while previewing, I can choose predicted sentence below input preview.(refer p3) But I can't choose predicted sentence on Affinity. While previewing input, commands to manipulate predicted sentence are assigned to arrow keys on Japanese input. So I'm supposed to be able to choose a predicted sentence with arrow keys.
  6. Designer 1.6.1.93 Surface Pen right click doesn't work at all, so I have no way to call right click menu with the pen. It slows down everything. Touches are still equal to pen strokes, this is NOT right, please make the app distinguish them from pen strokes, cause each touch paints things and it destroys the experience. Moreover touch can add more functionality by performing operations of for example Move/select tool while you're actually using any other mode, more convenient, more functional, isn't it? Thank you
  7. After a while in Designer, keyboard input for hotkeys (e.g. P, Ctrl+J, Ctrl+S) and Art/Frame text input do not work. Keys like Shift/Ctrl when transforming an object in the viewport still work, as well as zooming using Ctrl+Scroll, and property text input (e.g. names, transform values, brush size, etc.) still work. I've noticed that this is usually preceded by Designer freezing for a couple of seconds, and then once it resumes the issue starts. The issue can be fixed by restarting Designer, until it freezes again. Note that this issue only happens on this specific laptop and not on my Windows 10 and Windows 7 desktops. The issue has started recently - in the last one or two updates most likely. My specs: Windows 10 x64 Laptop Intel HD Graphics 620 & NVIDIA GeForce 940MX Intel i5 7200U Quad Core
  8. This problem still exists, even on the latest 1.6.4.104 release. I'm having trouble working around for multiple art-boards each time I open the document. I have posted a video to explain what's troubling me. As you can see, this problem is only with the art-boards. And also, the values once entered in the document creation window is stored in the document setup field and it doesn't update at all. Please watch the video to understand the issue more clearly. Please solve this issue soon. Thank you!
  9. Hello, would it be possible to limit input from tools, specifically the brush tool, to only stylus input? That was we could freely place our hands on the screen, pan, zoom, etc. without the fear of making marks. As it is now, whenever I'm drawing or paining, I have to go back and cleanup marks made by my hand. Thanks!
  10. snuggleton

    Pen performance poor

    I've noticed that Affinity Designer sometimes slows down drastically when I'm using a stylus. I'm not talking about drawing in particular; interacting with the UI is even worse. Simple things like locking a layer or selecting a color sometimes take several seconds. Everything suddenly performs as expected when I use the trackpad instead.
  11. This week, this happened several times: when using (randomly) some boxes such as kerning, text size (and other settings in different panels), it makes jump affinity to another app, making Designer disappearing and focusing on another window. The only solution I found is to separate Affinity on new space (mac) and to open in a full frame mode. If not, I can reproduce this really annoying bug. N.
  12. When I'm in a numeric text field, holding down the Shift key as I tap the arrow keys should increase/decrease the value 10x. (At the moment this key combination acts to select the text before/after the insertion point, which, while standard behavior for text fields, is not the expected behavior for numeric input fields.)
  13. Please consider adding a HEX color input box for the color pallete. Sometimes it's just as important to be able to input a color into the pallete as to extract one and this would be very useful for web design.
  14. Hi all, I just noticed the following buggy input behavior in the layerFX panel: if you: 1. type in your value and 2. immediately hit "tab" key to go to the next input field (which does not happen in case of layerFX panel, but that is another story, which is already posted as an other issue) then the new input value will be replaced by the former value. See attached video. In the first part of the movie, I typed in a value and waited 1 sec. before continuing with "Tab" key. That accepts the new value. In the second part of the movie, I did it rapidly - which shows the bug. Maybe it has some similar reasons to: https://forum.affinity.serif.com/index.php?/topic/24595-tabbing-documents-isnt-smooth/ Cheers, Stefan AD_Bug_InputAndTab.mov
  15. Hi, strickt speaking I have declare the current behavior of the input fields when using arrow keys (shift+arrow key) as buggy in the following 2 situations: 1.) if a value is "1,5px" and you press e.g. "arrow up" to step 1px up status quo: result is: 2px expected: 2,5px So the "1,5px" will be rounded to 2px instead of adding 1px But in the next usage of "arrow up" 1px will be added 2.) if a value is e.g. "12px" and you press "shift+arrow up" to add 10px status quo: 20px expected: 22px So the "12px" will be "rounded to 20px" (add 8px instead of 10px) But in the next usage of "shift+arrow up" 10px will be added The current problem I see here is, that there is 2 different actions with the same keyboard action. Which is in general not a problem but the AD does not give any feedback nor it gives me the option to prevent that first action, which I do not want to trigger. At least I would recommend to have this as an option in the preferences, so that every user can decide if the "first rounding action" is welcome or not. Cheers, Stefan.
  16. Hi, the following situation: for example I want to change the width of an object. I click into the input field ... within the "transformation panel" ... hit return - the focus stays on that input field which is NICE in case of using tab to switch to other input fields. BUT: when hitting the "Esc" button I would like make sure to release the focus of that input field so that I can go on in my work with AD. Now it leads to confusing situations like: if I want to go on with another tool like Zoom (Z), or Text (T) ... the still focused input field leads: 1) to entering the input field, 2) setting the value to "0" and the cursor is blinking. I have to click "Esc" again and the desired tool as well. Improving the current behavior would, at least in my case, lead to less confusion and saving mouse clicks >> increasing efficiency. Thanks for thinking about it, Stefan.
  17. Hi there, the input fields of slice names in Export Persona do not accept CMD+a to select all. Maybe it will be fixed "automatically" with that similar issue: https://forum.affinity.serif.com/index.php?/topic/24832-input-field-of-transformation-panel-in-export-persona-does-not-accept-cmda/ Thanks guys for your work, Stefan.
  18. Hi, I have got the following issues in the color window (see screenshot): 1.) focus the e.g. first color value input field ... then hit tab to get to the next input field > the slider thumb of the next RGB value will be focused (which is not what I really expected to be honest) But the slider can't be altered by left/right/up/down in any way - so it could be skipped 2.) tabbing from the sliderThumb to the next input field does not work > instead AD UI will be toggled
  19. Transform panel : when I press 'Enter', it will quit the process. Stroke panel and Opacity Box : when I press 'Enter', it remain in the process so when I try to press any shortcuts, the values in the input box will be edited. I really often adjust stroke values then hit 'Enter' and then press 'P' to use pen tool to continue drawing but I cannot. It's really awkward for me, please fix it for the next version. Cheers. :)
  20. Hello At this moment, the input fields in the Affinity programs behave in a way that is not native to OSX. I don't know if this is a deliberate choice, but I feel like it would be nice if they behaved consistent with other OSX apps. I also noticed that not every input field behaves the same in Affinity. An example in the Transform palette: - When hovering over an input field, the cursor should transform to the text-selection icon. - Clicking in an input field yields the expected behaviour; you can start typing where you pointed the cursor. This works perfect. - When using the tab key to jump from field to field, I expect the content of that field to be selected so I can immediately start typing thus replacing the previous content. But right now, if I start typing, my typing replaces the quantity while the units (i.e. px or mm) stay put. I get that you designed the input field this way because in most situations, the designer wants to adjust the size in the same unit. But when this is not the case, a few extra actions are required to clear the input field. Often I want to use the expressions in those fields like "sh" or "sw/2" (which are terrific by the way!). So if I jump to the height input field and type "sh" and press enter, nothing happens because it keeps the px unit and thus the expression is incorrect. In my opinion, this wouldn't be a problem if the whole content of the input field was selected on tab-jumping to it; if I just wanted to change 200 px to 400 px I could type "200", and Affinity would automatically append "px" (as it does now), but if I wanted to use expressions, I wouldn't be hindered by the sticky unit. I'm looking forward to hear your opinion! Bauke
  21. Here’s a little but important one, in my opinion: If you click an input field in the UI it should highlight the entire current value that’s there so that you can type immediately to overwrite it. Currently, if you click into an input field, it just sets the cursor in the respective position and you have to either do another double click or even a triple click (depending on the value present) to highlight it, or do more or less complicated keyboard actions to delete the value. This annoys the hell out of me. I want to click once and type a new value.
  22. In all other color modes in the color panel, when a value textbox is highlighted (as in, with a light gray glow around the textbox), as soon as I start typing, the first keystroke turns on "edit mode" (textbox background turns white) for that textbox, removes the current value and replaces it with whatever I'm typing. Intuitive. Except it doesn't work that way in RGB Hex mode. Instead, it will behave in different ways based on my observations: Sometimes, it will turn on "edit mode", but not remove the current value, and place the text of the typed keystroke in between the two characters of the two-digit value. (I've observed this when the textbox has a current value of "00", but not always replicable.) Other times, it will turn on "edit mode", accept the typed keystroke, pad it with a "0" (so if I typed an "A", it will show a "0A"), but for some reason, place the cursor before the typed keystroke (like so: "0|A").
  23. How about a feature that's seen on some software (including most adobe apps)… where as clicking on a field name with a box next to it for inputting values will auto select the preset values so that the user can quickly input their desired values. For now the user has to manually mouse over into the field and highlight the text to delete/input the numbers, The attached screenshot should demonstrate what I mean. Thank you and keep up the great work Affinity Designer looks VERY promising!
×