Hi Tom, > From: Tom Benson > These look very cool.
Thank you I hope you'll try them out. > Just one small suggestion based on the example code on your site: > Why don't you use the assigns keyword in your function definitions. > This would make your classes much more inline with the rest of the > native framework. > e.g. > If you change the SetFontName declaration to read > Function FontName(assigns s as string) > > then you could just state: myText.FontName = "Impact" > instead of the current: myText.SetFontName "Impact" > > And I would split the function SetShadowOffset to be ShadowOffsetX > (assigns n as integer) and ShadowOffsetY(assigns n as integer) > > Just seems more natural to me. Good suggestions -thank you! I prefer set and get methods when I write non-framework classes, but I can add this syntax. I'll put this on my to do list. And I'll kindly remind you that poo poo and cyanide are also *natural*. ;) JK. -- Thomas C. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
