December 11, 201312 yr Is anyone else naming their layout elements, such as back and forward buttons, buttons to navigate records, search fields etc. If someone’s practise this, can they say what advantages it has and where they find it useful ultimately?
December 11, 201312 yr Naming in what way? Object name? Buttons don't need to be named because they are activated by the person clicking them. Object naming is handy when you want a script to go to an object. If you mean something else then I am sorry I did not understand. HTH
December 11, 201312 yr Author Yeap, object naming. I might have been overdoing it for no reason with them, that's why I asked the forum. And many thanks for your reply, I am starting to understand that aside from scripts there's little purpose to naming objects.
December 11, 201312 yr "aside from scripts there's little purpose to naming objects" There is no other purpose. But it's a very useful one! However, naming buttons is not all that useful, since unfortunately a button cannot pass its own object name as a parameter. What's most useful is naming: tab controls, web viewers, portals, and fields.
December 11, 201312 yr What Tom says. And GetLayoutObjectAttribute() can be used to glean information from the object. :-)
December 11, 201312 yr I am starting to understand that aside from scripts there's little purpose to naming objects. And don't forget the new FM13 "Refresh Object[name]" script step, which comes in very handy with the new invisibility...
December 11, 201312 yr Author yes that's a nice hack you can do with this, I was reading about it in one of the blogs.
Create an account or sign in to comment