Jump to content


  • Content Count

  • Joined

  • Last visited

About Junon

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. It appears that snapping points to other point axes is not possible. Kind of aggravating, snapping feels a bit lacking and seems to continually get in my way. Here's a recreation of what I'm talking about: https://i.imgur.com/FCSLrZM.mp4 And my snapping settings:
  2. I've had the product a little over a year now and I've got to say I'm getting increasingly annoyed. I remember reporting crashes related to the guide manager around the time I started. A year later, they're still not fixed. I reported a crash related to the asset manager. It's still not fixed. Now, going to the search bar inside the preferences causes a crash. This is unacceptable. I am quickly losing confidence in anything I do in the program. I am tired of being worried that if I click on something, I'm going to cause the whole damn thing to crash. I'm a software engineer, I know how management works - so product/project managers, please hear this: stop forcing your engineers to ship features for once and allow them to fortify the codebase. It's so obviously required and yet it's not being done. It's absurd how unconfident I am in the program I spend a very large portion of my time in. Thanks.
  3. That's a silly children's game. Knowing whether or not they've acknowledged it and/or have it on a roadmap internally would be beneficial for prospective buyers.
  4. Perhaps you guys could comment on some simple stuff that still isn't added - e.g. warp and perspective. It's been a year with no ETA and these are kind of critical pieces of functionality for a vector graphics program.
  5. A year later and still no response from the team. Just an acknowledgement would be nice.
  6. Nope, not enabled. And no, no other apps to assist with keyboard input.
  7. I suppose most of us are in the camp that the features work at a basic level if they're included at all. From a QA perspective, a lot of broken features isn't having a lot of features. They don't equate, and it makes the product look buggy and cheap. So when a major feature such as Constraints just flat out doesn't work, it makes me (personally) feel uneasy pushing for or using Affinity software at all. Corollary: I'd rather the feature be completely removed until it's fixed (as in, working at all) rather than being taunted with it every second and having it clutter up the menus. Further, a lot of users I'd imagine are developers and understand the need for proper bug tickets being submitted in order for things to get fixed. People voicing their concern for a particular issue isn't "you're not moving fast enough", it's more "we want to make sure the team knows this is important to us". The latter is entirely justified. As far as I can tell, nobody is putting down the developers. We're all still here using the product, we're all still happy we paid for it or else we wouldn't take the time to post on the forums and we would have moved to other software. So please don't attack us for posting concerns here - the developers should be happy there's such a demanding audience. It means we want this to be a good product. I'm tired of Adobe's and Corel's stranglehold on the market and I think Affinity has a really good chance at uprooting them. That's why I'm here.
  8. EDIT: nevermind. Forgot things worked differently on retina.
  9. Hi Sean, I think that's close but not entirely correct - it depends on the intended functionality. As it stands, the preview isn't updated for the first layer that you're previewing the filter on (in step 2 of OP). That's to say, layers you're previewing filters on don't have their layer panel component updating, either. I'm not sure if that's intentional or not (either case would make sense IMO) but it's not just the cancelling out that's bugged. The fact the behavior is different between the original layer preview and the duplicated layer preview is what this bug is more specifically identifying. Hope that helps.
  10. Begin previewing a filter (I've been playing with Halftone, start there if others don't work) on a raster layer (that presumably has other layers beneath it) During filter previewing, drop down the blending mode menu and hover over different selections in order to preview the filter with the blending mode The canvas flickers but the blending mode on the canvas doesn't reflect what the mouse is hovering over. However, clicking on the blending mode does force the canvas to reflect the selected mode - it's just the blending mode menu hover that doesn't properly render the preview on the canvas.
  11. Create a layer with raster data (some image or something) Go to Filters -> Color -> Halftone, preview mode starts (haven't tested with other filters but I'd imagine it's the same for all of them) Without applying the filter or closing out of the filter panel, right click on the layer and click Duplicate The duplicated (new) layer's preview (in the Layers panel) shows the filter preview instead of the 'true' image data. Hiding/Showing the layer resets it and forces it to show the actual layer contents. Layer prior to starting filter: Preview of the canvas during filter preview: Duplicated layer preview: Shows the layer preview with incorrect data alongside the canvas (the canvas is correct in this case) - remains so even after closing out (not applying) the filter panel: And finally, after unchecking visibility, the preview is reset.
  12. If by crash report you mean the dump that Apple provides, I have attached one in the OP as a spoiler tag :) It's also worth mentioning that I was going to demonstrate this to a colleague but it appears to be intermittent at times - I couldn't reproduce after letting it 'cool off', so there must be some state-specific condition that causes the bug to occur. I wouldn't begin to have any idea what those conditions are, though.
  13. Hey there - it's a few months short of a year and it appears constraints are still massively bugged, to the point I cannot use them. As @rubs outlines, changing constraints should not affect the existing dimensions, but that's exactly what I'm seeing too. The only things listed above that seem to be fixed are that bad glitches can now be undone (kudos to making pretty much everything you do in AD go straight to the undo stack - it's so much more powerful) and I haven't (personally) seen objects disappear, except for when they go off the artboard (but the bounding boxes are still visible) nevermind, just ran into disappearing elements. Throwing my hat into the ring here, this is incredibly frustrating.
  14. Further, the delete button stays enabled even after deleting the last guide. Clicking it again disables it.
  15. Kind of a weird title, apologies for that. Create a new document (we'll call it document A). Put some shapes or whatever, doesn't really matter. Save it somewhere. Create another new document (called document B). Place document A inside somewhere. Double-click on the embedded document A object to edit it. The embedded document editor appears. Go to File -> Document Setup... and change the dimensions of the embedded document A object (in the screenshot's case, I made it smaller) Apply the settings and close the embedded document object editor; focus returns to document B. See screenshot for bug (both screenshots show document B) It appears editing the document size doesn't invalidate the parent document B's bounding box rendering around the embedded document A, and shows the old box with the controls and the new box with just a solid line (first screenshot). De-selecting and re-selecting the object shows the correct bounding box (second screenshot).
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.