Hi, I can't contribute to your particular problems, but have some remarks.
You said you "reverted" to 2.18. On Windows, you can easily run 3.x besides 2.x. Do you have the same problems with 2.18? If so, it's really your personal installation that fails, I think.
The node tool was redesigned in 3.x, and there is quite a discussion going on, cause not so many people like the new behaviour.
In general, I would like to say, that the promotion of the newest release shown in QGIS is quite a bad idea: The inexperienced will not hesitate to update and therefore run in every possible bug, being left clueless, while the more experienced are more cautious and install it only anlongside for testing purposes first.
The developers are in a bad situation: They need lots of testers to find bugs, but in my opinion they reach the wrong users with that advertisement. (no idea how to improve this)
Furthermore, the new version had a bad start, cause (as I understood) last-minute-changes in dependencies caught them unprepared.
Unfortunately, no one gives warnings about the major issues somewhere prominently e.g. on the QGIS.org website, so you have to read the mailing-list(s) and search in the issue queue yourself. In my opinion, in QGIS3 the developers were a little too ambitious, but it seems they also had kind of bad luck as well. Lots of features introduced are somewhat bleeding-edge and need time to ripe.
As I rarely use Windows, I'm not of big help. I just want to recommend you to use the network installer (advanced install!) and install the 2.x LTR and the 3.x LTR in parallel and update them through the installer once in a while, and keep 2.18 for productive work as long as you do not trust the 3.x version.
The open source mantra is "release early, release often", but that doesn't mean that everyone has to update early and often as well!
Cheers, Bernd Am 10.12.18 um 17:59 schrieb David Addy:
I have always loved QGIS and I have extolled its virtues to local historians and archaeologists in my area. I have had to keep quiet about it lately. I was somewhat relieved to hear a comment on a recent video of the Oceania meeting that QGIS 3.4.1 was a dud release as it caused Windows to crash at random moments. I had thought that all the long pauses, messages of QGIS not responding, and crashing when being closed down was some awful feature unique to my computer. I had even tried reverting to 2.18 for a while. However, after I upgraded to 3.4.2 I still had problems. Opening QGIS on Windows 10 can take over half a minute before anything happens apart from the outline box of the QGIS window full of blank space. Once a project finally loads up any random operation can still get the "QGIS not responding" message. This can result in further issues because I try pressing buttons to get a response. I even bought Anita's 4th edition of "Learn QGIS" to see if I was doing something radically wrong. It did highlight a few wrinkles until I got to page 55 when I discovered instructions on the edit node tool. This tool I had used OK in the past, but it now baffles me totally. I cannot get it to do what the book says. I am now losing my confidence in 3.4.2 and can only hope that the next point release will produce improvements. It would really help if known major issues like this could be posted here, perhaps as a sticky which stays at the top, to let users know that they are not alone with an issue. Sorry to complain. -- Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-User-f4125267.html _______________________________________________ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
_______________________________________________ Qgis-user mailing list Qgis-user@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
