David Poiron Posted June 2, 2019 Share Posted June 2, 2019 Is there a way to restrict the function GetSpaceNameForObj to only one layer? I'm trying to capture the room names on either side of a wall for a door schedule but it seems to be adding some space objects from layers where the door does not exist. Quote Link to comment
Pat Stanford Posted June 3, 2019 Share Posted June 3, 2019 Edit the criteria you pass so that it is also limited to a layer? =GetSpaceNameForObj(((L='Your Layer Name') & (T=DOOR))) [The above is from memory and not guaranteed to be correct. Use Insert Criteria function to get the proper criteria you need] Quote Link to comment
David Poiron Posted June 3, 2019 Author Share Posted June 3, 2019 I forgot to specify this is in a database header and not a spreadsheet. The object being found is a door so it would not need the T=door criteria. If I add the layer criteria VW hangs (beachball). I don't think the search criteria is meant for the database header as the header already has its own criteria. Unfortunately the GetSpaceNameForObj does not seem to adhere to this for the space names it finds. Quote Link to comment
Pat Stanford Posted June 3, 2019 Share Posted June 3, 2019 What about putting the layer in the Database Header and then just using GetSpaceNameforObj() without any criteria in the column formula. It should inherit the criteria from the database. Quote Link to comment
David Poiron Posted June 3, 2019 Author Share Posted June 3, 2019 I have done this but it still seems to be finding other phantom spaces. We will keep looking to see if these really exist. Quote Link to comment
Pat Stanford Posted June 3, 2019 Share Posted June 3, 2019 Worksheets find instances on both Design Layers and in Viewports on Sheet Layers. Try limiting it to just a single design layer. Unless you have Design Layer Viewports on that layer in which case you will have duplicates. Quote Link to comment
JMR Posted June 5, 2019 Share Posted June 5, 2019 @David Poiron Have you checked that your spaces are not overlapping in the Z direction? That could cause doors being listed in additional spaces. Spaces can have height, and they can have individual elevations, too. Quote Link to comment
David Poiron Posted June 5, 2019 Author Share Posted June 5, 2019 The project is a one storey building and none of the space objects have a Z height. Some doors show the expected spaces and also "Room" or "Corridor". Some show duplicates of the Room name in a slightly different format (possibly from older versions) but I cannot find them, even with all layers and classes turned on. I've tried custom selection without success. Not sure what to do at this point. Quote Link to comment
Pat Stanford Posted June 5, 2019 Share Posted June 5, 2019 Can you post the file or share it privately so we can take a look? Or even a demo of just part of the file showing the problem? Quote Link to comment
David Poiron Posted June 5, 2019 Author Share Posted June 5, 2019 Well, I am not sure how to share privately. However, I have "solved" the problem. I deleted half my layers and recalculated the worksheet and the problem went away. So I took another version of the file and started to delete the layers one by one and found the offending layer. First I deleted the layer and the problem went away. Then I undid the layer deletion and instead deleted all the the objects on that later(none of which were space objects), and the problem persisted. Then I deleted the layer and recalculated and the problem went away. Some random layer was the problem why a worksheet was incorrectly finding space objects. 6 hours to solve this one. We are having a real hard time with VW2019. There are so many glitches. I've been using this software since 1993 - however my new employees think VW is garbage. Quote Link to comment
Pat Stanford Posted June 5, 2019 Share Posted June 5, 2019 If you still have a copy of the file with the problem, click the Bug Submit link under the Community header at the bottom of this page and submit a bug. Ask them to send you an upload link to send them the file. That is the best way to help make VW less "garbage". By the way, almost all software is garbage in most peoples opinion. Read any software forum and they all sound similar to what gets posted here. Quote Link to comment
David Poiron Posted June 5, 2019 Author Share Posted June 5, 2019 I will be submitting it. I would not have spent so much time to solve the issue if I did not care about using VW as I do want to see it improve. I fear at this point, however, it is starting to collapse under its own weight. I honestly don't know-how a program with 1000+ tools and commands keeps functional at all. I think trying to be all things to all people may have finally had its day. Thanks for your help - it is appreciated. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.