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

fde101

Members
  • Posts

    4,990
  • Joined

  • Last visited

Posts posted by fde101

  1. Hi @ToniB, do you have any suggestions on how to make this more intuitive without making it less efficient or wasting screen space?

    Many projects wind up with a large number of layers so expanding the UI to display things more clearly would likely use up more screen space which would make laptop users upset.  Anything that required extra steps would make the process less efficient which would slow things down; as this is a professional-level application meant primarily for power users, efficiency of operation generally takes priority over obviousness for those first learning to use it.

    If you can come up with ideas for improving the discoverability of the behavior or making it more approachable without compromising the efficiency or compactness of the current solution, your request is much more likely to gain some traction.

    Personally the only thing I can think of at the moment would be to add some kind of indicator to the mouse pointer which depicts what is about to happen depending on where you are pointing as you drag the layer, and maybe highlight the drop zones somehow as well while doing so?

  2. On 11/22/2019 at 3:54 AM, big smile said:

    It would be also super handy if the layers panel had an option to only show layers on the currently active page of a spread, as sometimes the layers panel can get very chaotic to navigate when it shows all the layers on both pages of a spread. 

    Here you run into a complication when dealing with parent/child relationships.  If you have a group containing layers on both pages, do you show the entire group in the layers panel, show the group but only the children on that one page (which might make it appear that the group is smaller than it is, causing both pages to lose content if you delete the group after only having seen objects from one page within it...), hide the group (since it contains content from the other page), ...

     

    Also, what are you going to do with layers that are outside the spread and not on either page?

     

    This is not the simple request you seem to think it is when you start digging into the details of what is being requested.  I agree in principle that having filtering options for the layers panel would be quite nice, but this request as specified could lead to dangerous forms of confusion if not implemented very carefully.

  3. Hi @florianr, welcome to the forums!

    The shortcuts assigned to these by default are command+backtick and command+shift+backtick, but you can customize them under Preferences -> Keyboard Shortcuts.

    The options are listed under the Miscellaneous category and are labeled "Switch to Next View" and "Switch to Previous View".

     

    Note that the command+shift+bracket shortcuts are used for Arrange options by default, so you will also need to change those to avoid a conflict if you want this behavior.  Given that command+bracket shortcuts are used for the other Arrange options, this is probably why the shifted versions were used there and not for tab switching.  The Arrange options can be found under the Layer category.

  4. 2 hours ago, JGD said:

    I accept your remark regarding the first feature request (which I will still defend on the grounds that, as per my stated MO, I'm trying to get as many team managers to realise just how serious the document model shortcomings are, but I respect your position so I will leave it at that), but not at all the one regarding variable fonts.

    I think you are missing the point.  The main problem is not that you are making a feature request, the problem is where you are making the request.  It does not belong in this thread.

  5. 28 minutes ago, Old Bruce said:

    I have one bit of software which will travel with me should I choose to change platforms but it cost much much more than all three Affinity applications

    I have quite a few more than that, but granted that most of those did indeed have higher price tags than the Affinity apps.

    Examples:

    • DxO PhotoLab
    • On1 Photo RAW
    • DaVinci Resolve, Fusion Studio
    • Ableton Live
    • Cubase
  6. For those who are using non-Mac systems, this is what I get with a "normal" Mac program when I click on the title (in recent versions of MacOS):

    image.png.c060517354adb495070b9ab38c898f88.png

     

    From there, I can rename the document, add tags to it, move it (using "Where:"), or lock it to prevent changes.

     

     

    This is what I get when I command+click on the title (and this has been around for a long time):

    image.png.5e33d879afdab540d8e437eeb48af4c3.png

     

    Selecting a folder from that menu navigates to that folder in the Finder.

  7. This may be nice to have, but it should be an independent checkbox during the import process, not something tied to an existing preference.  I could see this causing problems for some technical documents, such as syntax-highlighted programming source code in which typographic quotes could make the text invalid.

  8. 8 hours ago, craigleeus said:

    How hard can it be? 

    Consider that plugins are an unknown quantity when it comes to performance and to availability.

    If a plugin is used as a live filter and the document is then opened on a computer where the plugin is not installed, it will not be possible to render any changes to the document that would be impacted by the algorithm in the plugin.

    If the plugin is available, but is very slow and takes a long time to render, then every small change in the document could lead to unusable levels of performance.

    Node-based compositing software used in video production is generally designed with this in mind, but the nature of how the Affinity products work might make supporting arbitrary plugins as live filters impractical unless they could be sufficiently isolated from the main application to deal with plugin crashes, lags in rendering performance, etc.

    This may not be insurmountable, but it may not be as simple as you think either, particularly with so many filters not working well if at all on the software.

    Personally I would rather they got them working with greater consistency and stability first, then add in the bells and whistles like this.

  9. 47 minutes ago, StevenS said:

    I couldn’t figure out how to change the rulers from pixels to mm.

    https://affinity.help/designer/en-US.lproj/index.html?page=pages/DesignAids/rulers.html?title=Rulers

     

    48 minutes ago, StevenS said:

    I can’t see anywhere under “Preferences” that I can set up an overflow disk; with my files being quite large and plug ins being used, it would be preferable to manage distribution of data across the various disk drives on bigger systems like mine where there are choices.

    I believe the Affinity products use the document file itself for scratch storage, but that is based on a limited understanding and guesswork centered around comments I have seen tossed around the forum (and the fact that they do not respond well to "cloud storage" and network shares while working with the documents).  The applications are all 64-bit, so it is possible they could simply be relying on the virtual memory provided by the OS as well.  In any case, there is no equivalent to this option in the Affinity products.

     

    51 minutes ago, StevenS said:

    Program should offer alternative formats of original document format is not available.

    Agreed.

  10. This is the result of there not being enough modifier keys available under Windoze to map these functions to, and the use of mouse chording was selected as a means by which to work around that.  On the Mac there are sufficient modifier keys that this is not a problem, and a key is indeed mapped to this function.

    One way Serif might be able to work around this limitation of the other platform would be to treat left and right shift keys as two different modifiers, for example, but depending on the workflow of an individual user that might be more disruptive than the choice to use chording, so it would obviously need to be configurable somehow, and so far they have not provided an interface for remapping the modifier keys in any way.

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