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

A_B_C

Members
  • Posts

    4,419
  • Joined

Profile Information

  • Gender
    Male
  • Location
    Germany

Recent Profile Visitors

7,354 profile views
  1. Sorry, I had to like them all. 😁
  2. Thank you, everyone! — I had searched the forum before posting, but didn’t find the issue mentioned by Walt. That makes sense. So I agree with what Mike said: hope this is fixed soon. 🙂
  3. Please try the following: Create a new text frame. Insert some text, and place the caret cursor somewhere in the text. Use the Glyph Browser Panel to insert an additional glyph at the caret cursor position by double-clicking the respective glyph in the Panel list. Without clicking anywhere else, use the Backspace key. Expected behavior: The inserted glyph is deleted. Actual behavior: The entire text frame is deleted, even if the caret cursor is still shown inside the text frame. In the following screencast, you cannot see that I pressed the Backspace key, after inserting /abreve/ and moving the cursor to the left, above the text frame. But you can see that the entire text frame is deleted, even if the (non-blinking) caret is still indicating the insertion point in the text frame. Backspace.mov This behavior is, if not a bug, highly inconvenient. When you intend to select glyph alternates, you will often want to try out things in context, that is, you will want to insert glyphs and have the option to simply undo the insertion by pressing Backspace, then insert a different alternate. So double-clicking a glyph in the Glyph Browser Panel should never remove focus from the current insertion point in a text frame. Compare how the macOS glyph panel works. After double-clicking a glyph to insert it in a text area (like /abreve/ in the example below), you can simply press Backspace to undo your insertion: macOS-Glyph-Panel.mov Thank you for your attention.
  4. (Just posted because it wasn’t clear from Leigh’s post whether Publisher is included in the 2.5.1 fix.)
  5. First off, thank you for fixing Designer and Photo 2.5 by releasing 2.5.1. 😀 However, the same problem persists with the Mac App Store version of Publisher 2.5 on my system (MBP Intel 2029, 16'', macOS Sonoma). It crashes on launch. I sent the crash report through Apple’s reporting system, but if you need it, I can send it to you directly as well. Please fix. 😀
  6. FWIW — Last time I tested (by the end of last year), FontCreator does not work in CrossOver.
  7. (And there should be a way to minimize these panels to a list of buttons. Even on a 16'' MBP, it is very difficult to work efficiently in Publisher with the Panels taking so much space.)
  8. You can always store predefined instances (locations in a variation space) to a variable font. Not sure what additional value a “snap to discrete values” function would provide.
  9. While you’re at it, would it be difficult to add the following feature for collapsing and expanding panel sections to all panels? https://forum.affinity.serif.com/index.php?/topic/202656-please-improve-panel-visual-depth-management/#comment-1205284 A better explanation of the feature is provided by fde101: https://forum.affinity.serif.com/index.php?/topic/202656-please-improve-panel-visual-depth-management/#comment-1205349
  10. It’s interesting that there already is a Blender-like solution (confer my screenshot above) for the new Typography Panel, as shown in Ash’s announcement. So the UI framework basically seems to allow transferring a rendering logic for sections from dialogs to panels. Remember that the above rendering of panel sections in the new Typography Panel is essentially the same as it is in the current dialog (and also the same as it is in the current Preferences Dialog), so I wonder whether this new approach could be transferred to all other panels.
  11. @fde101, I couldn’t have explained my suggestion any better … 😀
  12. A modest suggestion that would improve UX in the present framework: please add Collapse-all and Expand-all by Alt-clicking the section headers inside a panel. This would at least provide a workaround for many orientation problems in crowded panels and reduce search time.
  13. While you are at improving the UX by turning the Typography dialog into a panel (thank you very much for that, it is highly appreciated), would you mind reconsidering the overall panels layout too? I still find that the current approach to draw panel sections is not very apt to visually keep things together that belong together, especially in the typography-related panels that have a lot of sections. The z-dimension (depth) management is not really compelling. Visually, the section headers are one level deeper than the panel surface, which creates a hierarchy problem that has been present from version 1.0. A section heading should never sit inside a groove, for when you do it this way, you cannot create the impression that the heading starts a section whose contents will be subsumed under the heading. If you need a section inside a panel, there are much better, time-proven ways to do this. To take a (really just random) example, here is a panel stack from Blender. I hope you can see that the visual depth management that is much clearer than Affinity’s. While it may not be perfect in any respect, it is clear at first glance what contents belong to the sections “Restrictions”, “Instancing”, “Line Art”, and “Custom Properties” respectively: Now confer this example to your visual depth management in the following example. Can you tell at first glance that “Justification” opens a new section? Or doesn’t it rather seem that the bar in which the section heading lives is the footer of the dark area for tabulator settings above? Especially when the scroll bar is present on the right? I hope you can see that there is room for improvement in this area. I know it’s not likely that you will overhaul your entire panel layout on occasion of reorganising the Typography panel, but maybe this change is a good occasion to take a step back and make notes for further improvements in future versions. So I just wanted to mention the problem here (again).
×
×
  • 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.