Jump to content

fde101

Members
  • Content count

    2,313
  • Joined

  • Last visited


Reputation Activity

  1. Like
    fde101 got a reaction from garrettm30 in Scripting   
    In this case it simply won't be possible for some people to meet their requirements.
     
    I've never seen ANY evidence supporting this common theory.
     
    No scripting solution that can integrate multiple applications across an environment can be at this point due to security restrictions within the OS.
     
    To fully meet the requirements of production workflows on both platforms, this will almost certainly be necessary.
     
    Yes, it is.
     
    Unfortunately not possible to do in isolation.
     
    As I explained previously in the thread, there are two major use cases here with different and currently conflicting requirements:
    The ability to script within the application.  This can be done with a cross-platform scripting language which could be selected by the Affinity team and integrated into the product; I proposed Lua due to the fact that it is engineered for this purpose and is likely to have the fewest security hazards and be the easiest code base for the Serif team to maintain - others seem to prefer ECMAScript (JavaScript) which has interesting semantics in a few places (but the syntax stinks) while others clearly prefer that snake thing for some incomprehensible reason.  Using a common language across platforms for this has the benefit of allowing scripts to be written once and shared by users on multiple platforms. The ability to combine multiple applications.  This cannot be done with a language integrated into the product and must use a solution provided by the host operating system.  In this case, to support the needs of users integrating applications within their workflows, there is no choice.  For the Mac, it must be OSA (AppleScript); for Windoze, it must be WSA (VBscript I think?)  
    Note that much of the work required to provide this support, if carefully designed, can be done in such a way that all of the requirements could use a common base within the application code, minimizing the amount of effort to support multiple scripting languages (and a plugin interface).
    If a system is set up internally which exposes a "document model" that is common to plugins and to the various scripting languages, then the general scripting support could be implemented internally once, and the various languages and the plugin interface could hook into that common model.  In this way, most of the "application" side of the scripting interface could be coded and maintained separately from the specifics of the individual scripting languages (OSA, WSA, Lua/Perl/Snake/CrypticThingUsedOnTheWeb/etc.) and from the native plugin interface.
    Then people who wanted to use the internal scripting language could do so, those building workflows across applications could use OSA/Applescript on the Mac or WSA on Windoze, and native plugin writers could hook off of the same document model.  As the applications expand and add new capabilities, Serif would only need to update the document model once and plugins and the scripting languages would all fall in line.
  2. Like
    fde101 got a reaction from TimBoh in Printing Color Managment   
    Make sure the color profile set for the document is correct (in Document Setup -> Color).  That would be my first guess.
  3. Like
    fde101 got a reaction from Copper Star Media in Publisher Calendar wizard   
    You would only need one file.  Use section manager, create a section for each month, and restart page numbering each time.
     
    See also this thread: 
     
     
  4. Like
    fde101 got a reaction from myclay in importing a 32bit TGA and exporting it results in loss of color where alpha is 0   
    I don't believe this is related to the export format.
    Affinity Photo does this internally without even exporting - I made a video to demonstrate this which is on another thread:
     
  5. Like
    fde101 got a reaction from SrPx in TARGA file please?   
    Actually, the brush is a bad example - shapes are more telling.
     
    Here I created three rectangles filled with one shade of blue, and three with a sort of greenish shade that still has some blue in it.  I gave all of them white strokes so that the strokes would stand out when looking at all of the channels.

    opacityZero.mov   Note that in the end, looking at the blue channel only, the rectangles with 100% opacity and the ones with 1% opacity look exactly the same, but the ones with 0% opacity disappear (except for the white strokes).  You can see from this that the channel in general is not pre-multiplied - it is not reflecting the 1% vs. 100% opacity - but there is something about the implementation that is causing the 0% opacity to drop off.  You can also see that the two different colors are reflected as different shades in the channel, so it is not showing the channel as a black/white mask or similar: it is reflecting the actual channel values.
    This is NOT a PNG vs. TGA issue - it is something in the implementation of the alpha channel within Affinity Photo itself.
  6. Thanks
    fde101 reacted to Patrick Connor in TARGA file please?   
    @fde101
    This thread is not the best (only) place for these comments. How about making a bugs post or adding to @myclays bug post 
  7. Like
    fde101 got a reaction from SrPx in Future support for Corel Draw files?   
    It is only subscription on the app store - if you purchase off their web site there is a perpetual license available: https://www.coreldraw.com/en/pages/ppc/coreldraw/mac
    I wish Apple would go back to forbidding subscriptions on the app store; they are resulting in lots of issues like this.  Right now CorelDraw on the app store has a two star rating out of 60 ratings and most of it (if you read the comments) is from might-have-been-users complaining about the subscription model.
  8. Like
    fde101 reacted to Patrick Connor in Affinity Photo Customer Beta (1.7.2.153 - GM) [BETA CLOSED]   
    Only betas built and released after the MAS release will activate. All earlier betas stop running when a new MAS release comes out, (unless you have the Affinity Store releases in which case old and new betas both function)
  9. Thanks
    fde101 reacted to Frank Jonen in Affinity Video Editor?   
    So you can scale it without rendering quality issues. A motion graphics tool can use temporal anti-aliasing more efficiently when it can use paths to generate its own pixels the way it likes to process them. In Nuke for example you can get super sharp logos if you create a font with the base shapes and colour them in-app once compiled to match. In general, rastering to need vs pixel remapping is very different when it comes to render. Also most motion graphics apps will let you manipulate the vector shapes once imported.
  10. Like
    fde101 got a reaction from pauldub in Can you fit frame to text in a text frame?   
    From what I can tell, it fits the width such that the text stretches to fill the height of the text box.
    Double-clicking on the middle handle along the bottom of the text box fits to the current height of the text, so if you double-click that one first, then the one on the side, it gives a somewhat useful fit to the text.
    The status bar also shows the "double-click to reset" text for the non-scaling handles in the corners of the text box, but as far as I can tell that doesn't do anything.
  11. Like
    fde101 reacted to Bugbob in Digital Asset Management (DAM)   
    I only posted it because a tech from Affinity asked me to do so.
  12. Like
    fde101 got a reaction from walt.farrell in CR3 Support or Refund   
    It looks like there may be some patents involved with the compression this format uses?
    https://github.com/lclevy/canon_cr3
    https://www.fredmiranda.com/forum/topic/1586395/1
     
    Nevertheless, it looks like libraw intends to support CR3 sometime in the fall: https://community.skylum.com/hc/en-us/community/posts/360048005532-v3-1-2-again-still-no-CR3-support-
  13. Like
    fde101 reacted to walt.farrell in Create new Layer from selected layers   
    Yes, they're different, but the only substantive difference that MEB discussed in that thread is that you need an extra click the first time you want to select something that's in the group. That seems like a very minor difference, to me.
    You're right that New Layer adds the layer at the top of the stack. If you suddenly decide that you'd like some objects in the middle of the stack to be in a new layer, that's inconvenient. On the other hand, if you organize as you go along, when the objects are still at the top of the stack, it's easy. Or if you're organized enough to create the Layer before you create the objects, it's also trivial. Create the Layer layer, and any objects you then create are immediately created in that Layer. When you are done creating objects for that Layer, do another Add Layer, and create the next set of objects. Etc.
    Nonetheless, yes, it would be convenient to be able to create the Layer at a later time, in the same way one can create a Group, especially for those times when one wasn't organized enough from the beginning
  14. Thanks
    fde101 reacted to ashf in Suggestions for Japanese UI   
    It's still valuable since most Japanese don't speak English.
    Vertical text is essential in publishing/printing industry for sure, but in certain industries such as web, photography or painting, they can go without vertical text in many case.
    Unless Affinity become well known, people won't be interested in it and domination by Adobe will continue.
    So we have to gain users in industries where vertical text is less important first.
  15. Thanks
    fde101 reacted to GabrielM in History and Recovery issues   
    That option "stays" with the document. Let me explain it
    You create a new document You tick save history with Document You save the file Close When you re-open the file, Save history will be enabled by default- This flag is automatically set by the document you open. (Ticked or unticked depending on how the file was saved) If you then untick the "Save history with Document" and Save, you will lose all the history, and not just the most recent changes.
  16. Like
    fde101 got a reaction from Alfred in Allow objects to snap to their “ghost”, initial position during drag operations   
    I can't believe I am jumping into this discussion on this forum; as @MEB pointed out this really is NOT the place for this, but here goes...
    In the Spanish language, all nouns are either male or female - there are NO gender-neutral nouns.  The rule is that when the gender is unknown or mixed (like a group of both men and women), the nouns always default to the male version of the noun.  That is considered part of the usage of the language, and is not in any way a slight toward women - it is simply the way the language works.  Gender neutrality is a practical impossibility in some languages.
    In the English language, we have a mixture of both gender-neutral and gender-specific nouns and pronouns.  Historically it has generally been the case that we would often treat the gender-specific ones much as in Spanish - if there was a mixed group or unknown gender, we would default to the male noun or pronoun to refer to the group.  Once in a while we might use the female pronoun to refer to someone of unknown gender, though this historically would have been more rare.
    For many of us, we still "default" to a gender when unknown.  This is not an attempt to slight either gender, it is not sexist, it is simply a function of the way our language works - still works - as many of us still use the language in a more traditional way and are not concerned about the "political correctness" garbage that is bogging down the supposedly "modern" generation.  If someone is overly sensitive to this, they need to grow up.
     
    Again, this is NOT the place for this discussion, so I will drop off the topic at this point, but this whole thing didn't even exist until @robinp turned it into something it otherwise would not have been; that this is somehow even a discussion is ridiculous and someone needed to say as much.
     
    Can a moderator split these posts into a separate thread so as to de-pollute this one and get it back on topic?  I for one would rather not need to wade through all of this while trying to look at the much more useful feature request and related discussion, and I'm sure the developers would probably just as soon keep this on topic given that they were already having trouble plowing through the on-topic posts because of how much information they had accumulated...
  17. Like
    fde101 reacted to MEB in Allow objects to snap to their “ghost”, initial position during drag operations   
    Hi robinp,
    Again, this is not the proper place to do so. These forums are the first line of support for Affinity users/customers - they were created specifically to help users/customers deal with issues/bugs, listen/receive feedback and generally speaking tracking/following any problems that may arise related with Affinity apps - that's what they expect when they come here. As you certainly understand - being one of the customers who has brought up a few issues recently - we can only do this efficiently if we can (easily) keep track of the issues/points being made.
     If you do need to make your voice heard regarding any disagreement/differing point of view with another user please do so/address the issue privately through PM's.
    No one disagrees that there's a long way to go/various subjects that should be discussed/talked publicly but turning any forum - particularly those already focused on solving/dealing with a specific set of issues/problems - into public discussion will not help anyone and if anything will just get your message and the original forum purpose lost across the stream of unrelated/mixed posts.
    Splitting posts on a long thread like this not only requires quite a considerable time from the staff (which could be better spent elsewhere on support), it's also difficult when in the same post users mix both related and unrelated subjects in their replies. We also do not have a general section where to place the split posts since (and again) that's not the purpose of this forum (I will pass the feedback regarding an eventual general discussion section).
    We would be grateful if we all could go back/discuss the topic at hand again. Thank you.
  18. Like
    fde101 got a reaction from Alfred in Allow objects to snap to their “ghost”, initial position during drag operations   
    I can't believe I am jumping into this discussion on this forum; as @MEB pointed out this really is NOT the place for this, but here goes...
    In the Spanish language, all nouns are either male or female - there are NO gender-neutral nouns.  The rule is that when the gender is unknown or mixed (like a group of both men and women), the nouns always default to the male version of the noun.  That is considered part of the usage of the language, and is not in any way a slight toward women - it is simply the way the language works.  Gender neutrality is a practical impossibility in some languages.
    In the English language, we have a mixture of both gender-neutral and gender-specific nouns and pronouns.  Historically it has generally been the case that we would often treat the gender-specific ones much as in Spanish - if there was a mixed group or unknown gender, we would default to the male noun or pronoun to refer to the group.  Once in a while we might use the female pronoun to refer to someone of unknown gender, though this historically would have been more rare.
    For many of us, we still "default" to a gender when unknown.  This is not an attempt to slight either gender, it is not sexist, it is simply a function of the way our language works - still works - as many of us still use the language in a more traditional way and are not concerned about the "political correctness" garbage that is bogging down the supposedly "modern" generation.  If someone is overly sensitive to this, they need to grow up.
     
    Again, this is NOT the place for this discussion, so I will drop off the topic at this point, but this whole thing didn't even exist until @robinp turned it into something it otherwise would not have been; that this is somehow even a discussion is ridiculous and someone needed to say as much.
     
    Can a moderator split these posts into a separate thread so as to de-pollute this one and get it back on topic?  I for one would rather not need to wade through all of this while trying to look at the much more useful feature request and related discussion, and I'm sure the developers would probably just as soon keep this on topic given that they were already having trouble plowing through the on-topic posts because of how much information they had accumulated...
  19. Like
    fde101 reacted to JGD in Allow objects to snap to their “ghost”, initial position during drag operations   
    Yeah, you are, for the most part, correct. In any case and by the way, I'm probably the worst offender when it comes to all things off-topic. 
    Still, don't you reckon that if the user count booms it may one day become necessary (even if you personally don't use it, which is just fine anyway)? Just a thought.
  20. Like
    fde101 reacted to ChristiduToit in Feature Requests/Suggestions!   
    @fde101
    Good news!

    I've managed to reach out to the people over at Coolorus again, and they mentioned that they plan to make an improved/updated and compatible version of the old Coolorus Mac native colour picker that would then be 100% usable within Affinity apps, albeit slightly less feature rich then their Photoshop CC (Coolorus 2.5) version. 
    Unfortunately there's no set release date, but they mentioned that they've had multiple requests for an Affinity compatible version of Coolorus and will be working on it. 
  21. Like
    fde101 reacted to robinp in Allow objects to snap to their “ghost”, initial position during drag operations   
    Interesting. I've just had a look and this is the entry @JGD refers to I think.

    I'd say that was pretty explicit to be honest.
  22. Like
    fde101 reacted to JGD in Allow objects to snap to their “ghost”, initial position during drag operations   
    Even when Apple is explicit, they sometimes leave some stuff omitted (and I can't seem to find anything on Command+dragging), but the best practice is to keep it as consistent with the pre-installed apps (and not necessarily all the first-party ones – do you guys remember the dark days of “brushed metal”? And what about GarageBand and its wooden trim? –, but mostly those, too) as humanly possible.
    As for the other modifiers and the Pen Tool, I haven't tested them enough for that to be able to express a final opinion on that. But I will stress that Command+dragging should not result in duplication, ever. If it even nullifies it in, of all apps, the Finder, it stands to reason that it should never, ever do the opposite. No matter what ergonomics tell you. In my 16+ years of experience as a Mac user, I can assure you that's just not how 99% of macOS apps are developed, period.
    @Ben, this shouldn't be a case of accommodating users who “can't cope” with a non-standard behaviour (there's so much troubling stuff to unpack in that statement that I don't know where to begin), but instead fixing something that was patently wrong in the first place. If you wish to make things simpler and have two modes in Affinity apps, “Standard” and “Optimised for Ergonomics”, so be it, but at least respect conventions in some way and give users, pun unintended, some options on the matter.
    Look, I've studied ergonomics. I know that if I'm not careful enough I may get RSI and CPS (if I don't suffer from them already; I'm 34 and have been working and playing with PCs since I was 7, after all…), so you're preaching to the choir, here. But the default behaviour should always be to have shortcuts (all of them, as in both key combos and mouse+modifier combos) be as consistent with the host OS and apps as possible.
    And if someone is such a power user that having to move one of their fingers an extra inch might cause them RSI or slow them down considerably, add it as an alternative preference for them, then. Or if you're so afraid that users will injure themselves with (or be pissed about) that new default, keep this current weird behaviour as it is and add the other one for “lite” users (which, as it has been so eloquently stated here more than once, may eventually become your biggest user group) who may enjoy a bigger level of consistency across their OS.
    Those are the ones who will, after all, be using other first- and third-party apps for longer and who'll have to face the worst muscle memory conflicts when firing up Affinity apps (if you're a power user, you may deal with those conflicts more frequently and, bothersome as they may be, you eventually get used to them, just as I did when I had to deal with that “UX turd” of an app that was QuarkXPress; “lite” users, on the other hand, will just get frustrated all the time).
  23. Like
    fde101 reacted to JGD in Allow objects to snap to their “ghost”, initial position during drag operations   
    Well… On the other hand, many Corel users are running oooooold versions. They just keep on going. And legally so, because, you know, perpetual licenses.
    Offering them something new and fresh, that respects some of their favourite app's conventions (at least when it comes to object selection, which is a biggie) and optimizes the UI/UX greatly, might be an interesting value proposition.
  24. Like
    fde101 got a reaction from TEcHNOpls in Size optimized file format/extension   
    In the interim, try periodically doing a "Save As" to save a new copy of the file, to see if it is smaller.  Due to the nature of how the Affinity file format is handled, that can sometimes result in a smaller file.
     
    You might also consider leveraging filesystem-level compression:
    Mac - https://developercoach.com/file-system-compression-in-hfs-space-savings-and-performance-gain/
    Windoze - https://www.howtogeek.com/133264/how-to-use-ntfs-compression-and-when-you-might-want-to/
  25. Like
    fde101 reacted to Pšenda in Perspective ability   
    Perspective Tool and Mesh Warp Tool is in Affinity Photo (bitmaps/picture editor).
×