Thread: Re: [ocemp-devel] newbie question about varying the appearance of different instances of the same wi
Status: Beta
Brought to you by:
marcusva
From: Marcus v. A. <ma...@sy...> - 2005-12-28 21:15:03
|
On, Wed Dec 28, 2005, Laura Creighton wrote: >=20 > I have been playing with ocempGui for a few hours now. Thank you. > I would currently like to build a table of buttons, but with each > button a different colour. Actually, I want a button that can=20 > receive a message 'change your colour to this' and 'flash your > colour between this one and your current colour'. >=20 > Do I need to write my own class that inherits from 'Button'? What I > have been trying now only makes _all_ the buttons change colour. > Just wanted to ask in case I am missing something obvious. No you do not. Use the get_style() method of the button(s) to create instance specific styles for them and modify those: # Create an instance specific style. button.get_style() # Set a red background color for the normal state. button.style["bgcolor"][STATE_NORMAL] =3D (255, 0, 0) More details can be found in the style and theme examples and the manual, which ships with the OcempGUI package and should be installed under /usr/share/doc/ocempgui on your Debian system. You can find it online at http://ocemp.sourceforge.net/guidoc.html, too. Regards Marcus |
From: Ben O. <bo...@ve...> - 2006-01-03 17:07:13
|
Maybe other people will have feedback on this too, but this reminds me of something I don't like about the style system. It's nothing big, but the term "get_style" is not very intuitive for what the function is doing. In my mind, if I call a function like "get_style" I would expect it to return a style object that I could apply somewhere. Instead, this function creates an instance-specific style for use only on that object. I like the way it works, only I think the term "get_style" itself is misleading, and probably causes confusion for people trying to learn the style system. Perhaps a better term would be "create_style" or "unique_style". Ben > -----Original Message----- > From: oce...@li... [mailto:ocemp-devel- > ad...@li...] On Behalf Of Marcus von Appen > Sent: Wednesday, December 28, 2005 2:14 PM > To: Ocemp-devel > Subject: Re: [ocemp-devel] newbie question about varying the appearance of > different instances of the same widget >=20 > On, Wed Dec 28, 2005, Laura Creighton wrote: >=20 > > > > I have been playing with ocempGui for a few hours now. Thank you. > > I would currently like to build a table of buttons, but with each > > button a different colour. Actually, I want a button that can > > receive a message 'change your colour to this' and 'flash your > > colour between this one and your current colour'. > > > > Do I need to write my own class that inherits from 'Button'? What I > > have been trying now only makes _all_ the buttons change colour. > > Just wanted to ask in case I am missing something obvious. >=20 > No you do not. Use the get_style() method of the button(s) to create > instance specific styles for them and modify those: >=20 > # Create an instance specific style. > button.get_style() >=20 > # Set a red background color for the normal state. > button.style["bgcolor"][STATE_NORMAL] =3D (255, 0, 0) >=20 > More details can be found in the style and theme examples and the > manual, which ships with the OcempGUI package and should be installed > under /usr/share/doc/ocempgui on your Debian system. You can find it > online at http://ocemp.sourceforge.net/guidoc.html, too. >=20 > Regards > Marcus |
From: Marcus v. A. <ma...@sy...> - 2006-01-03 19:22:55
|
On, Tue Jan 03, 2006, Benjamin Olsen wrote: > Maybe other people will have feedback on this too, but this reminds me > of something I don't like about the style system. It's nothing big, but > the term "get_style" is not very intuitive for what the function is > doing. In my mind, if I call a function like "get_style" I would expect > it to return a style object that I could apply somewhere. Instead, this > function creates an instance-specific style for use only on that object. >=20 > I like the way it works, only I think the term "get_style" itself is > misleading, and probably causes confusion for people trying to learn the > style system. Perhaps a better term would be "create_style" or > "unique_style". >=20 Agreed. I'll change that name in 0.2.0 and keep get_style() as deprecated method until it will expire. Regards Marcus |