Jump to content

Search the Community

Showing results for tags 'bool'.



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 4 results

  1. Hi, I'm wondering if it's possible to mask a stroke in Affinity Designer and keeping it open? As you can see in the image attached, I'm creating a compound object (Stroke + Sphere Shape). Unfortunately the stroke always gets closed after creating the compound object. What I'd like to do instead is to split the stroke in 2 with a sphere mask. This should be done in a non destructive way so that I can adjust the sphere mask later on. Is this possible? Thanks and best regards, Daniel
  2. Hi, with the current version of Affinity Designer for OS X (from the Apple Store) I encounter some strange problems with Compound (Live Booleans). For some reason simple things like the "Add" method produce strangely broken results, also moving compound elements around in the hope the problematic merge resolves makes Affinity Designer looks up on a regular base (starts busy looping and doesn't seem to return back to normal). Interestingly the very same shapes can be merged w/o problems with the normal boolean operation. I attached a test case which triggers the problem for me. If required, I can also provide a process "Sample" generated with Activity Monitor during such look up situation. Affinity Designer: 1.6.0 (latest) Mac OS X: 10.10.5 (Yosemite) Hardware: Mac mini (late 2014) with Intel Iris TestFileBug,1.afdesign
  3. Hi! I couldn't find any thread related to this issue, so I assumed the bug is not reported yet. While preparing the file, I noticed more odd behavior, so I'm reporting 1 potential + 1 bug in this thread. Still, I would have sworn that my eye caught some mention of some issue pertaining to lines and boolean operations, but couldn't find it anyplace... Sorry for the duplicate if there is one indeed. The test setup: I wanted to fill a small area with black ink, so I drew dense jittery brush curves with my stylus. The stroke width parameter was rather thick. Then I made a copy of these curves, and made a compound object out of them. The compound object came out strange-looking. 1st (potential) bug Description: In Affinity Designer, when creating a compound object of a few brush curves that have a stroke width >0, the result of the operation is not as expected For me the expected was the unaltered appearance. Or in other words the appearance of the compound object if I had expanded the strokes first. (see 1st line in the image) 2nd bug Description: If I scale down the non-destructive compound objects by dragging the circular handles, the screen doesn't refresh until you release dragging. Scaling down a (destructive) compound object, works properly hope this helps! -Fotis 2 .afdesign files attached: compound_strokes_issue_fileB.afdesign is the one described above compound_strokes_issue02.afdesign is another example I made compound_strokes_issue02.afdesign compound_strokes_issue_fileB.afdesign
  4. Hello folks, I've been using Affinity mostly to my utmost satisfaction. Putting it through its paces more in the coming days. Here is a bug? that I encountered working with boolean tools, which in this case was the 'intersect' boolean: Have a look at the picture and look for yourself. As you can see the results are inaccurate. (In number 3. I've put the original circle behind the resulting shape and you can see that the curvature is not accurate.) Now...that could be a tolerance or accuracy setting that I'm missing or...it is in fact a bug of some sort. Let me know what you think! Cheers, madeinxyz
×