Nicolas Goutte

It is available, but as you do not set it, it has a default value that is NIL. May be you can try something like: Procedure do_me (myH : HANDLE); BEGIN h := myH; TheUnitNumber := GetRField(h,'VG-Area Poly','unitnumber'); ForEachObject(process_storage,((NOTINDLVP & NOTINREFDLVP & (R IN ['VG-Area Poly']) & ('VG-Area Poly'.'polyclass'='Area-Storage')))); ForEachObject(process_balcony,((NOTINDLVP & NOTINREFDLVP & (R IN ['VG-Area Poly']) & ('VG-Area Poly'.'polyclass'='Area-Balcony Open')))); END;

You are not setting the variable "h" as defined by VAR h : HANDLE; in the main procedure. Procedure do_me (h : HANDLE); only sets "h" in that function. It is by chance the same name as the "h" variable of the main procedure but it is not the same variable.

Sure that could be. I have my Windows always with "User Access Control" set at the maximum. (I have tested on WIndows 10 1803)

See the documentation in http://developer.vectorworks.net/index.php/VS:vsoStateGetExitGroup (and perhaps the one in http://developer.vectorworks.net/index.php/VS:Parametric_State_Notifications ) As for the question how the path has changed, I think you have to do it by yourself, if it is relevant to you

Ok, too bad, I was not sure, but as you have waited since a few weeks I thought you should give a try.

Have you tried to use "Refresh Libraries"? Does it make any difference?

Are you sure you have the correct workspace for your serial number? Is the serial number correctly activated or if you need a dongle, is the dongle really attached and working?

I am not sure but I suppose that the installer makes the Library folder writable due to the library cache files.

I did a quick test in my Mac. I can create a file (from the command line, not from VW) in /Applications. However I cannot do the sampe in C:\Program Files on Windows. That is how both operating systems work. (Being an admin user on Windows, does not mean that unpriviledged programs like VW have admin rights to write files.)

The folder is probably write protected for a standard user.

Thank you

Well, we do see your signature and one part of it displays: "Interiorcad XS 2015"

macOS 10.13 is more picky on signatures of the installer (as every version of macOS in the last years has become more picky each time). Therefore an old installer might not work correctly. That is why I thought you might have luck by copying a complete installation. As for newer version of VW, they install fine on macOS 10.13 (I am currently writing this text from a Mac using macOS 10.13 😉 ). What I meant is that if the article was about VW 2017 and 2018, then the behavior of previous versions is undefined, which is mostly a bad sign.

That is very curious. However I have to call for others to help you, as I have no idea what might be further wrong here.

Then try to delete them again from that "NMAINY" file, save the file to another place (not in a special folder) and then without VW running, replace the old file by the new file in Explorer. Does it work better after that?

Ah OK, if I remember well, there was no caching at that time. I must have misunderstood your case.

Which VW version do you have?

I suppose that by "system folder" you mean where the VW has been installed (what I would call the program folder). In that case, in the resource browser, you have to use "Refresh Libraries", so that VW's caches are again synchronized. (VW does not assume that someone has changed the libraries in the program folder.)

Too bad. Unfortunately I have no idea for a work-around.

Your path should not start with / . A path starting with / means that it is absolute (The same with \ under Windows) As for your last example, I do not know if the space is allowed before } or if the space would count as if being part of the path.

I do know any, but it is not difficult, as the $INCLUDE notation does not change. You must just specify a relative path, instead of an absolute one. E.g., instead of using: {$INCLUDE c:\some\path\where\I\am\scripts\myscript.vss} just use: {$INCLUDE scripts\myscript.vss}

For point 2: have you tried relative paths for the includes? If you copy always the same folder onto each computer, then the relative paths should still always be the same, shouldn't they? (Sorry, I cannot help for point 1)

VW 2015 is pretty old for macOS 10.13. In the knowledge base, there is an article with compatibility problems for 2017 and 2018 (see below). If you have an installed version somewhere else, you might try to copy it. (It may work, it may not work.)

If you want to do it manually (or if you want to write a script for it), I think you must move the text as 3D move. (To avoid conflict with the texture of the extrude, you might have to move the text a bit farther up than the extrude thickness, additional 0.01 Millimeters or so.)