Jump to content


  • Content Count

  • Joined

  • Last visited

About LCamachoDesign

  • Rank
    Advanced Member

Contact Methods

  • Website URL

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

1,187 profile views
  1. For those wondering, what this actually means is support for fonts installed through Adobe’s Creative Cloud app. Nice!
  2. Yeah, the iPad AI seems to have better pattern functions than even desktop AI. The main problem with these Adobe iPad apps is that none of them, neither the legacy or the new ones, support CMYK. So... we're kind of stuck when it comes to print patterns on the iPad. This is an area where Affinity could do a quick 'land grab'. Getting a proper vector pattern editor, both in Desktop and iPad, would help Designer's adoption a lot, I mean a lot, a lot. For example, I have a client that I could fully migrate to Designer if it had vector patterns editor. But without it, there's no way out of Illustrator for him, it's as simple as that.
  3. As far as I know, all recent drivers actually do the opposite of what @Mark Ingram said. By default it allows more than 1024 levels, and you must activate a compatibility option to limit the levels. Does it matter in any way? Nah. I mean, I'm pretty sure anything over 256 levels is indistinguishable to the user. These pressure levels are just manufacturers err... phallic waving. Like the Ghz race of yesteryear, or the DPI race on phones. Also, Windows Ink isn't bad. It's just not meant for art, or at least that's clearly not the focus of the API (despite what MS might publicly claim). That API is squarely aimed at hand writing on pen enabled screens, and it's good enough for that purpose. Let's be honest here, any Windows tablet (meaning a computer device with a pen enabled screen, not a graphic tablet like Intuos) is just not good enough for art. It's not even the hardware itself, that's... serviceable. It's the software. I've had a Surface Pro 1 and a 4, it's been years now since they first came to the market, and no software ever worked very well on a touch only basis. The UIs have never adapted to a touch first approach. Why bother creating a super accurate API if the software UI essentially doesn't work without a keyboard and a mouse? I've tried to make concessions over the years so it "works" , but in the end I just got an iPad with an Apple Pencil. I'll sell my Surface Pro 4 one of these days, replacing it with a regular laptop.
  4. Changing a gradient type when using the Fill Tool adds huge amounts of the same entry, "Set fill type", to be added to the History panel. This is to the point that it will push everything else away, leaving only these repeated entries in the History panel, essentially denying you any way to undo your work. Steps to reproduce: Create or select an object With the Fill Tool drag across the object to create a simple gradient On the context bar at the bottom, scroll to another fill type, like conical Watch as the History panel get absolutely overwhelmed with the same entry over and over I've actually manage to crash the app doing this, but it doesn't happen always See the attached video for a visual guide on how to trigger this issue. Workaround while this bug isn't fixed: With your object selected, DO NOT trigger the fill type popup by tap the fill type name Instead tap the arrows to the left and right of the fill type name Each tap on these arrows will only had one entry to the History panel If you accidentally trigger the fill type popup, either tap away to close it or directly tap once on another fill type, NEVER SCROLL THROUGH THE LIST Directly tapping another fill type on the popup still adds two duplicate entries to the History panel, but that's still better than flooding it and loosing your undo ability Thanks! RPReplay_Final1592384177.mp4
  5. This is true, changing the Coverage Map to that extent essentially gives the shapes a "fake" stroke and "turns off" anti-aliasing for that shape. But there's a middle ground here that can be useful for some people in some situations. That is borrowing an "old" technique from video games. Just do manual SSAA. SSAA, Super Sampling Anti Aliasing, is a technique where vector objects are rendered at a much higher resolution and then scaled down to the desired resolution. A possible fix for some situations like this is to do the Coverage Map trick of MEB, but instead of dragging the left point all the way up, do it only halfway. Then export the image at higher resolution multiplier. 4x is ok, 8x is a good value, and 16x is great if your computer can handle it (anything over 16x is insane). Once the image is exported, take it to Affinity Photo, and scale it down by the same factor. If you exported at 8x from Designer, scale it down by 8x too. This will get rid of most hairlines without jagging all the edges of your image, any hairlines that remain will either be too small to notice or can be dealt manually.
  6. This is hard to describe in words but I'll try: Create two global colours Create a simple shape Apply one global color to the fill Apply the other to the stroke Notice the global colour used in the stroke is highlighted in the swatches panel Switch to the fill Notice the global colour is not highlighted as expected Upon deselecting the object the global colour used in the fill will be highlighted I've attached a video reproducing the issue, it's much easier to understand what's going on, and what would be the user expectation. Let me know if there's any additional questions. Thanks! recordedVideo_Trim.mp4
  7. This is the third global colors issue I reported just today. While the other two could be considered kind of niche or harder to spot, this one is dead obvious. You guys really, really, really need to spend a whole version just tearing down the Swatches panel and rebuilding it in a way that's user friendly and that actually works well in all situations. Select an object. On the Swatches panel press the add current color as global color. That's it, that's all it takes to reproduce. 🤨 You'd obviously expect the object to have the newly created global swatch applied. It doesn't. You need to actually click on the newly created swatch for it to be applied to the object... Attached is a video reproducing the issue. Really consider spending 100% of the time for version 1.9 rebuilding the Swatches panel. Managing colors is a fundamental part of well done graphic design, guessing if our swatches will work on a given situation is not acceptable. Thanks! 3_Trim.mp4
  8. Create an object and apply a global color to it. Editing the said global color changes the object as expected. Then convert that object into a symbol. Changing the global color no longer changes the object. Say that you now apply the global color to this symbol object, it starts working again as expected, but only for that instance. If you delete it and drag in another instance the global color will no longer work again. See attached video for steps to reproduce. Thanks! 2_Trim.mp4
  9. Let's say you add two fills to an object with the Appearance Panel, and to each fill you attribute a different global colour. If you later modify both global colours you'd expect both fills on the object to change appearance. Instead only the active fill changes. The attached video shows the steps to reproduce. Thanks! 1_Trim.mp4
  10. Yeah, it's a real pain. At the moment what I do is convert to global and re-apply all colours to all shapes on the desktop when I'm done. This is of course a pain and it's only worth it on illustrations that likely will have a reuse/recolour value down the line... The whole swatches panel, both on the desktop and iOS really need a complete rewrite, it feels like it barely works and it's all held by strings. One feature that would be awesome on top of proper support for global colours on the iPad, is "automagic" convert to global, like Illustrator does. On AI you can select the artwork and choose to add all colours found in the shapes as global swatches. This lists all colours used, converts them to global, and reapply them to the shapes, all in one step.
  11. Yeah, but this is a major flaw. If you don't know what option to turn off, this renders all Affinity apps unusable on Windows machines using pen inputs. I'd say it's pretty serious and requires top priority and constant reminder it's not fixed.
  12. I have this happening to me as well. Very frequent crashes, about once every 10 to 15 minutes. There does not seem to be a specific trigger or cause, seems random. The best I can say is that it seems to happen more frequently when pinching to zoom, or undoing. But that might just be because that's my most frequent actions? This is an iPad Pro 9.7" (2016) with iPadOS 13.3 (13.4 was released today, maybe that will help, but I doubt). On another topic I've seen that Photo was stability issues on devices with 3 GB of RAM, this iPad Pro has 2 GB of RAM. That might be the cause. Devs/QA let me know if there's any other info you need. Thanks!
  13. Steps to reproduce: Create a certain number of objects, for example 5 squares Use the Move tool to drag select, without pressing the Shift key, all the squares While pressing the Shift key, use the Move tool to drag de-select the top 3 objects for example The expected result was a selection with 2 objects, instead everything is deselected. I'm seeing the same behaviour in Photo and Publisher too. Thanks! recordedVideo.mp4
  • 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.