Jump to content

Nicolas Goutte

Member
  • Posts

    411
  • Joined

  • Last visited

Everything posted by Nicolas Goutte

  1. Yes, it is surely tricky. May-be users having migrated from AFP to SMB can give you tipps. (I can only re-iterate the theory... like a parrot. 😉)
  2. It has little to do with project or non-project VW files. The root problem is the different lock types between SMB and AFP. Of course, as you are supposed to share project-type VW files, the risk to have a real damage is higher. That is why the "one protocol only" way is recommended, for all VW files.
  3. If you want mixed environment, you have to use SMB as network protocol, as you should only use only one protocol (and Windows cannot do AFP). See what I had written and referenced in a previous thread. (Probably you can read that entire thread too)
  4. Then at least wait for the official go, which has not been given yet (as @Tamsin Slatter has already posted similarly in this thread):
  5. Would the list documented in http://developer.vectorworks.net/index.php/VS:InitXML be what you search?
  6. I suppose that Python is delivered as both 64 bit and 32 bit.
  7. For resetting the serial number, you have to contact your VW tech support with your serial number (do not post the serial number here).
  8. Polylines are indeed better... just be careful that a polyline can also contain Bézier and cubic... which not all CNC can handle.
  9. I have found a previous official answer by Tamsin Slatter on such a kind of question:
  10. If I remember well, just do not use that computer for a certain time (a day or so). If it does not work automatically, I suppose that you have to go through support to reset your serial number.
  11. Just to be picky: that is print from Python 2. In Python 3 you need parentheses: print(int("1") + 1) As for tutorials, I would start with the official one of the Python documentation (here the Python 3.5 version, as VW uses Python 3.5.2): https://docs.python.org/3.5/tutorial/index.html
  12. The post in the German forum I have quoted earlier gives this command line for checking the last available version /Applications/Vectorworks\ 2019/Vectorworks\ 2019\ Updater.app/Contents/MacOS/Vectorworks\ 2019\ Updater cli check
  13. That is the difference between Windows and macOS. Windows tries at great pain to keep compatibility to old software, macOS does not. (Also the 2017 hardware was surely not delivered natively with macOS 10.14.) As for the fact that this is "annoying", see other threads in this forum.
  14. Have you already tried out VW 2019 SP5.2. (There is supposed to be fixes for Nvidia GPU inside. May be it would fix your problem.)
  15. VW 2017 and older are not guaranteed to work on Mac OS 10.14. Only VW 2018 and higher were adapted.
  16. "many" perhaps, but dongles are not the standard installation anymore. But how can something be done on the VW side? VW cannot invent a dongle driver if the dongle supplier has not released its own version of the driver. (Except, of course, by changing installations from B to E serial numbers, like the current program for the German VW... for other reasons).
  17. If I remember well, a few years ago, I tried to get that translated name too... and I have not found a way. So, unfortunately, I am not the one who can help.
  18. Has the Plug-Ins a localized named at all? Tools, menus, objects have translations, but Plug-Ins? (At least in C++, I do not think that they have any.)
  19. Well, personally I did encrypt on Windows on VW 2019. (Yes, sure by VS call, not by VW directly) As for HFS/APFS difference, I have just thought of it because we were bitten by some differences just last week (on something else in VW's world, not encryption) Good question, indeed, to double-check if there would be still any error or warning
  20. OK, that leaves not many options left for you to have a quick workaround. I can only think of two possible ways you could try: - a Mac running an older macOS - a Mac running macOS 10.14 but on another filesystem (HFS versus APFS, of course case-insensitive, as VW does not work on case-sensitive file systems) Also, you might try to encrypt a brand-new VS. Does it work?
  21. The simplest solution would be probably to try to encrypt on Windows (if possible for you).
  22. That was for VW 2018 (where the switch to Unicode was done).
  23. It was the first idea I had when I have seen this thread. However I am not sure if it is need or not, if you do not encrypt per script (unlike we do). (That is why I have answered with such a delay.) As for documentation, see http://developer.vectorworks.net/index.php/VS:EncryptPlugin
×
×
  • Create New...