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

wesleyb

Members
  • Posts

    23
  • Joined

  • Last visited

Reputation Activity

  1. Like
    wesleyb reacted to Luca H in Grid gutter decimal places limited to 3   
    Hi @Patrick Connor,
    thanks for the quick reply, you are right, the value is correctly stored. What must have confused me is the rendering of the grid.
    I attached a video to show the grid rendering confusion.
    In the beginning the gutter is set to 0, then I paste the exact location of my object and then the rendering of the grid makes it seem like there is a rounding error, because the lines don't align, but then I discovered if I play around with the decimal place numbers the rendering of the grid is not correct or precise enough.
    Bildschirmaufnahme 2021-05-26 um 12.04.31.mov
  2. Like
    wesleyb got a reaction from Enzi in Suggestion for Minimal Public Access to Issue Tracking   
    Known Situation
    I am aware of the following:
    Serif code is not open-source, so direct public access to an internal issue tracking software is not likely. The forum itself is not suitable for bug tracking. The forum is not used as an issue tracker by Serif. A forum, for non-tecnical bug reports, is understandable, because a user may produce a wall of text, that must be parsed, tested, and converted into a technical bug report.
    Request / Suggestion
    Provide the users access to a pre-filtered view of the issue tracking. I.e. users would be permitted some or all of the the following:
    see list of issues see platform of issue see related milestone see kind of issue (feature, bug, defect) see status of issue (in progress, queued, backlog, pending review) see date of last activity on issue subscribe to activity But, users would not be permitted the following:
    view internal communication about issue comment on bug Benefits
    Managing forum posts, that discuss the same bug, could then be as simple as linking to a single bug report. Answering new forum posts, that ask about the status of an old known bug, could be as simple as linking to a single bug report. Users can be informed clearly of known and unknown bugs, thus reducing requests or losing loyalty due to abandonment. Status update posts, of project milestones, could be made with less effort.
  3. Like
    wesleyb reacted to mackleys in Light Mode UI for iPad   
    I would like the option to have the light ui on my iPad AD. If this is a redundant ask then please close.  I searched and did not find any requests for this—which makes me fear my request puts me in the minority (or my search skills are rusty)
  4. Thanks
    wesleyb reacted to Peregrin in Roughen Tool   
    I've suggested this before and some staff members have said they plan to add this feature, but looking at 1.7's features I thought this would be a good time to bring it up again.  Smooth curves are great most of the time, but when you want something to look hand-drawn, you usually need it to be a bit rough.  I think many illustrators would benefit from a roughening tool; it would allow illustrators to make non-uniform curves more easily than having to draw each node individually.
     

     
    As it is, it's really hard to produce a line that doesn't look uniform, and a roughening tool to add pseudorandom midpoint displacement would make illustrating much less time-consuming.
    Last I heard, the plan was to have a brush-type tool that would allow the roughening effect to be "rubbed over" a curve.  I think that's is a great idea, but even something as simple as Inkscape's Fractalize feature would be sufficient for many illustrators' purposes.
  5. Like
    wesleyb reacted to Ed A in Designer Layers / Artboards and how they work in Publisher   
    Hi all!
    I’ll cut to the chase. I make customisable kid’s books - currently with Adobe Illustrator and InDesign. Right now, the child’s character is an Illustrator file placed at multiple points throughout an InDesign document (the book) and I go through and change layer visibility (annoyingly I have to do this manually on each page) depending on the visual options selected. Finding and replacing text is easy.
    I’ve been trialling Designer and the Publisher beta and am really impressed, but I have a question for those more in the know:
    Is there a quick way to choose which layers in an imported linked file into Publisher are on / off? So far I’ve been clicking to edit the linked file from within Publisher but if, for example, I wanted to switch on a particular hair style and colour layer, I’d have to do this for each artboard, defeating the object of saving time. Throughout the book, the character might change clothes so I’ve used artboards to different but was hoping common layers like skin, hair, eyes etc. could be shared and quickly switched on / off for everything quickly.
    It looks like artboards in Designer are like a traditional group and a Designer file with multiple artboards doesn’t share layers. Is there any way to change this or another way of doing things / thinking about this?
     
    My initial thinking / solution:
    Tweak my Designer file so it has an artboard for all common features needed on each page and other artboards for other layers that only need to be visible on certain pages? This way, I could place a Designer file a few times in the same location in Publisher and have different layers on / off overlaid on each other. Seems a bit of a clunky workaround though.
    Publisher question (sorry, wrong forum but related to this): when you import multiple instances of a Designer file and want to be able to play with its layer visibilities throughout, can you set some layer overrides in some instances of an imported file and not others?
    Thanks so much in advance (and sorry for the long post! Just really like Affinity and want to change over!).
  6. Like
    wesleyb reacted to BEGRAFX in Converting Pixel drawing to Vector?   
    Yes, Illustrator has been around longer, and has had more of a chance to "refine", we understand that. I don't think anyone is expecting Affinity (or any other) to be "as polished" from the start, as a tool that's been out for over a decade. I think we all agree with you completely, that Affinity can do a lot of things, and is a great deal for the price point. But you hit right on a key issue. Many of us ARE Pro Users, making our living with this software as one of the tools in our kit. As others have said, we don't expect it to do everything. No carpenter uses any one tool exclusively. However, many of us have switched to the Affinity Suite from the Adobe Suite, and Affinity Designer has done a great job at replacing Illustrator for us. Vastly better than Inkscape or others out there. But to say we are expecting it to "do everything" is unfair. I don't think any of us expect that. We DO expect a "Brand X" Hammer will drive a nail as well as the "Brand Y" Hammer that it replaces. We've come to see Affinity Designer as a solid replacement for Illustrator, and we've come to see Affinity Photo as a solid replacement for Photoshop, and Affinity Publisher for InDesign. We all realize that things take time, however this thread has been going for 2-3 years now. I think by this point, we are at least hoping to hear from Affinity/Serif, that Vectorizing/Image Trace is something that IS on the drawing board. Are we expecting it to be in the next update? Sure, it'd be nice, but I think we'd all just like to hear, "We've heard you, it is in the works, we hope to have it available in... 6 months, 12 months, whatever. We love Affinity/Serif, we're just looking for some communication from them. 

    Thank you.
  7. Like
    wesleyb got a reaction from hawk in Suggestion for Minimal Public Access to Issue Tracking   
    Known Situation
    I am aware of the following:
    Serif code is not open-source, so direct public access to an internal issue tracking software is not likely. The forum itself is not suitable for bug tracking. The forum is not used as an issue tracker by Serif. A forum, for non-tecnical bug reports, is understandable, because a user may produce a wall of text, that must be parsed, tested, and converted into a technical bug report.
    Request / Suggestion
    Provide the users access to a pre-filtered view of the issue tracking. I.e. users would be permitted some or all of the the following:
    see list of issues see platform of issue see related milestone see kind of issue (feature, bug, defect) see status of issue (in progress, queued, backlog, pending review) see date of last activity on issue subscribe to activity But, users would not be permitted the following:
    view internal communication about issue comment on bug Benefits
    Managing forum posts, that discuss the same bug, could then be as simple as linking to a single bug report. Answering new forum posts, that ask about the status of an old known bug, could be as simple as linking to a single bug report. Users can be informed clearly of known and unknown bugs, thus reducing requests or losing loyalty due to abandonment. Status update posts, of project milestones, could be made with less effort.
  8. Like
    wesleyb got a reaction from mondze in A forum is NOT a bug tracking system!   
    I agree that users, and I add that staff, could benefit from a public issue tracking system; but, there are disadvantages for staff (non-technical wall-of-text bug report spam, exposure of sensitive internal communication). I have reated a feature suggestion post that attempts to solve the disadvantages of both sides, and hopefully will promote constructive discussion.
     
  9. Like
    wesleyb got a reaction from mondze in Suggestion for Minimal Public Access to Issue Tracking   
    Known Situation
    I am aware of the following:
    Serif code is not open-source, so direct public access to an internal issue tracking software is not likely. The forum itself is not suitable for bug tracking. The forum is not used as an issue tracker by Serif. A forum, for non-tecnical bug reports, is understandable, because a user may produce a wall of text, that must be parsed, tested, and converted into a technical bug report.
    Request / Suggestion
    Provide the users access to a pre-filtered view of the issue tracking. I.e. users would be permitted some or all of the the following:
    see list of issues see platform of issue see related milestone see kind of issue (feature, bug, defect) see status of issue (in progress, queued, backlog, pending review) see date of last activity on issue subscribe to activity But, users would not be permitted the following:
    view internal communication about issue comment on bug Benefits
    Managing forum posts, that discuss the same bug, could then be as simple as linking to a single bug report. Answering new forum posts, that ask about the status of an old known bug, could be as simple as linking to a single bug report. Users can be informed clearly of known and unknown bugs, thus reducing requests or losing loyalty due to abandonment. Status update posts, of project milestones, could be made with less effort.
  10. Like
    wesleyb reacted to Aammppaa in [AD] Propagate symbol name when renaming   
    When I rename a symbol in the Symbol panel, the new name does not propagate to instances of the symbol already on the page.
     
    Also, could renaming and deleting be brought inline with other conventions within Designer...
     
    Click the name in the Symbols panel to rename Rename inline rather than a modal box Select in Symbols panel and hit Delete key to delete Thanks for your consideration.
×
×
  • 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.