Jump to content
Due to limited holiday staffing, chat will be unavailable from Thursday, July 2 at 5:30 PM (CDT) to Monday, July 13 at 8 AM (CDT). This will allow us to reply to your email requests as quickly as possible. Thank you for understanding. ×

dconnet

Evernote Employee
  • Content Count

    655
  • Joined

  • Last visited

  • Days Won

    14

Everything posted by dconnet

  1. No. All you can do is try to register it. If it fails, someone has it. The way people figure out "who" has it - use taskmgr and kill processes until the hotkey is released.
  2. Oh great. Another of our default hotkeys has been hijacked by Microsoft... sigh. (Whoever registers the hotkey first gets it. Windows has an advantage there.) > did they bother research what windows built in shortcuts are? Yes. Yes, we did. And then MS released an new version of Windows and here we are.
  3. Try disabling hardware acceleration: Tools -> Options -> General -> "[ ] Enable Hardware Acceleration"
  4. Sorry, no. We don't give out internal details like that or scheduling info. (I remember creating the bug/feature-request when I stumbled over an MS blog "Supporting “launch at startup” in a desktop app converted with the Desktop Bridge")
  5. It's in the backlog. Windows Store apps are ... um ... different. So the startup doesn't work the same.
  6. As far as I know, there have been no code changes around links... If you right-click over the link and select 'Edit' from the context menu, does the link appear to be ok? I'm wondering if somehow the link's actual link got changed... If that appears ok, then I suspect some OS setting was changed that's blocking it... (no idea what - maybe some other program hijacked the default http/https protocol?) (My links are opening in Chrome)
  7. Depends what version of Win10 you're on! Microsoft stole that shortcut for their screen clipper. He-who-registers-first-wins.
  8. Because we haven't fixed it yet. We're actively working on it, but there's many moving parts and things we thought for sure would work caused havoc in other areas.
  9. We released the hotfix last night, so the email issue should be fixed now.
  10. It was released last night. ("Help -> Check for Updates" to get it now, I don't believe we've released it to 100% yet - but a manual check will always find it)
  11. The way it is presented is slightly different, though the font size should be the same. We now allow you to specify the font and font size for the title. That was the only reasonable way to get all character glyphs to show correctly. (I'm not aware of any standard Windows font that has all unicode characters. Text is hard.)
  12. I have a fix pending review. This problem would have also been in the last Beta, but we missed it there. This is related to the new note failure in that Beta.
  13. Ah *****. We fixed the issue from the last Beta with this in the main EN application. But missed it in the other supporting executables. I'm on it...
  14. This was an issue that slipped out in the last Beta. It is fixed in the GA (recently released). Edit: Oh. Different but related issue. A fix is pending.
  15. Hardware acceleration can also be changed via the Options dialog (on the General page).
  16. I shudder to implement this because of ambiguity (yes, I'd be the one on the Windows platform)... You realize %APPDATA%.txt is a valid windows file name?
  17. As far as I know, we do not support environment variables in a link. (For one thing, they're not cross platform so that link could not work on any platform other than Windows)
  18. Yes, this is correct. Currently the program remembers the last "notebook" (in quotes as it applies to things like all-notes and workspace views). Remembering the last view would be a (nice!) feature enhancement.
  19. They are 2 completely separate instances running. With some coordination via the tray icon program. Program robustness for detecting that other instances have crashed could (um, yeah) use a little work...
  20. As far as I remember (without digging into the code), we check the database when it is opened. Having the database live on a network drive is risky. We rely on sqlite file locking and that may not work on networked drives. (As I remember, that warning was added because people kept complaining about data loss/corruption when on a networked drive.)
  21. Thanks - this is a known issue. We have a bug tracking it (well, the bug is actually for Russian, but it's the same thing!)
  22. There was. There wasn't. There is. It went away for a while and then was resurrected in a new form. That's been available for a while now.
  23. Simply viewing the note will index them. What I need to test still is what happens to the others. (It also indexes when the note is updated on another machine and synced) It's still very early in testing (I mean I literally figured out the issue just before lunch time today!) - I still need to add some UI to turn this off for users who have "bad" pdfs that crash the filter. (I have some better ideas for blacklisting bad pdfs, that that will take at least a week to prototype and we're trying to get a beta3 out "real soon now".)
  24. I just realized why searching stopped working. The IFilter plugin we're using was causing a lot of crashes (when sycning) so it was removed (certain PDFs caused total memory corruption - no exception handling could catch it). Turns out that was how the pdf text was being indexed in the database. Which means I am now working on putting back this filter - which _will_ causes crashes for some people. But we'll add a registry switch to turn it off also. In the meantime, we're investigating an upgrade for the filter (I remember many years ago being told we had decided not to upgrade because of cost - hopefully that's changed!) (FYI: OCR has nothing to do with this)
  25. Internal verbiage slipping out... Yes, that view was created when we brought back the notebooks view (aka NBK). That same notebook list is also used for Spaces and SharedWithMe views.
×
×
  • Create New...