Jump to content

dconnet

Evernote Employee
  • Content Count

    655
  • Joined

  • Last visited

  • Days Won

    14

Posts posted by dconnet


  1. 1 hour ago, actant said:

    Do you mean that Evernote APIs can access the local database directly and also get the changes synced to the server? Thank you!

    No. Don't do that. Don't.

    FYI: Windows does have the enscript utility:

    (c:\Program Files (x86)\Evernote\Evernote)
    >enscript -?
    
    Usage: ENScript <command> [options]
    
    Commands:
    
      createNote     - creates note from the specified file or url
      importNotes    - imports notes from the specified export file or url
      showNotes      - displays specified notes in the Evernote window
      printNotes     - prints specified notes from the Evernote window
      exportNotes    - exports specified notes into a file
      createNotebook - creates a notebook
      listNotebooks  - lists specified notebooks to standard output
      syncDatabase   - synchronizes database to the service
    
    Type "ENScript <command> /?" to get command specific help.
    
    @filename - specifies response file name contaning options one per line.
    
    Command line options that follow response file name specification override
    options specified in the response file.


     

    • Like 3

  2. Do you know which version was installed previously? I'm thinking it was an earlier version - if you ran that, it should run in repair mode and fix the broken installation. The installer you're running thinks the old version is still installed and is attempting to do an upgrade - part of an upgrade is uninstall - and that's what's failing (because the MSI was lost in the migration - which a repair will fix)


  3. 1 hour ago, EdH said:

    I'm not exactly sure why

    File-changed notifications are notoriously bad on network devices. (Not the same reason we don't support putting the exb out there - that's because file locking is notoriously bad.)

    • Like 2

  4. 47 minutes ago, jbenson2 said:

    The program would randomly shut down with no warning and no error message a few times during the week. Evernote would not start up again unless I rebooted.

    These are the hated bugs - random. Very hard to repro and fix. Sigh.

    An alternate to rebooting: Open Task Manager and kill the running Evernote processes. You can leave EvernoteClipper.exe - that's not what prevents EN from starting again. It's the Evernote.exe, EvernoteSubprocess.exe, and EvernoteTray.exe processes. When the main Evernote.exe crashed, it died in such a way that the other processes didn't catch that and proceed to act very badly.

    • Like 2
    • Thanks 1

  5. 39 minutes ago, jefito said:

    Dunno if that's just development time

    That.

    Edit: BTW, I should mention I played around with trying to expand our current theming to the list controls (standard windows controls) that we use for the note list. It was a complete failure at making it look right.


  6. On 5/27/2019 at 3:53 AM, s2sailor said:

    My interpretation of the response is that it is a bandwidth / priority issue.

    Precisely. My (very rough) estimate is that it would be a minimum of 6 months of effort. Almost everything in the UI is custom drawn. (Actually many of the custom drawn things are probably easier to update than some of the standard windows controls are!)


  7. 4 hours ago, n5z said:

    would finally include dark theme for windows

    Most other platforms get dark theme support for free. Windows does not. (The Windows dark theme support you hear about is only available to UWP apps. That's not us.) The likelihood of the current Windows version supporting a true dark theme are about 0.1%.


  8. 1 hour ago, Don Dz said:

    I am guessing that since you did not address my comment about the reminder view specifically, it must not have been present, whatever I thought I saw in the note list  at the time.

    Ah, sorry... The reminder list has not changed in Windows. It is not in either of the list views. (And unless something changes, there are no plans I know of to add it.)


  9. 3 hours ago, Don Dz said:

    I could be mistaken, but I am fairly certain I saw that view in the recent beta 2 on the side list (I believe it went away after they had to do some major surgery for the current beta 3, see the discussion), maybe they will bring it back eventually.  Unless I was just seeing things . . . 

    FYI: All features that were in Beta2 are in the current Beta3. (It was the first Beta3 release that was the pain-point.)


  10. 12 hours ago, Don Dz said:

    Rather than not implemented, it seems buggy.

    How an emoji renders is dependent on the font used. Not all fonts can display all characters. Different fonts may be used in different areas of the program - we do support user specified fonts for the caption (this is a per-client setting - not a syncd property).


  11. Just a terminology clarification (at least when I talk about them!). In EN, F9 is an "accelerator". Cortana's F9 is a "hotkey". The difference is an accelerator will only work when an application has focus. A hotkey is a system wide hook that works no matter who has focus - as such, the app who registers first wins - and all others lose. It's a constant battle! (EN does have some hotkeys - these are configurable in the Options dialog. Accelerators are not configurable.)

    • Like 1

  12. 17 hours ago, TdeV said:

    Evernote is telling me I have to uninstall 6.18.2.8380 to proceed. I think an upgrade has never told me this before. Should I proceed?

    It sounds like this is doing the 6.17.7 upgrade (which is really a downgrade). Since you're on beta2, skip this. A new Beta3 is now available and will upgrade in the way you expect.

    • Like 1

  13. 15 hours ago, Don Dz said:

    Hmm, somehow I think it should have been called beta 4,  to avoid confusion with the other beta 3 (and to discuss it separately), but ok.

    True. We probably should have - it would still be 6.18.3 tho! (because of the MSI update issues I talked about before)


  14. 11 minutes ago, EdH said:

    Reboot requirement is a new thing.

    We try to avoid this style upgrade - as I noted, we re-release Beta3. So MSI sees this new version as the same version as the old Beta3 - this is the same-version upgrade path. It's not very user friendly, so we try to avoid ever doing this publicly. However, the old Beta3 has a newer version of CEF - so any upgrade from that would cause "very bad things" to happen (because we would be violating MSI component rules). We made a conscious decision to inflict that same-version upgrade so the CEF dll downgrade would properly install.

    Probably as clear as mud now.

    tl;dr: Installers are hard. Downgrading files during an upgrade is harder.

    • Like 2
×
×
  • Create New...