Jump to content

fde101

Members
  • Content Count

    3,743
  • Joined

  • Last visited

Everything posted by fde101

  1. I have a scroll bar for that... and the scroll wheel works in a "blank" part of the scrollable area. Before jumping through the hoops of resetting everything you might want to check to see if you have "Show Scroll Bars" set to "Always" in the "General" section of "System Preferences" as they do disappear for me if that is set to the other options.
  2. Ok, so here is my take on a menu reorganization for Affinity Photo. I did change my mind about some of those options going into the Window menu... It might not be quite perfect, I may not have gotten the keyboard shortcuts correct, and I am not showing some of the menus/submenus that I am not changing. This is based on the 1.9 betas and is not intended to add or remove items (though some are renamed and many are in different menus). I removed the "..." from a number of items that should not have them (the "..." should only be present when a command requires more information to proceed - "New Astrophotography Stack" for example does not, nor does "About Affinity Photo" whose entire purpose is to display information - no additional information is requested by that command...) There are many ways to do this, so take this as one suggestion, not the only one. Also, I did this as an exercise and possibly to open up discussion - it is not necessarily a feature request in its own right.
  3. I think I would place those in the Window menu. While in "normal" mode they open tabs, the tabs in Photo are in effect a consolidation of what would be separate windows in separated mode, which indeed these do create when in that mode. The panels themselves do not, but their content does. One of the examples given in the HIG is that of an "inspector panel" - such a panel changes its content based on the active selection but is not in and of itself tied to any particular document. The one they picture resembles the Metadata studio panel in Photo, for example. An example of something that does not fall into that category is the new Account window. Serif has chosen to place that in the application menu, which is appropriate according to the HIG, which indicates that menu should be used for options that are not related to any specific document "or window" - though the command itself opens a window I still think that is appropriate in this case (the "About" option is supposed to be there too, and that is explicitly indicated in the HIG as the correct place for it). However, the HIG also indicates that the About item should have a separator after it and should not be grouped with other items - Serif has placed the "My Account" and "Check for Updates" options before the separator after "About" (which also incorrectly has dots after it and is missing the application name - "About..." should be "About Affinity Photo", "Hide" should be "Hide Affinity Photo" and "Quit" should be "Quit Affinity Photo").
  4. HIG spells out that auxiliary windows which display information related to the open document or selection are considered panels (https://developer.apple.com/design/human-interface-guidelines/macos/windows-and-views/panels/) and that open panels should NOT be listed at the bottom of the Window menu (https://developer.apple.com/design/human-interface-guidelines/macos/menus/menu-bar-menus/). I need to partially correct myself on this one: the HIG indicates that you should "consider" including such items in the Window menu, but then indicates specifically that it is not necessary to include the Font or Color panels as those can be accessed from the Format menu (missing from the Affinity products)... so this seems to suggest that the panels should be listed in the Window menu if they don't appear anywhere else? However, it DOES spell out that the View menu should NOT contain items for displaying panels and indicates that the Window menu should be used for this instead! The View menu is meant to control the way things are displayed within a window and should never be used to control whether or not other windows (panels or otherwise) are displayed or to navigate among them. My interpretation is that if a panel fits better in a different menu it is fine for it go there, but otherwise they should be in the Window menu. Thus all of the following being in the View menu in the current Photo beta are wrong and directly violate the HIG: A few of those options, such as the Resource Manager, could reasonably be moved to the Document menu if desired, but otherwise the Window menu is appropriate (the View menu is NOT). However, having these options in the Text menu (for example) should be fine:
  5. Just so this doesn't lose attention, this is still happening in the latest release candidates of all three apps. It seems this happens after an unsaved document has been open long enough to be auto-saved; if you just quit immediately after creating a document and quickly adding a shape to it this doesn't seem to occur.
  6. Explained here: https://affinity.serif.com/en-us/publisher/studiolink/ The way I'm reading it, the intent of "StudioLink" is to allow access to photo and illustration tools from within a Publisher project - in other words, you are designing a publication (what Publisher itself is intended for) and need to create or manipulate vector artwork, so you can switch to the Designer persona within Publisher to work with vector artwork that is being used inside of a document that is still basically within the realm of what Publisher is ultimately designed for. I don't see any indication that it was ever intended to replace using Photo separately for working with a photo as the end product or using Designer separately for creating vector artwork as the end product. If you are creating an illustration as the end product in its own right, it would still be best to do that in Designer rather than in Publisher - but if you are creating a book or similar product and need to create an illustration to use within the book you are working on, that is what StudioLink is for, and for that it is great. The current Export Preview feature is really optimized for standalone art pieces and does not seem to be particularly optimal for a publication. While adding it to Publisher would not be unwelcome, I don't believe it would be particularly helpful for the use cases that Publisher is intended for. I think a better option for Publisher would be to add a separate persona for prepress setup and similar tasks such as color separations and imposition and that a more complete preview function should be included as part of that persona. Yes, Publisher would benefit from an export preview, but to really be useful for its intended use cases it needs something a bit more sophisticated than what has been added to Photo and Designer in this round of betas.
  7. Then what would be the point in having three programs? They could just build it all into one program and be done with it - but that obviously is not what they want, as has been discussed multiple times in the past. If it works for you, great - nothing wrong with that, just possibly not what was intended.
  8. Sure - If I do a File -> Edit in Photo after creating the layer, I can double-click the thumbnail in Photo and edit it there, and the effect does carry back over to Publisher if I then send it back... but that saves me nothing over simply doing a File -> Edit in Photo first then adding the layer.
  9. It doesn't crash for me on the Mac. The layer gets created but is worthless within Publisher unless you switch to Photo to edit it.
  10. Why does the Photo persona in Publisher allow you to add a Liquify live filter to the document if you can't edit it without switching to the Photo application anyway?
  11. I believe the point of StudioLink is to make it more convenient to work with resources embedded in Publisher projects, not to replace the use of the other programs for their own dedicated tasks. This is hardly the only thing you are missing by working that way - no access to the RAW development feature set or the Liquify or Tone Mapping features of Photo, no Export persona, etc.
  12. I created a new document in Photo (1.9 RC1). I added a simple rectangle, gave it a fill color, and used Duplicate Linked. I then did a copy/paste, which actually pasted another linked rectangle - ok... I then unlinked that rectangle by clicking the topmost link icon in the Links panel, but the link indicator still shows in the Layers panel, even though in theory that rectangle should no longer be linked at all - correct? I then did a copy/paste on that rectangle, and the new one also shows as linked in the Layers panel, even though it is not actually linked to anything (color changes independently). It seems there is some kind of issue with the link indicator in the Layers panel.
  13. For whatever it is worth, Apple has been using the term "Dialog Box" since before the invention of Windows: https://lowendmac.com/2005/innovative-macintosh-system-1-0/ They still do: https://developer.apple.com/design/human-interface-guidelines/macos/windows-and-views/dialogs/
  14. It is understandable to be disappointed that your expectations are not being met, and maybe even frustrated, being angry about it is something else entirely, and is neither justified nor appropriate. It is very sad that we are not surprised by this anger. It means that we have a very negative view of the character of the larger base of customers in general, which is quite unfortunate. I think there have been a number of misreadings of others' posts and pointless replies to things that are going around in circles and ignoring what responses have already been there, and I don't think there is much left to be gained from the continuation of this thread... not only has it descended into line noise, but I think the intended subject of the thread has itself been beaten to death already. Let me summarize the on-topic posts of the thread: "We need footnotes and endnotes!" "So do we!" ... "we are working on it and will release it when it is ready". "We need footnotes and endnotes!" "Why aren't we getting any answer to this?" "There was an answer a few pages back!" "We need footnotes and endnotes!" "So do we!" "Why aren't we getting any answer to this?" "We need footnotes and endnotes!" "So do we!" "Why aren't we getting any answer to this?" "There was an answer a few pages back!" (continue to repeat in arbitrary combinations) Does anyone actually have any new material to contribute that is on-topic? If not, I recommend the thread be locked, as it seems to have run its course.
  15. It is kind of curious how many requests on this forum are for functionality that belongs to non-destructive editing tools (such as this particular request). Affinity Photo is by nature a destructive editing tool, so the "original" photo is lost after it is edited, making this feature request contrary to the nature of the software. As per your suggestion, you could pull the data via the history/undo/snapshots mechanism, but that too will only go so far back as history exists, which means that unless the user has the option enabled to save history in the document file (making the document file that much larger in the process), the data will only exist back to where the document was most recently opened. What might work out a bit better would be a feature to compare the image with a selected snapshot, or possibly with the oldest available historic version of the image, either by flipping the entire view between the historic version and the current one by splitting the display with a movable divider, similar to the one currently available in the Develop persona.
  16. I don't follow this either. Why should the overflow area get the labels and the main context toolbar not get them? In order to see the labels on items that your window is ordinarily wide enough to display, you would need to make the window uselessly narrow in order to force those items into the overflow area. It probably isn't possible to make the window narrow enough to force the leftmost items on the context toolbar into the overflow which means their labels would never be visible. How is any of that behavior any more "ergonomic" or "graphic" than what it is doing now, which matches the behavior of the overflow area to the toolbar itself?
  17. If you are importing Illustrator files into Designer, then it is possible that even if the metadata panel were made available it would not contain any useful information. Illustrator documents contain an embedded PDF stream which is what is actually imported by the Affinity products, so unless the metadata is included in the PDF stream (I don't have any here to try to check) then it would be invisible to Designer anyway (or to Photo or Publisher for that matter). I do note that the author at least does sync between the Metadata panel in Photo and the Fields panel in Publisher...
  18. There should be a drop-down for that too... call it "Pose" - "Sitting" (old cat), "Walking" (new cat)...
  19. Push button labels should always be verbs in modern apps. "OK" is not a verb and should not be used. "Yes" and "No" are not verbs and should not be used either. What "X" are you clicking on? If you are closing the document, then the correct thing to be asking is whether or not to save the document before closing it. If it cannot be saved without completing the development (which is a document model deficiency in my opinion), the buttons might be "Develop and Save" and "Close Without Saving" for example. If you are switching to a different persona the options might be "Develop and Switch", "Switch Without Developing", and "Cancel", if we really need to keep this modal behavior for some reason.
  20. Chroma keying can be a complex task due to issues with spill and the like, which a simple color range selection tool is not sufficient to address. There are dedicated tools for this which can easily cost real money. Most of them are focused on video work, but there are a few around for stills work as well. So far I have mostly been interested in doing this with video so other than observing that they exist I haven't really delved into the particulars of the ones that are offered for stills.
  21. I'm right-handed and prefer the tools on the left. Of course I wear my watch on my right arm too, so maybe I'm just strange like that... who knows... Having options to customize these things per user is always welcome of course.
  22. There should be a drop-down in the context toolbar for the cat tool to select a breed, too.
×
×
  • 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.