Custom keyboards = awesomeness

Vince's Avatar

Vince

28 Nov, 2017 05:20 PM

It's your customer you wished still used MacDown. :)

4.2 is awesomeness in a box. (OK, not a box, but "awesomeness in a bunch of electrons" doesn't have the same ring to it.) I opened the default file, added a quick Cmd-K to insert a left bracket and left-paren, and presto-magicio, a link hotkey! Great job, and thanks for all the fish!

Just a few notes and/or questions.
1. It appears that MMD only reads the file at startup, i.e. editing it requires a re-start for the new keys to take affect? Or is there a way to force it to re-read? Either way, you might want to explicitly state that on the help page.
2. The help says, "As usual, you can use a button in the Pro Preferences to open this file for you automatically." but the button says "Open KeyBindings Folder" — did you mean "folder" there instead of "file"?
3. I copied the schema from your link and the unchanged default file using the JSON schema validator, and it still gives me an error. I attached a screen-print; it can only show the lower half of both files, but I just cut-and-pasted both of them and I did it a couple of times to make sure I had everything. They both look OK, i.e. have the correct opening/closings, etc., and the default file obviously works, so it appears to be a problem with the validator. Or I'm doing something wrong in my cut-and-paste.
4. A couple of things to consider for the future. First, it would be nice to have a way to view the customized keys in a clean GUI dialog or something instead of having to open the file and read the JSON.
5. I assume the keybinding folder isn't replicated in iCloud, so we have to manually copy the file to a new computer when MMD is installed, correct? It would be nice™ to have the file in an iCloud directory that was automatically replicated, so changes to one computer automatically made it to our other ones.
6. Last ("a couple" can mean 2-4, right?), and a much bigger deal to be sure, it would be nice™ to be able to put our keys on the menu even if they're not replacing something already there. I don't know if dynamic menus are as feasible as dynamic keys, but it would be nice™ none the less.

Regardless, great job!

  1. Support Staff 1 Posted by Fletcher on 28 Nov, 2017 07:26 PM

    Fletcher's Avatar

    Nahhh.... If you used other software, you wouldn't find bugs for me to
    fix in mine... :)

    I'm glad you liked the new feature -- I thought about you and your
    hotlink request as I finished this one up....

    1. Composer reads the file at launch *for the menu bar*. It reads it
    again for each new document window *for the non-menu bar* hotkeys. You
    can reopen your documents to start using the new commands right away,
    but they won't be updated in the menu bar. That requires a restart.

    2. Changed

    3. The schema was missing a comma after the comment line. I just
    updated it. The keybindings file itself was ok. (Thus far, I have not
    encountered any bugs in the schema validator web pages, so in general if
    it says there is a problem, there is a problem.)

    4. Agreed -- but that will be a fair amount of development time that
    could be better spent on other things right now. (trust me on this
    one.. ;) I'll come back to that when I finished up the better features
    I have planned.

    5. That's already available, just like with themes and CSS (Multiple
    Devices in pro preferences). I *DO* recommend backing up your files
    when doing this -- I have had some instances where my updates get
    replaced by the default versions when I play with the iOS test builds.
    I have not noticed problems with the Mac app by itself. The "Restore
    Deleted Files" becomes your friend in this instances, but an external
    backup doesn't hurt.

    6. This is technically possible, but would also require a fair amount of
    work to get it right. Plus it wouldn't work with macros since menu
    commands only call one action (that would require creating "wrapper"
    actions, and at some point it just gets really messy, and also risks
    running afoul of App Store rules.) For now, this is in the "I would
    like it too, but don't hold your breath" category.

    And as above, stay tuned -- more is on the way.

    F-

  2. 2 Posted by Vince on 28 Nov, 2017 08:31 PM

    Vince's Avatar

    1. Gotcha. You might put all of that in the help file, just for clarity.
    3. Confirmed, all OK now.
    4,6. No worries, these were nice to haves, I don't feel strongly about them in the short term. :) (I don't feel strongly about the menu one at all; I guessed it was probably a lot more difficult than the keys themselves.)
    5. Hah. I've never noticed that checkbox before. And, I read your entire paragraph, but didn't actually *process* it. You have now "seen" the Mac app replace the modified file with the default. :) I only had that one new key, so NBD. Just for information, in case you want to try to replicate — I upgraded A, modified the default file on A, then upgraded B and checked the Multiple Device on B *before* I checked the multiple device on A. So maybe it goes from whichever one is checked first to the other one(s)? It would be nice™ if it always kept the later date file, but that might be out of your control. Anyway, as I said, NBD, just providing the information in case you ever want to try to replicate it.

    Thanks again, great stuff.

  3. 3 Posted by Vince on 28 Nov, 2017 08:35 PM

    Vince's Avatar

    Oh, one more thing I forgot. Is there a reason MMD isn't marked as being able to open the .keybinding files? Maybe because it wasn't a new installation? Or are you not doing that at all? It seems a little weird that MMD can't open it's own configuration files by default.

    And one more FYI nit — on B above, I hadn't upgraded yet, and when I opened MMD 4.1.3, it went to the web page automatically, but it went to the 4.1.3 web page, not to the 4.2 web page. IOW, it went to the same page as the version as I was already on.

  4. Support Staff 4 Posted by Fletcher on 29 Nov, 2017 02:22 AM

    Fletcher's Avatar

    > Hah. I've never noticed that checkbox before. And, I read your entire
     > paragraph, but didn't actually *process* it. You have now "seen" the
    Mac app
     > replace the modified file with the default. :) I only had that one
    new key, so
     > NBD. Just for information, in case you want to try to replicate — I
    upgraded
     > A, modified the default file on A, then upgraded B and checked the
    Multiple
     > Device on B *before* I checked the multiple device on A. So maybe it
    goes from
     > whichever one is checked first to the other one(s)? It would be nice™
    if it
     > always kept the later date file, but that might be out of your control.
     > Anyway, as I said, NBD, just providing the information in case you
    ever want
     > to try to replicate it.

    Actually, it seems to be some strangeness with iCloud's data store.
    iCloud is so much better than it used to be (both as a user and as a
    developer), but I'm still not convinced it's "up to snuff." (I've spent
    the last few days working on iCloud/Dropbox code, and Dropbox is still
    so much more reliable...)

    But I'll look back at this Composer config sync again when I get a
    chance and see if I can improve it.

    F-

  5. Support Staff 5 Posted by Fletcher on 29 Nov, 2017 02:25 AM

    Fletcher's Avatar

    It's because the file extension isn't recognized by the system as a text
    file. I'll add a UTI for it.

    That web page is just an announcement mechanism -- nothing to do with
    which version of Composer is in use. If there's a new announcement that
    you have not seen (on that computer), it opens the web page when you
    launch Composer. I rarely use it, but 4.1.3 fixed a few important
    crashes and I wanted people to upgrade it. (many people apparently don't
    update their apps very regularly, even though App Store does it for you...)

    F

  6. 6 Posted by Vince on 29 Nov, 2017 04:49 AM

    Vince's Avatar

    Yes, I've been hearing that (iCloud) multiple times just today. (I went looking for why Scrivener doesn't use iCloud for syncing, lots of words that boiled down to your three words. :) But, I'm not using Dropbox, so I'm glad for your work, even if it is a hassle.

    Ahh. I knew it was announcement, I just figured it wouldn't show announcements for a version you're already on. And even with what you said, that would mean I upgraded to 4.1.3 but never actually opened it. That seems … weird. But maybe not. I haven't been using the laptop much lately.

  7. Fletcher closed this discussion on 02 Dec, 2017 01:57 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac