Jump to content

dcon

Level 3
  • Posts

    219
  • Joined

  • Last visited

  • Days Won

    4

Posts posted by dcon

  1. Most people who have seen this have are basic users with 2 devices already registered. There's evidently a bad bug in the server where the page that tells you this is completely messed up. Log in to the web interface and use that to revoke a device's access (v6 and v10 count as separate device instances)

    Edit: v6/v10 being 2 instances was a rumor I thought I'd seen in another thread - corrected below by Shane, so editing that out here!

  2. On 12/9/2020 at 10:18 AM, Milincho said:

    2 months and counting to just disable a setting...     what a bunch of awesome coders.   💩

    The coders could very well have the fix complete. Completion of a fix does not necessarily mean it will be in the next release. There are a lot of things gating bugs/features moving forward. (QA availability, Management decisions, etc...) As a dev, that can be a particularly annoying aspect of development cycles.

  3. On 12/1/2020 at 1:15 PM, gazumped said:

      It's a Windows standard behaviour that clicking the top-right 'x' will just close the window but leave the app running.

    That's not a standard Windows behavior. Standard behavior is to close the program. Evernote's standard behavior is to continue running. (Unless you're running legacy and uncheck the 'sync in background' option!) A program has to go out of their way to change the 'X's behavior.

    • Like 3
  4. 37 minutes ago, Don Reba said:

    I don't know the details, but I find the claim that a 32-bit program couldn't use dark mode hard to believe.

    It has nothing to do with 32bits. Windows dark mode is only available to Windows Store (.net) apps. The EN (legacy) client is a Win32 (full thick client windows application - "win32" can mean either 32bit or 64bit - yeah, weird developer nomenclature) app. Win32 apps using native controls simply do not have access to the dark mode api. It used to be that a Win32 app couldn't even determine if dark mode was enabled without checking an undocumented registry flag. I don't know if that has changed since I looked at it.

    > But, even granting that, it's pretty unusual to have to rewrite much just to recompile a program in 64 bits. Most of the time, it does not take any changes at all.

    ROFL!!! BTDT, seen many pointers pushed into a 32bit variable. It's not that it won't compile - it will - and then proceeds to blow up in the most interesting ways! The first step is seeing what the compiler tells you (with warnings cranked all the way up). The 2nd step is inspecting pretty much every line of code that works with pointers.

    Also, as I remember, there were some 3rd party libraries we (past tense, I've been gone a while now) used that didn't support 64bits. So the effort required to update was deemed too much - since we still had to support 32bit OSes.

    • Like 1
  5. On 11/27/2020 at 2:05 PM, RightPaddock said:

    it installed ok, but it would not let me 'login' because it didn't have an internet connection

    That has always been the case with Legacy. When you login, it has to verify against the main server. It then stores an access token locally so you can remain logged in even when offline. That token has a long expiration time. But you can also revoke that token from the web interface.

    • Like 1
  6. Just now, gazumped said:

    Not familiar with W10 "S"

    The "S" stands for "Stupid". (at least that's how we described it when testing on it)

    Ok, it's really (from the ms webpage) "Windows 10 in S mode is a version of Windows 10 that's streamlined for security and performance, while providing a familiar Windows experience. To increase security, it allows only apps from the Microsoft Store, and requires Microsoft Edge for safe browsing."

    • Thanks 1
  7. On 11/2/2020 at 2:36 PM, MotoWolf said:

    After three unsuccessful installs of Evernote 10.2.4 on Windows 10 Pro (ver 10.0.19041) I finally succeeded. But it did not install in a Windows Program Files directory but in C:\Users\(username)\AppData\Local\Programs\evernote-client. What gives with the strange location and why the drama with the installation in the first place?

    They changed from an all-users install to a per-user install. (Pretty sure it's so they can do silent updates without requiring admin access.) I just saw in another thread that they're working on an all-user install. (No idea why you had a problem installing. Of course, I haven't tried. You can pry v6 out of my cold dead hands!)

    • Haha 1
  8. On 10/23/2020 at 1:25 PM, yavin said:

    Why on earth would the even the basic "Win + Shift + F" be removed....

    One reason for that would be anything using the Win key may be usurped by Microsoft. A program not use the Win key as an accelerator (by default).

    I remember when I was there, we used to use Win+Shift+S for screen capture. Then Windows 10 came along and "stole" it. I remember posting messages here for months saying "you need to change the key you have assigned". (Legacy's default was eventually changed to ctrl+alt+s)

  9. 20 hours ago, CalS said:

    Until there is a clear definition of what is in the "legacy" 6.25.2 version I am sticking with the last version I have, 6.25.1 .  6.25.1 is working plus the chaos in the V 10 cluster thingamabob makes sitting on the sidelines seem the right thing to do at this point.

    And 6.25.2 is evidently not an upgrade - I'm on 6.25.1 and doing a "Check for updates" says "nope!".

    • Like 1
×
×
  • Create New...