Jump to content

Wux

Level 2
  • Content Count

    37
  • Joined

  • Last visited

Community Reputation

18 Neutral

About Wux

Profile Information

  • Subscription
    PLUS

Recent Profile Visitors

2,611 profile views
  1. Yes but with this we both are rather old school. I have my notes structured in a lot of thematically ordered notebook stacks / notebooks, so I do find my notes if I remember in which notebook they should be. And I have a tight tag structure, so I do find them through this also. But it is a nuisance. The kids from today, they just throw everything on a big heap and let Google Evernote do the search for them. Since computers have become quite good at searching this is a rather efficient method. Until somebody decides to break the search feature for good of course.
  2. Yes of course, this is the solution. You just have to allow to install apks from third party sites, where at this point Google urges you very strongly to reconsider, cause this is very often a very bad idea. And after this your have to switch off auto-updates for every app on your phone, which will also include not installing security relevant fixes, cause EN is not able to get its act together. Yes, that sounds about the right thing to do. For me the most incomprehensible thing with this bug BTW is for me not the bug itself - bugs can happen. It is not even that they did not revert to an earlier version, cause I really don't know about the intricacies of the Google App Store (if you look at the troubles with the actual Windows Beta of EN then sometimes there is more in the background going on then we know). No, if you look at the first post in this thread, then you will realize that EN knew about this bug through its voluntary beta-testers all along, and they released it anyway. This reminds me of MS, who were told bei their beta-testers that this Window release sometimes deletes all your data (which an OS really shouldn't do), and they too released it anyway. Somewhere in the management of EN somebody said "what the heck, we'll just release it, hardly nobody will notice". That our note-keeping app is unable to search for notes anymore.
  3. I have to agree too. They broke the search in a note keeping app and just don't seem to care that one of the most important features of such an app is now unusable.
  4. I think this may be releated to the "search not working anymore" since the last update, which is also not working for me anymore. I can select every other option for the list view of the widget (last shown, recently, notebook, reminder... sorry if not all options are correct, I use the german version of Evernote), and they all show a list of notes in the widget as they should. But if I select the "saved search" option, then none of my saved searches show up, I only get the very unhelpful message "list can not be shown, maybe there is a problem with your WLAN". Yes, surely. I didn't now that EN on Android is only to be used with WiFi... Yes, EN on Android does not get much love. But releasing an update ("dark mode is better", and I even like and use dark mode) which breaks search, which frankly is one of the most import features of a note keeping app, and (a) not repairing it or (b) rolling back the changes as quickly as possible baffles me.
  5. I think a LTS version would be a major pro-argument for using EN in the business market, not the other way round...
  6. I don't think that it is that easy: I believe minor releases are really only for fixing of severe bugs. For instance, the "special characters do not display correctly in the title" bug is still in all subsequent releases of 6.15 (up to now), but it should be fixed in 6.16. Which makes sense - all code changes, regardless of bug fixing or introducing new features, can also bring new bugs. So a GA will only get a new (sub-)release if the bug is severe, everything else is fixed in the next release. So the next major release really is more bug-free. But of cause the next major release is not only for bug-fixing but also implements new features, which will certainly bring innovative new bugs , so it is less bug-free... What EN lacks is an LTS (long time support) version, which would implement also minor bug fixes, but no new features...
  7. Now this undocumented feature is really nice, thx. ?
  8. Just tested it with 6.15.4 - still broken. At least with my example (Capital Sharp ß: ẞ)
  9. Small bug in the new templates feature (and of course I've stumbled over it with the first note ) Notes can only be saved as template, when the note is already synced, or else this menu item is greyed out. But if you have the auto-populate note with active tags option turned on AND you select a different notebook with this new note, then the "is it synced already" check does not work, you can click on "save as template" which leads to this rather strange very empty "save template" window: Frankly I think it would be a better solution, if there is no sync check, cause it leads to confusion, why sometimes "save as template" is greyed out and sometimes not. I think it would be better if EN would handle this the same way as the note link feature - force syncing, then open the "save as template" window, and the menu item is never greyed out.
  10. Templates seem to be turned on again this morning (local time: UTC +2). At least when I start a new note, there is a new "templates" button on top of the note.
  11. German Umlauts like Ä, Ö, Ü and lowercase ß are working fine, but the special new Capital sharp s: ẞ which (from Wikipedia) "was introduced as part of the Latin Extended Additional block in Unicode version 5.1 in 2008 (U+1E9E ẞ Latin capital letter sharp s)" does not render correctly in the title. In the snippet view on the left side it displays as it should - titel and text:
  12. No, this was the first version I did try after remaining at 6.7 for ages. This was the version after the bad sync bug, and the one that you brave beta testers told me was the first relative stable since 6.7. I am now at 6.14, and since the "cursor is anywhere" bug is resolved with this version, I will stay with it (which really drove me crazy in 6.13).
  13. I have crossed my fingers, installed the new EN version on my new notebook and upgraded the desktop vom 6.7. So far it seems most of the things are working. Yes, the PDF viewer ist ... a very limited piece of software, seems more like a design study. What also is lost is my user dictionary, so i have to redo all the spell checking. This seems to have occured in an update somewhere around february. A shame that this hasn't been fixed since. I also noticed that notes in English are heavily underlined - my default language is German, so practically all my notes are in German except some web clippings. But obviously there never was a language detection in EN, so it does not seem as a regression.
  14. The Wikipedia entry to CEF1 vs CEF3 shows that CEF1 is no longer supported - so EN had to upgrade sometime. CEF3 is multithreaded, while CEF1 is singlethreaded, so EN should be much faster ?. But I do understand that rewriting the code base to a multithreading model is heavy work, is likely to break a lot of things, and is a massive challenge to programmers used to singlethreading. It would have been better to be open about this change, tell people why this is necessary, and stop regular updates for half a year until a decent version is ready for GA. I do not think that anyone at EN wanted to break PDF workflows or thinks even remotely, that the feature-less version is better then the old one. But it seems they seriously underestemated the work needed for switching frameworks, so I guess it will be another few versions until all the functionality is back. I am far from an EN guru, and I do understand that you are angry. But I don't see how your rambling is improving anything, and I really don't like being told to not be allowed to say what I have to say.
  15. Before I install a new Version of EN I check this forum. For the last months I have read the postings with growing bewilderment, and decided to stay at 6.7 (I think this is the last version before the ugly New Note button). Now I have a new notebook – and since the feedback to 6.13 for the first time in months doesn’t seem horrible, I think I will give it a try. Thanks to all here who are more brave then me.
×
×
  • Create New...