Jump to content
You must now use your email address to sign in [click for more info] ×

smallreflection

Members
  • Posts

    233
  • Joined

  • Last visited

Everything posted by smallreflection

  1. A big +1 for this for me as well, although I can live without it in the meantime. "Transform each" when making individual selections (vs. selection of a group) is default functionality in Sketch and some other apps, and it is quite handy—it could potentially just be a checkbox option in the Transform panel to toggle on and off.
  2. Perhaps I'm missing something, but does batch processing resize currently work in this beta? I've tried pure numerals and pixel values but there's no change in the processed file dimensions.
  3. As I've been working in Designer recently, it's a bit frustrating when adding a swatch from the Pantone set the default has the name of the next unused global color (e.g. "Global Color 7") instead of the name of the Pantone swatch. It would be great if all swatches, even if global, contained the name of their value so I didn't have to enter them manually (including CMYK and RGB swatches).
  4. Excellent. :) I know this is an additional thing, but any chance a pattern fill option might squeeze in as well?
  5. One bug I'm still noticing in this most recent beta is grouping a variety of layers or folders tends to scatter the layers/folders around instead of keeping them in place.
  6. Love the progress on Macros and Batch processing! :D And the halftone filter is awesome, as well. :)
  7. Resurrecting an old post—has anyone used After Effects and Apple Motion enough to compare how sufficient Motion is for UI animation?
  8. As an aside, it would be really, really great for Affinity Designer's growth if in the future it did support some types of plugins!
  9. Having a search box included in the standard color library panels is fantastic, but when editing a color's fill (for instance, replacing a pantone global color with another pantone color) is quite tedious without the search being included in that second overlaying library panel. Any chance it could be included there as well? :) It would also be really nice if the currently active color was highlighted or outlined slightly in some way.
  10. I know to some this may seem to be going too deep, but one feature that would be tremendously helpful in Affinity Designer for UI work is the ability to rename multiple layers or find and replace in a selection of multiple layers. When creating a lot of different similar layers, it's great to make a selection and be able to add or change a folder prefix, for instance. Adding the ability to create a shortcut for renaming a current layer also helps make things just a bit faster in heavy workflows. I use these in plugin form elsewhere and it saves tons of time.
  11. Interesting—I had just activated about 72 different fonts from the Tolyer family and instantly received a crash, but did this update and (fingers crossed) so far it's working! Edit: cancel that. I quit, restarted, and now it's failing on each open again. :blink: Then I deactivated the entire Tolyer family, and now it seems to work. Very strange.
  12. So it does look like the crash is definitely font-related (for me, anyway)—I disabled all of my active fonts (about 800, since I don't know exactly what was going off), and Beta 5 opened up just fine again. I reactivated all of the fonts from my last doc without problems, so I'll have to keep an eye out to tell what exactly was causing the issue. :)
  13. I noted that in the error log, but can't think of anything I installed new just before the crash (I had installed several fonts a few days ago, but it was working fine with them, my MAS version seems fine with them too, so it's strange if that's doing it. My install on my work machine has a lot of the same fonts installed as well and seems fine—it seemed to go haywire when I was trying to move around in a huge file (~500mb+), and it hasn't opened since. At home later I'll try disabling my whole font library via FontExplorer X and see if it will work. :blink:
  14. Hmm, I got this working at work fine, and tried at home and got it to open up a hefty size project once, but after one in-project crash now I'm getting a repeated crash when I attempt to open it, getting nowhere. I attempted a reinstall but I still can't get it to open. Attaching a crash log here. I attempted to go back to 1.5 beta 4 and even beta 3 but for some reason on this machine even those are crashing on every attempt at opening now. Any clues or help would be appreciated! affinity-1.5-beta5-repeated-crash-log.rtf
  15. I just tested again to be sure—it's happening all the time when just Shift + dragging, not only when Clone + Shift + dragging. The problem doesn't occur when just clone + dragging or dragging alone). So Shift seems to always be acting as an off-pixel-grid modifier key instead of just keeping the shape on the pixel grid and moving locked on an axis. Since Opt/Alt seems to be an off-pixel modifier already, it seems strange that Shift would be doing the same thing. I noticed if I keep the grid turned on with snap to grid, it definitely helps this problem a bit, but it seems like it shouldn't be going off-pixel even without the grid.
  16. Take a look—I've recorded a clip including modifier keys: am I doing something wrong here? https://www.dropbox.com/s/wgso02vaxlnie7t/affinity-snapping-test.mp4?dl=0
  17. Right, that's what I had expected as well. However for me, Shift+dragging an object on the X and Y immediately takes it off the pixel grid, every time, at least it's seeming to. I'll try to drop a screencapture into Dropbox to show what I'm seeing.
  18. Ah, that makes a bit more sense now I think. I had completely forgotten that Cmd+dragging also duplicated, I'd been so used to using Alt/Opt instead. That does indeed keep pixel-snapping going, however I'm pretty used to Opt/Alt (now Cmd) + Shift dragging when duplicating elements, and adding Shift does tend to almost always bump an item off the pixel grid, apparently because it's switching to primarily snapping to the preview shape being cloned. That makes sense in theory, however for UI design and the like it would be nice if that was perhaps a setting to turn off/on, so that when doing precise work with a lot of shapes, we could still use Shift to keep elements in alignment with each other and roughly snap them to other objects, but ensure that everything still stays snapped to the pixel grid. It seems like if you wanted objects to primarily switch to snapping in relation to another shape instead of the pixel grid, you'd just turn the Force Pixel Alignment option off. I suppose alternatively though, if object snapping is keeping my elements in alignment, I don't really have a need to use Shift so much, and perhaps I should just break that habit. ;) Thanks!
  19. Correct, and that's what I thought I'd done. I went back to do another test and it seems to be working as it should, so I think I realized what might've been doing it—when option-dragging a layer to duplicate it, because Opt allows you to break off of the pixel grid, I think that's what was causing certain layers and artboards to get off by a pixel even with Align to Pixel and Move by Whole Pixel on. Hadn't realized that before. Edit: I just went and tested again, and in addition to snapping to other objects potentially jumping it off a pixel, Shift + Dragging also seems to always bump an object off the pixel grid. I'm sure that's a tricky thing to solve, but that seems to be going a bit too far in allowing objects to get off.
  20. Perhaps I'm doing something wrong, but pixel-snapping and export size to me is one of the biggest outstanding issues that takes up a lot of time. Essentially, even when keeping Force Pixel Alignment and Move By Whole Pixels turned on and making sure a shape is a whole pixel measurement, moving a shape, group, or whole artboard often still positions the shape on a partial pixel, resulting in an additional pixel on export. The only workaround I've found for this is to go back to the Draw Persona, manually input an even pixel coordinate into the transform panel, then reattempt to export. That's fine for a few items, but if you're dealing with setting up numerous layers or artboards for export, that can be quite time-consuming.
  21. Hey guys, one bug I just ran across in the last beta is using a curves layer with just a single point and pulling out (in either the lights or darks) causes this weird drop in that throws all of the colors off.
  22. One of the only things I can't quite figure is how does the unlock from center or from outer edge symbols in the bottom-right of the panel function that differently from each other?
×
×
  • Create New...

Important Information

Terms of Use | 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.