-
Posts
219 -
Joined
-
Last visited
-
Days Won
4
Content Type
Profiles
Events
Forums
Blogs
Gallery
Downloads
Everything posted by dcon
-
Actually, the fix is easier. Just unpin the blank icon. And re-pin. Officially, Microsoft does not allow access to changing user choices (pinning is one), so the installer doesn't try to do nefarious things like other installers (Firefox!) do. Since the underlying exe has changed, MS no longer considers the previous pin a valid shortcut.
-
I remember that! I owned a number of versions of it. Still like how it determines estimated drive times better than what Google does now... (since it uses, by default, lower speed limits, it effectively accounts for stop lights - which google maps obviously doesn't - since my ETA always slips when I'm caught at a light!) (I actually started fulltime AT&T in 89, started as a contractor there in 87)
-
Hyperlinks not working
dcon replied to Glenn Shukster's topic in Evernote for Windows Issues (Versions 6.25.1 and under)
I'm pretty sure that was the last thing done during shutdown. Obviously making sure the database is properly closed is the highest priority! Guess I'm pretty lucky at this point in my career - my bosses usually listen to me when I say it's worth taking the extra time now! Age (and experience) do still count for something in our world! (mumblemumble young whippersnappers and their framework-of-the-week mumble...) -
Hyperlinks not working
dcon replied to Glenn Shukster's topic in Evernote for Windows Issues (Versions 6.25.1 and under)
2 out of 3's not bad... -
Hyperlinks not working
dcon replied to Glenn Shukster's topic in Evernote for Windows Issues (Versions 6.25.1 and under)
Except that the clean shutdown process with EN sometimes takes longer than the time Windows allows when it's rebooting. End result - the registry settings don't properly get flushed. (Ever tried debugging a program during shutdown? Yeah, it's a problem... 🤣) Before I left, I was working on a "stealth" project to always write the settings to the registry when they changed. That change was getting big/scary. Design advise: Never allow direct access to member variables in a C++ class. -
As @jefito mentioned - use Task Manager. Every time I've seen EN not start when I try to, it's because of a hung process. Killing the existing EN processes allows things to return to normal. (The monitoring process gets very confused when EN crashes - the lock (global mutex) doesn't get cleaned up so when another instance tries to start, it goes "Oh, I'm already running - bye!")
-
some queries re Evernote premium
dcon replied to amartya's topic in Evernote for Windows Issues (Versions 6.25.1 and under)
As I remember, if you set the global option for 'view as attachment', that's what all notes get (hence why the above is greyed out). If you uncheck the global option, then you can control notes individually. -
That would probably be the confusion - as this forum is for the Windows beta...
-
The Evernote Editor
dcon replied to PeeJayTee's question in Evernote for Windows Requests (Versions 6.25.1 and under)
Each previous incarnation is replaced by the next. As far as I can remember, if you've been using EN for a number of years, you're seen every "new editor" that was released. As I understood it, the new "new editor" is part of the new program that's in the private beta. (Which some people here have tried - I'm haven't.) Whether it will be retrofitted into the Windows product? 🤷♂️All I can do is speculate like the rest of you now! (My speculation is no.) -
Special Symbols
dcon replied to KenGamble's question in Evernote for Windows Requests (Versions 6.25.1 and under)
Windows 10 Fall Creators Update (Fall 2017) -
The Evernote Editor
dcon replied to PeeJayTee's question in Evernote for Windows Requests (Versions 6.25.1 and under)
Nope, pretty much nailed it! (I'm only talking about the Windows platform - I don't know how the other platforms embedded the editor) They weren't abandoned. They went into the product. Sometimes the updates were very noticeable to users because of the differences. Sometimes they weren't (good regression tests in those cases!). -
The Evernote Editor
dcon replied to PeeJayTee's question in Evernote for Windows Requests (Versions 6.25.1 and under)
For certain definitions of "joy"! LOL! -
Dealing with DB "Bloat"
dcon replied to TahoeLocal's topic in Evernote for Windows Issues (Versions 6.25.1 and under)
To add to that - after creating the 2nd account, create a folder there and share it to your primary account (or share a folder from the primary to the 2nd acct). You can then just drag/drop the notes to move them. The only "gotcha" is it will leave them in the primary computer's database. You could move them out of the folder on the 2nd account to a different folder (either synced or local) and just use that shared notebook as a transfer folder. Advantage: Don't have to export/import. Disadvantage: Sharing. (It can be a little weird sometimes. It works. But it can be weird. I say that as one of the people who use to work on that feature!) -
The Evernote Editor
dcon replied to PeeJayTee's question in Evernote for Windows Requests (Versions 6.25.1 and under)
We were (pretty sure I'm allowed to say this...) actually looking to consolidate that in a common C++ core library. That work was put on permanent hold (at least it was when I left) in favor of the new version the CEO has been referring to. -
The Evernote Editor
dcon replied to PeeJayTee's question in Evernote for Windows Requests (Versions 6.25.1 and under)
Hehe. We wrote the app that contained the containing app! Google wrote CEF. (ok, we modified that too) The only reason I maintained my sanity is because I stayed as far away from the CEF tweaks as I possibly could. (Just building that thing was a nightmare - let alone actually looking at that code!) -
The Evernote Editor
dcon replied to PeeJayTee's question in Evernote for Windows Requests (Versions 6.25.1 and under)
That's the browser framework the editor is built in. CEF1 was used when I started. The first common editor targeted CEF3 but was backported to CEF1. The CEF3 upgrade was pushed by several things - lack of support for CEF1, and effort for the editor team to support it. Upgrades to CEF were completely orthogonal to CE updates.