Jump to content
We apologize for the inconvenience, but chat support is currently unavailable. Please feel free to submit an email ticket or reach out at discussion.evernote.com. Thank you for understanding. ×

jefito

Level 5*
  • Content Count

    18,925
  • Joined

  • Last visited

  • Days Won

    310

Everything posted by jefito

  1. It's coming. It's in the current web beta, as has already been noted in this thread.
  2. Top left corner of the topic, the green triangle with a number below it:
  3. Odd. I invest my time and money into Evernote because of the features it has today, rather than the feature I hope it acquires in the future (but may never get).
  4. Well, I don't understand it, that's whyI asked. If you can't be bothered to describe it any better, than good luck.
  5. Double-click on a note in the note list ~or~ Select a note in the note list and hit Ctrl+Enter ~or~ Select a note in the note list, right click, and select Open Window ~or~ Select a note in the note list, and in the main menu: Note / Open in a New Window
  6. Please do not post identical content multiple times in the forums. I've merged them: please delete the extra copies. Thanks.
  7. Or you could just use the Evernote Windows global shortcut key (default is Ctrl+Alt+N, I think, but it's configurable) to open a new Evernote note, and you just type in that note, and you'd get the exact same result.
  8. Since when? It does a Cut operation for me, as it should. Ctrl+Shift+X encrypts text, though. None that I know of. It would be nice.
  9. What "intermediate steps" are you referring to? The functionality is to move a note to a new notebook. They have put three recent notebooks at the top, which is A Nice Thing (though they should probably not include the notebook that the note is currently in), you can use the search magnifying glass to find other notebooks, or scroll through the list. What, precisely, do you want to see?
  10. Same answer, most likely: The Paragraph entry doesn't have an ID (there's no "Paragraph" command), only its children do, e.g. "Left" (= aligh left), "Right" (= "align right"), etc. Is this a problem?
  11. I don't understand what you are saying. Can you explain it better? Provide a screen cap? If you're talking about the search results once you've performed the query, they are always in the order specified by the sorting chosen by you for the current context, which, n the Windows application, can be different for different notebooks; there's also a global search order as well. If you're talking about search suggestions as you type, then that's what is unclear to me.
  12. Please read posts by @dcon / @dconnet to get a handle on why dark mode is difficult to implement on a Win32 application. Windows is not that same as Android...
  13. To make Evernote better. What's the point of your useless comment? Sorry I read your post -- you're back on 'Ignore'. Again.
  14. In Windows, Ctrl+Alt+N anywhere opens up a new Evernote note, type, type, type, you're done. Easy, and not any harder than what you suggested, plus it makes it easier to assign a notebook and tags right then, rather than having to figure it out later.
  15. I'm OK on disagreeing on this point (and don't want to belabor it further), but more importantly, I'd like to emphasize that from my side, we're all good now. To the stuff about an actual editing interface, just allowing you to do what could be done previously, i.e., add or remove individual items from a straight list would be sufficient. Really, you're looking for ways to remove actually misspelled items, since you can add new items via the standard note editor. Perhaps the UI could include a way to import a simple list in, as well; that would be handy. Beyond that, working in affix rules would be extra credit, and probably overkill for most Evernoters. And if they could automatically turn 'teh' into 'the', and 'Evernotoe' into 'Evernote' while I'm (mis)typing, that would be ok by me.
  16. Fair enough, and for the record, I also respect the work that you do in the forums: you help a lot of folks hereabouts and you often tackle stuff that I wouldn't. Sometimes communication gets a little sideways on the web, if if I misread your feelings as being more overwrought than were meant, then you have my apology as well. Sure, those are my words, and they stem from my experience in the software development field. To my mind, when you make software, there is -- or ought to be -- some form of understanding that some elements of an application are for use by the end-user, and some are not. The UI is an obvious case of what's clearly in the user area. Scripting languages, and the like, the same. Flip side: registry settings, undocumented files, the actual executable file(s), those are on the developer side. To me, there's an implied contract that the user keep to their side, where we'll do our best to maintain stability of UI and operation, and not muck with things on the developer's side, because the latter are apt to change. So a contract, not in the sense of something that's legally binding, but nor enforced, but something that gives some measure of guarantees to the user as to where it's safe to change things (user options or settings) and where it's not. If it's a gray area or not documented publicly, we can clear that up if asked. As a software user myself, I *want* to go through the app's UI to do things; I don't want to be poking around in the registry or external files unless it's absolutely necessary. The registry is a terrible end user UI, and will give you no information about what are good changes and what are potentially dangerous ones. Ditto for external files. Stuff on the developer side doesn't need to make sense to the end user; they need to make sense to the developer, because presumably, they're in position to understand what their intended use is. Some developers are happy to explain why changes are made, some not so much. In this case, it'd be "go ask Google", since it was their change. To me, the dictionary file was on the other side of the line; indeed the fact that it became essentially a binary format is a clue to how the developers viewed it, and that's probably why it was deemed to be OK to change. Maybe they didn't know, or never expected that users would hand-edit it. Or maybe that caused a problem somehow, and it was made binary to make it easier to keep prying fingers out. We don't know. It's unfortunate that it broke some user's workflow, and also if people lost their edits when the changeover happened, but it seems unlikely to get changed, so it's a case of "be careful what you tinker with" if it's not explicitly deemed appropriate by the developer. Or, in the old saying, "Caveat hackor"...
  17. Thanks, but the problem is that this is an Android-specific thread...
  18. Sure: That it was a simple text file was a fact, that it would remain one was an assumption. In Windows? Roger that.
  19. Oh yeah, missed this. So sometimes, when there's no contract about a particular artifact of a program (file format, registry entry, etc.) a developer will make changes that provide a prelude to making future changes, because there's no expectation that anyone outside will be consuming it directly. And maybe due to scheduling and prioritization issues, the actual changes/improvements aren't made right away (or at all). Them''s the breaks, because the program has already moved on, and the format is different, and it shouldn't affect anything except the program. People who make assumptions about artifacts of an application can be met with a rude surprise when things change. But there was no contract here. *shrug* But on the topic of pluralization, case endings,and other linguistic delights, here's a page that discusses the Chromium approach, or at lease serves as a starting point for how Google thinks about such things: https://www.chromium.org/developers/how-tos/editing-the-spell-checking-dictionaries. Interesting stuff.
  20. Assumptions ("hey, this is just a text file, I can just edit it myself") are easy to make, but not always warranted. It was an assumption on the part of certain users that the file format would never change, but there was never any contract between users and the developer about the file format. Reality bites, sometimes.
  21. The user dictionary -- or specifically, the list of user additions -- should absolutely be editable. The fact that you cannot make deletions is something that Evernote should provide, and if you want to know the answer, you should ask them rather than ranting (your word) about a file format change. In computers, there very often a distinction between a concept or abstraction (i.e., a user dictionary) and its representation (a text file on disk, a binary file, a group of registry entries, whatever). This is the case here. Evernote should provide the ability to edit the former, but is under no obligation (indeed, isn't even in control of) providing a user editable file that represents the user dictionary. See the difference? Just because the dictionary file representation was at directly editable at some time doesn't mean that there was any guarantee that it would be in the future, unless that's made explicit by the developer, which as far as I can tell, didn't happen. So the file on disk is evidently not meant to be user modifiable any more, for whatever reason (and your guess would be as good as mine as to why, though my experience tells me that such changes are usually done for a reason, and not at the capricious whim of some "goofball programmer"). If and until someone dives into the CEF change logs and figures out why the change was made (if that's even recorded there), all of the derision, fist shaking, etc. is coming from a place of lack of knowledge of certain facts. Maybe the changes were indeed made on whimsy, but nobody here actually knows that. So sure, people will go on mucking about under the hood with undocumented files, tweaking the registry, hacking the executable, etc. Fine. But there's no contract between the user and the developer that those things will work in the same way in future releases. It's fun and cool, and useful,to find hacks for things you want to change -- and I'm writing someone who spelunks the registry myself - but I know better than to have expectations about the future-proofedness of under the hood hacks. So hmmm, there is industry precedent for this sort of arrangement.
  22. Your wish is granted. In the Evernote Windows Application, you can right-click in a note, select "To-do", then "Uncheck All" to uncheck all checked todo checkboxes ina note
×
×
  • Create New...