Too Familiar with Revit

Have you found that you are too familiar with Revit now to see all the little things holding you back in the program?

You have done it this way for years now, know the work arounds and the limitations. To quote the 6 Phases of Revit, "You "know" what Revit "likes", and what it "dislikes"" After Rod Howarth's post with the Revit API tic-tac-toe, I have started working on making a Revit Family version in the evenings. I am not new to formula driven families so I thought this would be fun. Click here for a 42 page formula guide.

Instead, this challenge brought to light a whole host of deficiencies because I was trying to design the simplest interface for the game. The key to a complex program is a simple UI and that is the same with a family. Give a user a complex door family with 50 parameters that they can change and they will be crippled not knowing even where to start. Simplify that down to 6 to 12 well named and understandable parameters and they will use it without question.

So, I would start with an input parameter, chose an X or O for a particular box. The first thought would be to just use a text parameter and fill in X or O for each grid box.

Problem - One cannot drive a yes/no parameter from a text parameter and one needs two yes/no parameters to drive the visibility of the X and O. In fact, I do not believe one can drive any parameter type from text and I don't know how it got into our AU handout. This is a huge deficiency that I have come to overlook in Revit. When setting up files for others, if they need text in their schedule but also need to drive visibility, I create two parameters. We find this issue a lot, for example one has a piece of equipment with an optional piece attached to it. You want to catch it in the schedule but you don't want the endless yes, no, no, yes, no, no, no in the schedule. So one has their yes/no parameter to control visibility and ease of selection but then another text parameter that fills out for the schedule. If(YesNo Param, "X", "") I have even done this with bullets on some projects and not the X. While you may say, "see it works fine by just clicking on the yes/no" but the bigger issue comes when red lines are being picked up on a project. You now need two schedules, one with the yes/no parameters and another with the text parameters that goes on a sheet. My wish, is that in the appearance section of the schedule, one would be able to specify what a yes displays as and what a no displays as AND/OR that you could use text parameters in formulas. In the case of tic-tac-toe, it is more than just the one to one relationship between a text and Yes/No parameter since in a perfect world the text parameter would be able to influence two or more Yes/No parameters.

I have numerous other examples for use cases of text parameters influencing other parameters if someone from Autodesk needs examples of how we would actually use access to the text parameters in formulas. It seems like a huge overlook since even the software that the programmers are using typically can utilize text inputs and numerous other programs. There are other formula deficiencies but this post ended up longer than expected so I will cover it next week.

If you have a use case, send me an email or leave a comment.  I will compile a list/report and send it on to Autodesk to see if there is something we can do about this.