kMoquin Posted May 5, 2014 Share Posted May 5, 2014 Does anyone know if there is a setting to show dimensions in a door or window schedule in feet and inches instead of inches only? (I cant seem to locate it...) thanks! Link to comment Share on other sites More sharing options...
Joe_Carrick Posted May 5, 2014 Share Posted May 5, 2014 No, there isn't any way to do that currently. The easiest way would be if Chief would provide alternate columns formatted for us. It might be possible by adding columns that could be filled in with macros - I would have to study that. My Schedules are set up with 3 additional columns (Head, Jamb & Sill Detail Reference) so I know we can add components and get extra columns but the component fields would need to be able to utilize a macro to display the values. Link to comment Share on other sites More sharing options...
Rectangle Posted September 4, 2014 Share Posted September 4, 2014 This seems like a pretty simple function/ feature that they should definitely support in an update to the program. I hope they are working on a way to do this, as Feet and Inches is used much more easily than Inches only. Link to comment Share on other sites More sharing options...
GerryT Posted September 4, 2014 Share Posted September 4, 2014 Two - Three ways to do this automatically One --- Add a sub-column to replace the width or height columns. Write a macro to enter the door width/height info into global memory. Make a second macro & put in sub_column to retrieve from global and write to the component sub-column. Add the sub column to the schedule. Two macros per door. Remember to use Caps. Two - Add the door accessor methods to global then a second macro to retrieve. Then same as above. Three -- IOW -- Just copy the dims into a sub-column manually. Link to comment Share on other sites More sharing options...
lbuttery Posted September 5, 2014 Share Posted September 5, 2014 Gerry: even though I advocate for macros I think functions like this should be controlled via a setting in a DBX I hope Chief never gets to the point where "everything" needs to be done via a macro on the other hand, if I chose to I should be able to do "anything" via a macro Lew Link to comment Share on other sites More sharing options...
GerryT Posted September 5, 2014 Share Posted September 5, 2014 Good Point -- Mine also. The real purpose of macros is to allow the user to customize the process to the way it's comfortable with, without tying up programmers with endless requests -- which never end and never satisfy anyone. Any attempt to do so just creates a cumbersome mishmash, to puzzling for anyone to use in the end. Chief has so limited Ruby, that it serves no real advantage, which was what I was trying to point out-badly. Does not have to be that way. Tremendous waste just to save a few programming man-hours. Link to comment Share on other sites More sharing options...
Doug_Park Posted September 5, 2014 Share Posted September 5, 2014 Keep asking for expansion of our internal API. I am a big proponent of adding at least enough functionality to iterate through objects and have the ability to set the exposed properties of them. The API already has the power to set items and is exposed via select same / load same. The only bit that is missing is the ability to access items via some sort of iteration. The possibilities with an expanded API are vast. And I agree with Lew, we should make it easy to do the common things without macros. Link to comment Share on other sites More sharing options...
lahirudmki Posted February 13, 2022 Share Posted February 13, 2022 how to show schedule dimension feet Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now