Jump to content

PixelPoetix

Members
  • Content Count

    6
  • Joined

  • Last visited

About PixelPoetix

  • Rank
    Newbie

Profile Information

  • Gender
    Male
  • Location
    California
  1. Hello Serif Friends... There's a certain behavior within Publisher that I find particularly annoying: when I hide a layer or layer group that has Text Wrap enabled for itself or for any nested layer within it, those text wrapping settings continue to affect visible text layers. I haven't been sure whether this was intended behavior or a bug and finally did a search here in the forums and discovered that it is indeed the intended behavior apparently to accommodate those who are used to the same behavior within InDesign. While I get that reasoning and I can certainly see the merit in having this behavior enabled for certain use cases, I would also LOVE the option to disable this behavior when it makes more sense for my workflow (which for me, at least, would be most of the time). To be clear, I am well aware of the option to "Ignore Text Wraps" for a visible text frame but this is NOT a suitable workaround since that visible text layer may still need to wrap around other visible layers. So currently, the only workaround is to disable text wrap for any hidden layers that I don't want affecting visible text while I work on those visible layers. But then, if I want to compare the look of one layer group to another, for example, I can't just hide one group and make the other one visible. Instead, I have to disable text wrap for each individual layer that has it in the currently visible group, hide the group, show the hidden group and then go through and re-enable text wrap for each individual layer that uses it for that now visible group. This makes comparing two overlapping layer groups a tedious experience. If I had the option of toggling a setting that prevents hidden layers with text wrap enabled from affecting visible text layers, I could then simply hide and show each layer group to compare them. Alternatively, perhaps you would consider a hybrid solution whereby individually un-checked layers with text wrap enabled continue to behave in the way the devs intended. But if they are contained in a layer group, then that group's checked or un-checked state would determine whether its child layers still affect visible text layers. I will illustrate with some example scenarios. In each of the following scenarios, all object layers have text wrap enabled. SCENARIO 1: ✓ PARENT GROUP 1 ✓ TEXT FRAME 1 ✓ OBJECT 1A ☐ OBJECT 2A ☐ OBJECT 2B Proposed Result: TEXT FRAME 1 wraps around OBJECT 1A, OBJECT 2A and OBJECT 2B. SCENARIO 2: ✓ PARENT GROUP 1 ✓ TEXT FRAME 1 ✓ OBJECT 1A ✓ PARENT GROUP 2 ☐ OBJECT 2A ☐ OBJECT 2B Proposed Result: TEXT FRAME 1 wraps around OBJECT 1A, OBJECT 2A and OBJECT 2B. SCENARIO 3: ✓ PARENT GROUP 1 ✓ TEXT FRAME 1 ☐ OBJECT 1A ✓ PARENT GROUP 2 ☐ OBJECT 2A ☐ OBJECT 2B Proposed Result: TEXT FRAME 1 wraps around OBJECT 1A, OBJECT 2A and OBJECT 2B. SCENARIO 4: ✓ PARENT GROUP 1 ✓ TEXT FRAME 1 ✓ OBJECT 1A ☐ PARENT GROUP 2 ☐ OBJECT 2A ☐ OBJECT 2B Proposed Result: TEXT FRAME 1 wraps around OBJECT 1A but NOT around OBJECT 2A nor OBJECT 2B. SCENARIO 5: ✓ PARENT GROUP 1 ✓ TEXT FRAME 1 ✓ OBJECT 1A ☐ OBJECT 1B ☐ PARENT GROUP 2 ✓ OBJECT 2A ✓ OBJECT 2B Proposed Result: TEXT FRAME 1 wraps around OBJECT 1A and OBJECT 1B but NOT around OBJECT 2A nor OBJECT 2B. To me at least, a hybrid solution such as this would be an elegant way to please BOTH those who prefer the current behavior, i.e. those who are expecting a similar experience as they may have had with InDesign, AND those of us for whom this current behavior drives them bonkers...and all without having to choose a side AND even allowing both sides to easily adapt their workflow to make use of the alternative if and when they ever find the need to. I hope all of the above makes sense. If you've made it this far, thanks for taking the time to read through my suggestion! Let me know if I can offer any further clarification. In the meantime, keep up the AMAZING work! I've been LOVING Publisher overall and look forward to even more improvements over time. ~ Chris
  2. Hello... So I've been encountering inconsistent export behavior that doesn't seem to have any rhyme or reason to it and it gets SOO friggin frustrating to never know from one instant to the next how Affinity Designer is going to decide to behave - it's incredibly disruptive to my workflow especially since it seems to change every time. Have seen this for at least a couple releases now. Currently on 1.4.1 as updated from the MAS. What I'm experiencing: When I have an artboard selected within a document with multiple artboards and I go to File > Export..., sometimes the export mechanism will automatically choose for the "Area" dropdown that specific artboard only which is (for me anyway) the expected behavior. But sometimes (and I've not been able to figure out a pattern to it) it pre-selects the "Whole Document". In fact, funny enough, as I was writing this, in order to check the steps I took, it went from choosing the whole document the first time to choosing only the artboard I had selected the second time after saying "cancel". ALSO and MOST FRUSTRATING OF ALL the dimensions in the export popup mechanism can never seem to get it right anymore. Used to work just fine until a couple releases ago. At the moment, for example, I have an artboard selected with dimensions of 708pt x 354pt and DPI of 144, but when I go to export it (doesn't matter what format), the export popup shows 1417px x 708px instead of the expected 1416px x 708px. Worse still, if I change one of those dimensions with the aspect ratio locked, it doesn't get the other dimension right. Using the current example, I just changed the short side to 354px (which should yield a change of the long side to 708px) and AD changed the long side to 448px!!! WTF?!?! I changed the long side to 708px and AD made the short side 559px instead of the expected 354px. I'm attaching screenshots so you don't think I'm losing my mind (even though lately, AD has been making me lose it). Messed up thing is, just like the inconsistency with whether AD chooses the individual artboard or the whole document, there is similar inconsistency with the way it chooses to respect aspect ratio - sometimes it works exactly as expected BUT I never know when that's going to happen and it works correctly much less frequently than it doesn't.
  3. Hello... I have to admit that I've gotten to the point where I am preparing to migrate all my work back to Adobe Illustrator after being a fan of Affinity Designer from the beginning - I purchased it from the MAS, was impressed immediately and quickly adopted it as my daily graphic design tool, replacing Illustrator (even though my company pays for Adobe CC for me). But over the last few months, Affinity Designer is becoming increasingly unusable - so many bugs and I don't have time to log in here and report them all. I'm usually far too swamped with projects and it's bad enough I've had to spend extra time recreating whole projects in Illustrator just to get an output that is a professional enough quality to turn in. I can't tell you how many times I've exported a project from AD and ended up having to apologize for the poor output due to the way AD handles color, PDF exports, fonts, etc etc etc...the list seems to be expanding with each new release. What sucks is that I REALLY want to keep using AD - its user interface works for me so much better than Illustrator and I've become so accustomed to its workflow that I dread having to re-orient myself to the idiosyncrasies of Illustrator. And I REALLY don't want to have to shell out the cash to try something else like Sketch (which seems to have a higher adoption rate industry wide). I've even been using the betas as they're released in the hopes that some of the issues I've been experiencing will be addressed and each time I get hopeful as I download the latest one and infer from the release notes that maybe, just maybe one or two things have been fixed. But alas, there are still some persistent bugs that add time and frustration to my workflow and rather than that number decreasing, it seems to be increasing with each new release bringing a further and further degradation in performance. So, PLEASE can someone give me a reason to stick around? Please tell me there is a light at the end of the tunnel and that what seems to be a downhill slide for AD is only temporary and the dev team is aware and working on bringing it back to the glory and esteem it once held? In the meantime, despite feeling like I don't have the time to do so, I am going to start hammering you with every bug I encounter in the hopes that your team will actually listen and fix them and the time I spend reporting the bugs will be less than the time it would take me to migrate back to Illustrator as my primary graphic design app. Here's to hoping you make me a fan again. Sad and Skeptically Yours, Chris
  4. Thanks, MattP! For what it's worth, my opinion is that allowing it to be used on a pixel layer seems like a no-brainer. There are many tasks that can be accomplished in multiple ways. Why create a support headache by restricting a tool for the sole reason that there are other ways it can be done? You'll just end up with users wondering why it's not working when it seems like it should. I can respect a desire to avoid bloat in an application, but it's not like you'd be adding a new tool. The tool is already there. All you're doing is allowing the user one more choice as to how best to achieve a desired result based on their own personal workflow and preferences. One of the things I enjoy most about Affinity is its flexibility and adaptability. I'm not trying to preach to the choir as it sounds like you and I are on the same page, but hopefully my voice can lend some support to your own when you bring it up again with the team. I hope you manage to convince them!
  5. Yes, Chris_K. That's exactly right. Sorry I didn't specify. It should work on a pixel layer, yes? I was fairly certain I used to be able to use it on a pixel layer, but I'd be willing to admit to being wrong about that. Hi, Matt...thanks for all your hard work! Much appreciated! I downloaded and installed the new beta. Transparency tool no longer results in a crash and does in fact work as expected on a vector layer. However, while it no longer crashes the program, the transparency tool does nothing when attempting to apply it to a pixel layer (assuming the expected behavior is that I should be able to do so - as I said above, I seem to remember that I used to be able to).
  6. Hello... I know that beta builds carry with them the risk of things like this happening, so this isn't a complaint, just an FYI. While using the latest Affinity Designer Beta build (26820) on the latest El Capitan Developer Beta build (15A244d), attempting to use the transparency tool results in a crash of Affinity Designer Beta. Happy to provide more details to help if needed. Thanks for your amazing products and even more amazing and prompt support! Serif rocks! ~ PixelPoetix
×
×
  • 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.