Standardize Font Appearance

Bob Sneidar bobsneidar at
Fri Sep 2 22:31:10 EDT 2022

Imagine right-clicking on the card, getting. Menu, field, button, grid, widget. Next level, named instance of a predefined class. Code drops the field then registers the object with the class object. Now the class object knows which objects to modify. 

Sent from my iPhone

> On Sep 2, 2022, at 19:27, Bob Sneidar <bobsneidar at> wrote:
> Like any other OOP system. By providing a way to instance an object from the class, and then modify the parameters if necessary. Not saying it wouldn’t take code. But the code would not be difficult to implement. 
> Sent from my iPhone
>>> On Sep 2, 2022, at 19:13, Richard Gaskin via use-livecode <use-livecode at> wrote:
>>> Bob Sneidar wrote:
>>> See, this is the exact reason why I would love to be able to employ
>>> an OOP style system. Simply changing the font, size and style of a
>>> few "Master Class" objects could change the entire project's look
>>> and feel in a matter of a second or two. As it is, it took me almost
>>> an entire day futzing around with fonts I liked, and then going to
>>> each and every object and making the changes there. Now I see
>>> immediately other font and style combinations I really like! Am I
>>> going to spend another day? Hell to the no! See just changing a font
>>> might not be enough. Often the size and lineheight have to be changed
>>> at the same time to get it to look proper.
>> How does this proposed system know which objects are bound to a style defined elsewhere and which ones aren't?
>> -- 
>> Richard Gaskin
>> Fourth World Systems
>> Software Design and Development for the Desktop, Mobile, and the Web
>> ____________________________________________________________________
>> Ambassador at      
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

More information about the use-livecode mailing list