Jump to content

David Poiron

Member
  • Posts

    203
  • Joined

  • Last visited

Everything posted by David Poiron

  1. Thanks Matt - this will help!
  2. It appears that the catalog entries for IKEA cabinets do not include proper textures - the all show a grey Axstad texture, no matter which cabinet style I select. Is there a plan to include the proper textures, or is this up to the user at this point?
  3. I've ended up creating a 3D object with a slit in it and cutting copies of the original object (solid subtractions) and then reassembling the cut pieces back into the original shape.
  4. Is there a way to easily split 3D objects into slices of consistent width, like in this image. I thought there was a video regarding this but I cannot seem to find it.
  5. Actually, it has been working but the text was hidden under the image, which made me think initially it was not working. Now if I can figure out if there is a way to have the image top anchored, and have the text under it move down with a variable height image, I will be happy. I'm not sure if this is possible - cannot get the constraints to work this way it seems.
  6. I am working on graphic legends for walls, slabs and roofs. I am using the "Manufacturer" field as a kind of note field. I can reference this field from a text block in my graphic legend for walls, but when I try to do this for slabs or roofs it does not seem to return anything. This is the code used for slabs for example: #IfcSlab#.#Pset_ManufacturerTypeInformation#.#Manufacturer# Is this a bug?
  7. Is there a way to distinguish a slab being used as a floor versus one being used as a roof in a graphics legend? I tried using "name" and "starts with", but this does not work. It would also be nice to be able to refer to the fields inside a slab, roof or wall object in a graphic legend - maybe this is possible but I cannot seem to get it to work. Another related item: is there a way to access the IsExternal (exterior) criteria? This would allow us to easily have different graphics legends for interior vs exterior assemblies.
  8. I have established an ODBC connection to a FileMaker database but all my fields are greyed, preventing me from selecting a key. Does anyone know why this would be the case?
  9. Good to hear changes are coming. If possible, it would be nice if wrappings could be set to face of window or door frame, so that if the offset of the window or door is changed the wrappings would adjust accordingly.
  10. I have a window sill on a window and it graphically covers the wrapping of the interior gypsum board return in plan. Is there a way to bring the wrapping to the front? Also, there is a gap between the stool and the sill that I cannot get rid of (in 3D). Any ideas to fix these issues? Also, if and when the sill on the window tool is fixed, the stool has to get extended to the inside face of the window, not stop at the inside face of the wall.
  11. Pat, This is the answer I was looking for - worked like a charm. Thanks as usual for your help! (Thanks Nikolay for you offer as welll) David.
  12. Sorry if this topic is in the wrong place but it might relate to data tags too so here goes: I'm trying to parse out words that are part of a symbol name for a graphic legend field (text). The symbol name is made up of a reference (ex.L12) and a description (ex. recessed lighting), for an overall name of 'L12 recessed lighting'. I thought it might be possible to use the worksheet SubString function to, for example, get the first word - #WS_SUBSTRING(#SYMBOL#, ' ', 1)#, but this does not work. Can anyone help with this task - or maybe it is not possible?
  13. It would be nice to have a checkbox that allows for the curb to be located outside the defining shape instead of inside. Currently, I have to size the shape and then add an mount for the width of the curb to push the curb out to where I want it to be.
  14. Thanks Nikolay - this, as convoluted as it is, works! Much appreciated.
  15. I've been trying to add the word "note:" to a field in a slab "data tag" (in a graphic legend) before the field content and have been unsuccessful What I want to do is check if field is blank, and if it is not, add the word "note: " before the field in the data tag. I've been using <Value if True>@<The Condition>:<Value if False> format (I wish a normal If statement worked in data tags). Here is my code: Note:#IfcSlab#.#Pset_ManufacturerTypeInformation#.#Manufacturer#@(#IfcSlab#.#Pset_ManufacturerTypeInformation#.#Manufacturer#<>''):'' I cannot get the "Note:" part to append to the field information only if it is not blank. I've tried using concat and a number of other methods but nothing seems to work. Is this possible? I wish data tags had proper quoted strings and operands instead floating text where it is unclear what it is doing or how it interacts with field data. I would also like to see some user defined fields in data tags in graphic legend to allow for a user defined field, like in regular data tags. I know a user can add an annotation but it isn't the same work flow.
  16. We are currently using the following code for data tags to list out the components of wall, roof or slab styles in a data tag: #WS_COMPONENTNAME(1)# ... [insert intermediate values here!] #WS_COMPONENTNAME(16)# The problem with this method is that it has a bunch of blank spaces at the end, depending on the actual number of components. We are trying to use the new graphic legends, and this makes all the cells in the new graphic legends for this purpose the same height because of the fixed number of possible components. What we would like is a function to list the component names of all actual components, which would create a variable height list (depending on how many components). This would alleviate the extra space and the graphic legend height issue. Maybe there is a way to do this now in 2023 that I am unaware of.
  17. I have used this method for a while now, and am wondering if there is a way to have the sheet number become a hyperlink to the title block (the sheet layer it is on) itself in a PDF.
  18. We think we have figured out the problem. The replace IFC checkbox was not activated when replacing the wall upon exiting the wall styles.
  19. I am trying to get the acoustic rating of a wall object to show up in a data tag using #IfcWallStandardCase#.#Pset_WallCommon#.#AcousticRating# but it does not seem to work. Tagging other fields from the wall seem to be fine. Has anyone else seen this problem?
  20. The script runs fine on symbol definitions with the appropriate record format attached - I am changing the value of the fields in the record format using SetRField. The problem is for symbols that are within the symbol definition. For example, I have symbol A by itself and the record format updates fine. But if the same symbol definition A is inside another symbol (say symbol definition B), the version of symbol A inside symbol B will not update. I would have thought that ForEachObjectInList(SetFieldsSD,0,2,FSymDef); would traverse the symbol B to get to symbol A. This is SetFieldSD FUNCTION SetFieldsSD(h :HANDLE) :BOOLEAN; {set symbol fields for objects} BEGIN IF (GetRField(h, cpaRF, cpaRF4) = RF4) THEN BEGIN {for symbols with correct serial record field} SetRField(h, cpaRF, cpaRF1, RF1); SetRField(h, cpaRF, cpaRF2, RF2); SetRField(h, cpaRF, cpaRF3, RF3); END; {If} END; {SetFieldsSD} Thanks Pat.
  21. I have a script where I am am trying to change record format values of a symbol that is inside a symbol definition but I cannot seem to get a handle on it (pun intended). I was using the following to traverse the symbol definition list: ForEachObjectInList(SetFieldsSD,0,2,FSymDef); I thought this would do a deep traversal but it does not seem to do that in this case. This works for individual symbols with the record format attached, but not those that are within another symbol definition. The parent symbol definitions are of the "blue" type (symbol to group). Anyone have any tips that can get me to the nested symbol?
  22. Pat and Andy, Thanks for going further with this. By adding 'symbol' to the visualization criteria (and removing wall and solids as they are not necessary) and making sure that objects inside the symbol do not have the record format attached (it is attached at the symbol level), data visualization does indeed work! I think this may be enough for what I need at the moment. Have more granular control over objects inside the system at some point would be great. Pat, I am curious about the file you mentioned with your worksheet but I did not see it attached. Can you repost?
×
×
  • Create New...