_c_

It has been said before and it is perfectly useless to say it again, but indeed variable declaration and handling, while less powerful, is clearly a no-brainer in Vectorscript Pascal, while in Python it is a major source of headaches. I can't begin even speaking of how much I miss Vector variables in Pascal. And yes, I am using vector classes in Python. Rant off. I'll get fit in this fast enough.

Ciao @PatW, the vs.py comes from one of the latest SDK. I don't think that the problem is in the None access, I think that there are underlying problems related to user interaction -or lack thereof. The whole trouble comes from vs.GetPt in some subtle way.

No, it is definitely weird. I do have it also in the normal VS editor. This causes errors: import vs def LinkIt(obj): recH = vs.GetParametricRecord(obj) if recH is not None: # uses words vs.AlrtDialog(vs.GetName(recH)) def Sub(pt): vs.ForEachObjectAtPoint(LinkIt, 0, 0, pt[0], pt[1], 5) h = vs.FSActLayer vs.GetPt( Sub ) While this does not: import vs def LinkIt(obj): recH = vs.GetParametricRecord(obj) if recH != None: # uses operators vs.AlrtDialog(vs.GetName(recH)) def Sub(pt): vs.ForEachObjectAtPoint(LinkIt, 0, 0, pt[0], pt[1], 5) h = vs.FSActLayer vs.GetPt( Sub ) But this never gives problems: import vs def test(h): if h is not None: # uses words vs.AlrtDialog('not NIL') h = vs.FSActLayer test(h)

The errors come up in VW, though. I have a lot of problems but perhaps it depends on what I am doing. I was silly enough to begin my belated catching up of Python from.... vs.GetPt.

I don't understand this. if I use in an external editor (Visual Studio Code, should that be relevant) this code I get bucketloads of errors: h = vs.GetCustomObjectPath( gPio_H ) if h is not None: .... While the same, expressed with operators, doesn't: h = vs.GetCustomObjectPath( gPio_H ) if h != None: .... But only in the external editor. In a doc script both forms possible without any problem. What could cause this? Please read the Python Programming recommendations: www.python.org/dev/peps/pep-0008/#programming-recommendations

I fixed it now

@twk I added a remark on dev, it is important for people to know it. https://developer.vectorworks.net/index.php/VS:GetLBHeaderTextWidth Is it you the user Tui? I credited to that user.

Ciao @twk, you got me curious, I can confirm that GetLBHeaderTextWidth doesn't crash on Mac under VW 2021. I have no access to win at the moment.

It's taken, it was really only a glitch. It is something affecting foreign scripters not using a querty keyboard. How many are we.

I filed now again a reminder. I filed this as bug in 2014 and called again and again for the solution, like some others.

Hello everybody, just to inform that now the List Browser article has been reworked and put on dev in my user space, since the thing is all but official. https://developer.vectorworks.net/index.php/User:CBM-c-/VS-List_Browsers_part_1 I would be thankful if one of the admins could delete the attachment in my previous post (under Orso's Avatar). I found out that the webarchive I saved is full of truly ugly links, the wiki had apparently been capered before being shut down. This also applies to the Wayback machine, and BTW, that most articles didn't save. @Pat Stanford, can you help there? Delete the zip here? Pat, I could still delete it as Orso, it's done! Thank you and happy new year everybody!

❤️

What a lovely place you gave us! Here Berlin, pretty much according to expectations. Dark. Cold. Winter.

Wow!

Thank you for all the infos.

John, the public release of Renderworks as built-in part - vs being a separate module - was one of the best decisions ever. A true added quality. I truly hope that we won't be left without RW.

Yes, will do, but not now...

@Helm, my previous post came in just as your previous one!

John, while these young ones are indeed not paid much, they are still paid. This is Germany, not Italy, where they even pay themselves, in some particularly bad cases. I do remember that long gone myself struggling to find a job in a country whose language I didn't speak and I had the disadvantage to come from an environment where there was no practicing habit. Italy. I wished indeed to be given that chance beforehand. As a rule I think that no trainee, ever, came under my teaching without experiencing warmth and the highest degree an respect. I do like them immensely. I had countless and baked countless sweets for them.

Hello Elepp, we have a system which doesn't require particular skills and certainly no dedicated person. I consider it highly efficient and scalable, given the circumstances. We use it for every project, from small to large.

Ah, LOL, how true is that!

And the archive policy. You can archive a drawing made of references old style and a layout, because you can cap references keeping the layers. That's the real publishing. But you cannot archive sensibly a whole project with layouts in the same file of the geometry because you are never able to restore the exact things you published, should you need it. By legal troubles you want that certainty.

As my old friend Petri used to say: Dialogs are bad interface I know, I know, I am being provocative here... ❤️

And the viewport obsolescence. This is unavoidable when a project grows and/or you have multiple persons working on it. You end up with tons of empty or senseless viewports. In environments where you have large turn over of trainees -usually on 6-months basis- it is impossible to keep house clean publishing in the same file where you work.

For the moment a number, if not all, of VW features is cut on the premise that everything is in 1 file there are few elements to be edited construction drawings can be derived from 3D Where we have larger projects requiring multiple files VW fails. Features such as Project Sharing Stories Drawing sync items (grids, labels, etc) Data Tags Resource sync real workgroup management (spilt damned preferences from libraries) etc... cannot be used any longer or with monstrous workarounds. Projects last years, not weeks, here. VW, do you really think that we can have all variants of renderings, permits, calculations etc. etc. in the same file, year after year of project growth? The level of detail of the shipped plug-ins is barely OK for very early planning phases. All of them. Otherwise, VW is very, very late in the plug-ins development and this is not to be caught up any longer. The solution to offload the problem on our shoulders in form of user defined 2D or 3D components, is, let me say it, making me rageful. If VW is targeting the small American praxis, as it seems to us (see lack of aknowledgement that we adopted the SI system some decades ago), then please tell us so once and for all. It might really be the point where we must adopt software more dedicated to the Architect and to our needs.