SHCanada2

I just raise and lower the roofs, rebuild the trusses, until i get the desired heel height

...it used to remember ...if i am remembering correctly

that was it, i was looking for it in roofs given it was a manual roof, but it is as you show in walls merci buckets

Screen Recording 2026-09-25 000617.mp4 I can get rid of it by changing the eave width, but of course tha is not what I what. I also noticed the green right angle lines at the corner. I tried tab through to catch something else, and even turned all layers off excet roof planes, baselines, to ensure there was not another roof, but if I can change this roof and it comes and goes, i figure it must be related to this roof

hmm i was wondering that before I wrote it but I had checked mine that has two fields and they are both macros, and it works, but they come from rooms not notes...maybe its something along the lines of what joe said...interesting

they have a demo and Q&A next Thursday. I will ask the questions if i get the chance

did the "group similar rows" not work to get rid of the same null blank rows in the schedule

the offer was good for the rest of the year. Given I could not find any feedback, well that and its like $2k CAD, I decided to wait to see what people reviews are...and real people in the industry, not just some reviewer guy. So hopefully you will provide some valuable feedback. My biggest concern with all of these things that "make a floor plan" is they never seem to tell you what they adjusted to make it work. Given their stated accuracy is +- 1 inch, I dont want a bathroom shrinking an inch when they put it altogether. think most of these types of program make the walls thicker for the most part. but still, why not give me the raw measurements as well wo i can decide. I guarantee you a bathtub cant shrink by an inch

the other thing you could do, which I did originally for RSI calcs is put everything in one note for a single row schedule for each category. Given you want control and not have the user accidentally remove a row or have to do row management and looking at your example formatting, it might be an option:

you can consoliate similar rows into one(not zero) row, thats how room area schedules can be made to look like only a couple rows, but it would only work if your other rows have unique atributes

..another reason for the user to create a pdf from the downloaded excel, import into CA plan file....simple no headache or just screenshot the excel file, even easier (but loss of pixel accuracy) ..or the user can format excel and print to pdf ...or the user can create a "view" in excel to replicate the same thing every time ....or ... if the data is static and does not change and the format as viewed in CA does not need to change, I dunno, why bother bringing it in as numbers into CA.

I got a notice today for option to buy for a $100 discount on $1500, not exactly a lot. They do have the doc up and some videos on how to use. They also specify accuracy as +-1 inch ...per room it looks like. not great once you aggregate it all together. It also looks like it creates the floor plan as you go, which means it has the same type of logic as the apple room API. i.e it has to choose what walls to change the measured value on in order to close the room. It has an odd room transition. They recommend to,, hit the add room button on the app, then put the LX on the jamb to measure the wall thickness. ...and how exactly would that work? the casing is typically almost flush, which would mean, if it included the casing, they would calculate the wall to be another 1.5" thick. There must be something going on to mitigate this I also never saw in the video where they size a window that is flush with the wall. I would think maybe you just put it on either side of the window. ...and it does not show measuring a closet with a bunch on clothes in it. The one video I saw the guy says if it cannot get a laser reading it uses the gyro. it would be interesting to see a real life scenario with a third party reviewer. I looked around but have not seen one yet

oh the other thing to add, if you are using global variables to store the data, be careful as opening up two different plan files at the same time will execute the same. I use a global hash which includes the path/name of the .plan file for every NVP in the hash, in an attempt to mitigate this. ie. in order to show the contents of the variable, I check that it matches the current plan file name in the current active window. If you are doing it on the fly and returning data directly from a function, then not an issue

hmmm I dont think it would work in the restoring a backup or simply opening up a backup(which in this scenario is stored in the same dir), as the macro always reads the latest JSON, no? Or Consider the case where I create two different floor plan options in the same directory, if it always reads the latest, then both would show the same when I open them up, even though they should be different. to each his own, but I would see the tradeoff of that risk, vs simply creating a PDF of your XLSX (assuming it is pretty), and importing, as the least risk, easiest to manage, guaranteed accurate for backups & multiple option plan scenarios. hmmm, I thought the rb just brought the data into variables, and the CA text box with its grid lines is presenting that data(font, size, bold, etc).i.e. the RB would be more of an ETL process, where it extracts the data from the JSON, transforms it into the format you would like, and then loads it into variables. I suppose if you are adding tabs or the like as part of that to make it look pretty, then I suppose it is a bit of a mix never a dull moment in the CA automation topics...

ok so I think I am getting it....maybe... You are forcing the user to use a specific backup mechanism, where they must copy your .plan file and the JSON file into a separate directory when they make a backup? vs for instance in non PM mode I would make a back up or create a new version of the plan simply by copy and pasting the plan in the same directory or what exactly does this mean. Is this done by what the user downloads (MSI or something)? uhmm you are actually doing two formats? xlsx and JSON I dunno, copying around 2 files, requiring specific backup directories from the user, writing macros to read(which may impact performance), making sure the right .plan is linked, vs creating a specific JSON file for CA that the user just imports, presumably same as the workflow for the revit and softplan people...seems like a headache, not to mention the user has to maintain the links to your plan file. You might even want to ask your customers the question: If we had a standlaone utilitity to change the JSON file to a CA JSON file, would you rather run it through that and import the CA JSON file, or would you rather this setup where there is a seperate .plan file you have to link and maintain the JSON and .plan file. In my view of the world, which I will admit is far from the average person, I would pick the utility and keep with one .plan file. but and there is always a but, the CA macro import just brings in the text, you have a lot of grid lines. If these are just text boxes with lines, then the user would need to create those. If I was your company and went the CA JSON file route, I would then provide the example .plan file with those boxes and the text macro names and then the person could just put those on their own template file. BTW, the new feature of the "Project Information" where you can create your own fields, is exactly the same as the existing text macro functionality with respect to behaviour to read from them. The Project Information features implements a nice GUI to enter the data, vs the text macro which (if not imported from a JSON) needs to be entered via TMM. or...if your XLSX is already formatted pretty, the user could just make a pdf of that and import to their plan file. one and done