Jump to content

orokusaki

Members
  • Content count

    10
  • Joined

  • Last visited

Everything posted by orokusaki

  1. When one tabs between inputs in a form, whether in an app or on the web, the expectation is that the contents of the focused input will be selected. So, if I set the value of the R input to 80 and then tab from the R input to the G input where the value is currently 05, and then type 80, the value of the G input should now be 80. Instead, it's 008. This is because the program thinks I'm trying to prepend 80 to the existing value of 05. The first key stroke (8) is cancelled by Affinity Designer because prepending 8 to 05 would result in 805, which is invalid. Then, it allows me to enter the 0, because 008 is really just 8, which Affinity Designer normalizes to 08. Affinity Designer should instead select the contents of the G input when I tab to it, so that I can just begin typing, as expected. I suspect the same logic would work fine everywhere, since Affinity Designer normalizes values everywhere (e.g., adding " px", etc.). Note: I'm only speaking with regards to tabbing. When clicking into a field, the UI functions as expected.
  2. Awesome, thanks @MEB! I guess, even after having read the explanations many times, I still don't understand the value of the dpi setting, then. So, should I be using 72dpi, even when designing high-resolution graphics for Retina displays? Is there a time when it makes sense to use 144dpi?
  3. The problem I'm having is that Pixel View modes and exports are half the size they should be. If I export at 2x, the exported file, while named @2x is actually the resolution of a 1x export. Same goes for the Pixel View modes, they're half sized (see screenshots). So, when I export or preview at 1x, the image is pixelated down to ludicrous mode. Until today, I hadn't used Affinity since the last update (I'm now on 1.4.1), so I suppose this issue could have been introduced in 1.4.1. Here are some screenshots I took while zoomed at 100% (document setup included as well): Vector Mode (Pixel View Mode disabled): Retina Pixel View Mode: Pixel View Mode: Document Setup:
  4. Firstly, I'm on OS X 10.11.1 (15B42) and using Affinity Designer 1.3.5. make two 12px by 12px squares (one would probably work, but two is what I had) enter export mode select one square and click "create slice" in the layers panel select the other square and click "create slice" in the layers panel click the "slices" tab to open the slices panel select one of the slices use your arrow keys to move the slice around Witness the bug - at step 7 the square moves instead of the slice, even though the slice is what is selected. If I use my "delete" key, the slice is deleted, implying that I'm correctly observing that the slice is in fact the thing I've selected. Because of this bug, I cannot accurately move a slice around. I have to instead move it around with my cusor and use snapping to line things up more quickly. Meta note: unordered lists herein do not appear to work.
  5. orokusaki

    Slice UI bugs in Export Persona

    @pauls - I was excited about the update today. It seems to have fixed one aspect of this bug (the issue where using the arrow keys when a slice is selected causes the underlying object to move instead of the slice), but it doesn't address the other issues (the slice itself still does not move when it's selected and I use the arrow keys). Another issue is that if I select a slice from the slice panel and use SHIFT + arrow down to select more slices in that panel (similar to SHIFT + click or CTRL + click to select more slices), then hit delete, only one slice is deleted. If I instead click each slice to select it (using CTRL + click for each), hitting DELETE causes all of them to be deleted, correctly. This issue won't really be relevant once the former issue is addressed (using arrow down should actually move the slice, rather than selecting more slices).
  6. orokusaki

    Slice UI bugs in Export Persona

    Sorry to be a pest, but will this be fixed in the next release? This is a really nasty bug for anyone using Affinity Designer in a web design / slicing project. Another thing, perhaps more of a feature request than a bug, is that it would be really nice to be able to copy / paste a slice, since most web designs have things like rows of images, etc. The paste would of course result a new slice that is auto-named. P.S. Once developers have incorporated bugfixes for these sorts of reports, it'd be a good idea to post a reply to the original post, just to keep people in the loop. This is important, to avoid the Pixelmator dilemma, where users never know if their bugs are being fixed. In Pixelmator's case, the users get outright ignored, but that's beside the point.
  7. FWIW, IMHO, the solution to this should be that an art board *MUST* have a whole pixel size. There isn't any added value in half-pixel art boards.
  8. orokusaki

    Affinity Designer Bug Report?

    This bug drives me absolutely bananas. I beg of you to fix this in the next release, Affinity team. P.S. I searched Google for "Affinity Designer support" as a shortcut, so that I could report this very bug, and the first result on Google was the bug itself...
  9. This would indeed be an awesome feature. I think it should provide the ability to SELECT an exact transparency / color / stroke from an object or ALT + SELECT a raw display color (which wouldn't care about the settings of an object or whether it was raster, etc., but would instead just grab the color being shown to you).
×

Important Information

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.