![]() ![]() Now I may need to change the "shortcut" combination to something even more difficult to remember as i've already memorized it and sometimes accidentally use the undo-command without stopping everything to conduct proper "cost-benefit analysis".įortunately I've been lucky the last few times I used that command and it actually did what it was supposed to rather than wipe out every single thing I've worked on. I know that's an incredibly archaic method no one using any CAD software developed since the early 80's should have to resort to but it seems to have worked. Anything to avoid initiating an undo command. In disabling the default shortcut it would force me to stop for a moment and ask myself "is it really worth the risk?" and consider just deleting what I worked on in the last few steps and repeating the work again. One thing I did when having frequent recurrences of this problem in VW2017 was to change the default shortcut for undo to the most complicated combination of keys possible so I wouldn't use that command by habit and inadvertently lose absolutely everything I worked on since last opening the file. Sounds like maybe we should stick with VW2017. VW2018 has been installed on our workstations but most of us have not started using it yet. I was hoping at the very least an upgrade to VW2018 would resolve this once and for all. It is very discouraging to hear this problem is still recurring. I wonder if anyone at vectorworks is listening? For me VWA2018 is the buggiest release ever. This is on a new file started in VWA2018, as well as files updated from VWA2017.įrustrating. I can't work for more than three-four hours without it happening. Restarting the computer helps for a short while, then the behaviour happens again. If it doesn't work after a save I have to move the selected object - then the OIP shows the object, but of course I have to move the object back to its original position.Īnd if I use the undo command to move it back in position then I might get the behaviour that you mentioned earlier, that it jumps back to a random post in the undo history. It shows no info until I save, then it often shows the info on the object. ![]() Yes the Object Info palette does the same for me. VW2018 SP2.the issues still continue with:ġ) the undo command that freezes for a second and then jumps back performing the entire undo historyĢ) the OIP palette stops showing any info for a selected object be it a wall, polygon or door symbol. ![]() I have performed a preferences reset as above on a student's computer two days ago in our previous class and the problem has reoccured today. I can't as yet replicate the problem on my own machines but I would love to know if anyone has some preventive ideas. Restarting the program has fixed it in the past but it's almost guaranteed to reoccur on the computer later in the lesson seemingly unpredictably. Once the issue has occurred it seems to lock the Command + Z to always perform this mass undo. All using either VW2016 SP2 or SP3 on MacBook laptops of various ages and specs. I've had this occur on 3 of 16 student's computers over the last month. Holding the action causes the menu to flash as though the command is being executed but nothing actually occurs. Although the Redo option is available it does nothing. The issue is worst than just a potential 50 undo actions. It seems that something (unknown) causes a single press of Command + Z to change from a single instance undo to performing the entire undo history. MONGO_INITDB_ROOT_PASSWORD = enter your decided password.I can confirm that this issue is currently still actively happening for a select few of my students. If you are lazy enough to write sudo every time then use sudo -s once and you no longer require sudo in all commands.Ĭhange following values immediately, other values you can change as per requirement. Sudo unzip sra-vectr-runtime-7.1.1-ce.zip Let's create the directory and traverse to that for further steps mkdir -p /opt/vectr sudo systemctl enable dockerĪs per the official guide, we will install VECTR in /opt/vectr directory Now as the version is satisfactory, we will enable docker. Now verify docker-compose version: docker-compose -version Run below: sudo curl -L "$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-composeĪllocate permissions to docker-compose by: sudo chmod +x /usr/local/bin/docker-compose **Now we will be installing the latest docker-compose. When the above is completed, run apt update once again. Now let's grab docker-ce, docker-ce-cli, containerd.io and unzip. Let's start installing dependencies one by one. If you have used apt to install docker-compose then it would have grabbed a very old version with bugs. These can be installed via apt but be careful with docker-compose. We would require docker-ce, docker-ce-cli, containerd.io, docker-compose, and unzip.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |