stevenyhof Posted June 5, 2021 Share Posted June 5, 2021 Hello, Maybe someone can help me on this. I'm hoping I didn't break anything... https://www.loom.com/share/ae809a120e45408aac103b43353b9b2f Thank you, Steve Link to comment Share on other sites More sharing options...
stevenyhof Posted June 5, 2021 Author Share Posted June 5, 2021 It seems something might be wrong with the height as the width works. But when I look at the macro formatting it looks the same other than width vs depth Link to comment Share on other sites More sharing options...
stevenyhof Posted June 5, 2021 Author Share Posted June 5, 2021 Hmmm Now many are back showing valid Link to comment Share on other sites More sharing options...
stevenyhof Posted June 5, 2021 Author Share Posted June 5, 2021 I did not touch this, but noticed that FormatterDepthSixteenths and FormatterHeightSixteenths have the same code for obj.depth. So I did changed the FormatterHeightSixteenths to obj.height and now it gives me a valid number in the Expanded Macro Value field. Link to comment Share on other sites More sharing options...
stevenyhof Posted June 5, 2021 Author Share Posted June 5, 2021 And now it is working... Chief may want to look into this. Maybe Height and Depth give the same result, but something went wrong only by me making a copy of the formattedHeightSixteenths macro Link to comment Share on other sites More sharing options...
stevenyhof Posted June 5, 2021 Author Share Posted June 5, 2021 So I think I am all back to working again, but again, can anyone else verify that FormatterHeightSixteenths does in fact show obj.depth. I changed it to obj.height and now it is working. Link to comment Share on other sites More sharing options...
Joe_Carrick Posted June 5, 2021 Share Posted June 5, 2021 Steven, The first error was because you hadn't selected an object that had a width. Nil Class indicates that there's no object to evaluate. These macros supplied by Chief do not have "error handling" so they require that they reference only objects that have the attributes width or height. That can also cause an error to occur. When I create a macro I include "error handling" so that the macro will either: report why it failed --- example: No Object Selected to Evaluate or return simply a blank string or return a value of zero It depends on what the macro is supposed to do. I try to anticipate what the user needs to see in order to know what to return. 2 Link to comment Share on other sites More sharing options...
stevenyhof Posted June 5, 2021 Author Share Posted June 5, 2021 Here is a final update on what I did... https://www.loom.com/share/2583d3cb491c44c5b3f2016d66fb9d41 Link to comment Share on other sites More sharing options...
stevenyhof Posted June 5, 2021 Author Share Posted June 5, 2021 15 minutes ago, Joe_Carrick said: Steven, The first error was because you hadn't selected an object that had a width. Nil Class indicates that there's no object to evaluate. These macros supplied by Chief do not have "error handling" so they require that they reference only objects that have the attributes width or height. That can also cause an error to occur. When I create a macro I include "error handling" so that the macro will either: report why it failed --- example: No Object Selected to Evaluate or return simply a blank string or return a value of zero It depends on what the macro is supposed to do. I try to anticipate what the user needs to see in order to know what to return. Ah! I understand. Thank you 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