Robert, Thanks for your quick response. I tried "Appearance Parade" but I am getting errors. Error: A Variable was expected here??? in file Temp Project at line 204 in BUILDWND *err = Fn SetControlData (progBarH,_kControlIndicatorPart,_"inde",0,*0 ) '~' Error: Register variables can't be used in this statement... Use DIM @ var to force the compiler to assign it in memory. in file Temp Project at line 204 in BUILDWND **err = Fn SetControlData (progBarH,_kControlIndicatorPart,_"inde",0,0 ) '~' Error: Expected an end ')' here... Example: Too many parameters, or mismatched (). in file Temp Project at line 204 in BUILDWND *err = Fn SetControlData (progBarH,_kControlIndicatorPart,_"inde",0,*0 ) '~' Having looked at the code, it has some good examples, if only I can get it to work. Any suggestions. TIA David Parrish >>My software uses the Rntm FBII.Incl header. Can I use these >>Appearance Buttons without changing my whole program (15+ incls & >>fltrs)? Is it just a matter of adding INCLUDE "Tlbx >>Appearance.Incl" or other Headers to the program? >> >>Can I just add the needed reference codes in an Incl file? >> >>Thanks for any help and guidance you can offer. >> >>David Parrish > >The Appearance Gurus will know more, but as far as I know, you can >do that...just add that include. Some appearance options however >will be unavailable to you, and I myself don't know what they are. >But Ken and Steven among others used to put out a -lot- of examples >here using Standard runtime and appearance mangler. > >See "Appearance Parade" example, that shows that they will work fine. > >You will of course have to customize each control to your use. That >usually involves setting a new ID, a new rect, and moving around the >items which set the values to your own control/dialog/event loops. > >Of course you can change the Appearance runtime to be in your header >with a little effort and remove the other to have full availability >of all widgets. Requires having the headers folder open, and some >dragging and dropping. Or you can make a new project, and drag all >the files on over. > >There is not a lot of work to convert from standard to appearance in >particular, the harder work is converting to Carbon, and Appearance >makes this much easier than Standard for many things I have found. >Though for some things, standard is a lot easier. If you need >floating windows at all, use Appearance. Just the autohiding is a >big plus. > > >I've found it's easier to use "Standard" type programming in many >cases even in Appearance runtime rather than pure appearance >statements (like for buttons)....some of those things require 3 >statements to do the work of one "default" conversion. :) (like a >shadow button, easier to use the old way than to then have to set >the default button attribute afterward) > >I've learned a lot more than I wanted to know about all this stuff >in converting my app Compositor to OSX and Appearance, email me if >you have a particular question. > >Robert > > > >-- >To unsubscribe, send ANY message to <futurebasic-unsubscribe@...>