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

SaucyWeeTart

Members
  • Posts

    69
  • Joined

  • Last visited

Posts posted by SaucyWeeTart

  1. I get a couple jobs a year where I need to rent ID and I do so for a month at a time for those jobs. All the other ID work I do I use CS6 and older.

     

    Not to derail the thread but when you dip in and out of the CC, how do you work it? I was thinking about doing the same thing, but Adobe seem very unwelcoming in relation to single programs subscriptions for a short period. As in, a ID subscription for a month without a yearly contract would be about £30. Not sure I could stomach that.

  2. So it is possible the developers are feeling the pressure of those ever increasing expectations, worried that a beta that does not include most of those features, even in imperfect beta form, would be a such a disappointment that few people would be interested in beta testing it. Adding those features to the beta "to do" list increases the delay & around & around we go.

     

    I would certainly hope that they're not feeling too much pressure. The programs they have developed so far, and in that short a time, are bloody brilliant. I'm always a bit hesitant when posting in the 'Feature Requests' forums because I fear of exactly this.

  3. Just to add my 2p to the conversation, that would be a great thing to be able to do.

     

    I must say that you guys really helped me with a smooth transition from Adobe Illustrator to Designer because of the seamless import abilities of your software for .ai files. I know of a good few people in our office (who are predominantly Sketch users) who would probably give Designer a bash if they could open all their previous work with ease.

     

    I know that the route from Illustrator > Designer is a bit different than Sketch > Designer, but it may be something worth considering.

  4. Yea it does indeed stop working, that's sort of my point. The problem is it stops working in the most maddening way possible. And I know an easy solution is to just go to the 'Get info' menu and change the default program list, but it's always better to fix a problem from the source, which is in Serif's hands surely?

     

    Is it a way of limiting access to those that don't own the MAS version? Is it for another reason? I don't get it.

     

    Basically what I'm asking is if I accidentally open a file with the outdated beta, why do I get sent on a round trip via the app store? I own the MAS version, I own it. Please stop asking me to buy it again.

  5. Hey guys,

     

    I posted about this before a while ago but I feel the need to post again because it's very irritating and I really think it should be given some attention from the dev team.

     

    The issue is the kind of buggy relationship between the MAS/beta versions of your app. As you guys already know, during a beta cycle one might open loads of .afdesign files with it and therefore move the beta into the 'default app' list in OSX. The problem is that after the beta cycle ends and you update the MAS version, all your .afdesign files are still tied to the beta, which with a double click, sends you on a magical journey like this:

     

    > splash screen with an error message

    > click 'ok'

    > new tab opens in your browser to app store

    > app store then opens up on OSX

    > close window

    > close tab

    > another splash screen with 'failed to open file'

    > click ok

    > beta splash screen then freezes on screen until you right click and manually close it

     

    What's the problem with still being able to use the beta even if it's a version behind the MAS? There must be another way to indicate that you've opened your file up in an outdated beta, other than the process above.

     

    When I was using the Adobe Muse/Muse beta apps they functioned just fine because it was up to you where you opened your files. If you opened them in an outdated beta, fine.

     

    Unless I'm still totally missing the point, I still consider this a problem. And a problem that makes me want to systematically end everyone in the office.

     

    Thanks for reading that wall,

    Stu W.

    post-44337-0-14647900-1493976367_thumb.png

  6. Hi guys,

     

    I was just wrestling about with a Lightroom catalogue there and it raised a question about your upcoming DAM software. How easy will it be to transfer over from LR to Affinity? Will it even be possible to swipe data from lightroom catalogs in the first place?

     

    The reason I ask, aside from the obvious, is that my current process with Lightroom is to save every project in it's own catalog and open each one only when needed. It's a bit fiddly, but does work. I'm therefore wondering if I should be preparing my files for some sort of mass transfer in the future, because it might take me some time.

     

    I understand that this is information you might not want to give away at this stage, but thought I'd ask anyway.

     

    Thanks.

  7. Hi guys,

     

    Having a little trouble with bleeds at the moment. I'm already aware that if you specify bleeds in the document settings you can enable bleed marks on the export. I also know that live previews don't exist yet so I'm trying to hack together a kind of pseudo-preview workflow.

     

    As you can see from the video, it's a bit of a buggy, long-winded affair. This SURELY can't be the best way to do it.

     

    Anyone else got any ideas on how to do it better?

     

    Thanks!

    BleedIssues.mov

  8. As the developers have mentioned many times, the biggest obstacle to that is the number of plugins that rely on features not (yet) implemented or have no direct counterpart in either Affinity product, like Photoshop actions. So it isn't just about supporting more plug-ins, it is about supporting everything those plug-ins need to function.

     

    Do you have any links to some appropriate threads discussing it in more detail? I'm not a programmer/developer so I have a tendancy to suggest things that might not be technically feasable.

  9. We don't have any current plans to add plugin support into Affinity Designer, however this may change in the future. Hopefully as Affinity development continues and it becomes more popular, plugin makers will want to make their plugins compatible with Affinity Photo and work with our developers to achieve this.

     

    Would it not make more sense to offer plugin support earlier rather than later? That way, the community itself will help you proactively build and popularize your products - hopefully leading to a snowball effect. I see it as a potentially very powerful growth mechanism.

     

    I'm sure you guys have thought about it but I'm curious what your thoughts are.

  10. Unfortunately, it was previous said that animation will not come to either Affinity Photo or Designer. The reason is because it would compact too many unrelated features in one, and it would create an overwhelming user experience. With a few exceptions, Affinity wants to carry only the features that relate to the program so the experience is more clear.

    Totally agree with this. Photoshop may still be ubiquitous right now but it's a confusing, hot mess of a program. Its quite clear that Adobe have absolutely no idea what to do with it.

     

    When you try and cater for everyone, eventually you'll end up catering to no one.

×
×
  • 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.