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


  • Posts

  • Joined

  • Last visited

  1. Right. I drew the same conclusion. I don't think I agree with this line of thinking, however. Having it as an option? Sure. Having it as the default? Not so much. There's a commonality I've observed in serial "product managers" who tend to make this decision this way. Being in this field, I've had several conversations with product managers and interaction designers about this exact topic. Because there is so much disagreement on this topic (brand-first vs platform-first), customers have seen (and gotten used to) enough inconsistency that whichever way you go, you will absolutely piss-off someone. But I still fall squarely on the platform-first side of the interaction design debate. On macOS: Command+S should always save, always. It's a standard platform convention. Command+C and Command+V should always copy and paste. Most people work on a single platform. You learn how to traverse and select text on that platform (as in my case), and it should arguably work the same way across ALL (native) apps. There is a minor (but worth paying attention to) group of people who work cross-platform. Some of those patterns are strong enough to cross the platform barriers (e.g., Ctrl+S, Ctrl+C, Ctrl+V), and others are not (e.g., keyboard-driven text selection, multi-selections, behavior of the shift key when Caps Lock is enabled). That's where you will inevitably have differences. But I believe that the majority of users will be inconvenienced by generic "brand-first" controls than will be inconvenienced by generic "platform-first" controls. I'd love to see the hard data as evidence for this particular decision, but in reality, any data which _may_ exist is entirely proprietary and internal. We’ll likely never know if this decision was based on anything more than a product manager’s whim.
  2. Ah! Good find. It's unfortunate that this is the default, however. It's a flawed form of thinking when a company puts their brand/patterns/whatever ahead of the standards for the platform. I know lots of companies do it, and all of them are wrong.
  3. Appreciate the input. I've done a lot of work with ePubs, which can be easily done with VSCode and Pandoc. I'm looking at Affinity Publisher as a more affordable alternative to Adobe InDesign or QuarkXPress. Comparatively, Pixelmator is a fantastic alternative to Photoshop; Sketch is a fantastic alternative to Illustrator. I was hoping that Publisher would also be a fantastic alternative. It's not that the product is bad — it's pretty good for the first 90% of the project! But it definitely lacks tools for the final 10%. I was really hoping that the staff would care enough to participate and engage in actually working to solve customer problems. If it's true that "it will be a long time before your requests are fulfilled, assuming they ever are", I don't know how much I should bother investing here.
  4. Thanks, and I understand. That's why I'm posting this in the Feature Requests section.
  5. Using Find-and-Replace, I know that I can: Find by literal text Find by regex pattern Find by style Find by text or regex pattern with a particular style But something I miss from CSS is the ability to match by: A direct child Any descendant child First child Nth child Siblings Here is a real example of a find that I wanted (and can do in CSS), but was unable to perform with Publisher: In the section labeled "Appendix B"… After a heading with the style "Heading 4 containing a Citation"… After the heading’s sibling paragraph with the style "Quotation"… Select the first sibling paragraph, if any… And assign the style "First Paragraph after Heading or List" to it.
  6. Related to this and this, I have chapter titles made up from multiple styles. For example: ---- Chapter 1: Structure of the Federal Justice System ---- In this case, "Chapter 1:" has a style of Heading 1 with Sub-Head Next, and "Structure of the Federal Justice System" has a style of Heading 1 Sub-head. What I would like to be able to do is generate a ToC entry of "Chapter 1: Structure of the Federal Justice System".
  7. Currently, the Table of Contents (ToC) are generated literally. That is, whatever is written in the headings on the pages is what ends up in the ToC. I agree that usually, this is the right thing to do. I'm typesetting a book with lots and lots (and lots and lots) of U.S. Case references. The headings in the book are the full case references, but in the ToC, I'm truncating them to just the most essential parts. Here's an example: Heading “United States v. Richardson, 245, No. 1:97-CR-012 (D. Ida, Apr. 23, 2021)” → ToC item “v. Richardson (2021)” Presently, I'm having to make hundreds of these adjustments by hand. In addition to this, I think that being able to generate the ToC (or part of the ToC) by regex would be extremely helpful.
  8. In "standard" (i.e., native) macOS apps, there are specific keyboard controls which are how cursor movement is done on the Mac: Command + left/right will go to the beginning/end of the line. Option + left/right will move by word. By extension of those fundamental text controls, this is how text selection is done on the Mac: Command + Shift + left/right will select the entire line to the left/right from your starting point. Option + Shift + left/right will select the next word to the left/right from your starting point. I'm doing this in Safari right now. It's a standard Cocoa behavior. Publisher does not follow this convention and it's (bleeping) up my world. In Publisher: Command + left/right is used to move by word. Option + left/right doesn’t appear to move the cursor at all. There isn't a good way to move to the start/end of a line. 20 years of muscle memory falls to the wayside every time I open Publisher (and many other non-native/non-Cocoa macOS apps). Breaking the standard HIG patterns on the platform is 100% a bug.
  9. I'm working on a technical book, and I very much miss my multiple-cursor support. Presently, there are changes that I'm making line-by-line that would be dramatically faster if I could set multiple cursor points and make changes across multiple lines at once. If you're unfamiliar with this concept, here's a link: https://duckduckgo.com/?q=vsode+multi-cursor+support
  10. I want to do some regex pattern replacements, but ONLY in one specific "section" of the project. As far as I can tell, there isn't a straight-forward way to do this. I would love to see better support for this in a future version of the product.
  11. I've also been dealing with this in in Git. Both bitmap (PNG) and vector (SVG) images are affected by this, although only the bitmap images are blurred, it resets the settings when this happens as well. I've been having to go through and manually reset the settings on each image after a `git pull`.
  • 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.