Sean McCollum wrote: > I agree with Giovanni - FTC is a really nice control. And I > understand your position of only adding elements to your own code > that are needed in your own personal projects. I do the same. > > But, you are now selling this control to the masses for $450, and > something as basic (not necessarily easy for you to implement into > FTC, mind you) as being able to add a tab-stop in the text seems > like a big omission to me. It's been a request on the nug for the > RB editfield. > > Kind of reminds me of building a really incredible car for sale - > great looking, sleek lines, GPS nav, satellite radio, etc... but > no seats. > > Really cool features - the new custom object is awesome - are > great, but the control on the whole is lacking because of the tab > omission. > > Couldn't tabs be implemented without a visual representation > (ruler). There aren't any other built-in visual features. We could > use Zegs Ruler, if it's still around, or design our own custom > canvas to visually display the tab settings. FTC just needs to be > able to handle the tab settings.
Most certainly it could be implemented that way. I am not going to do the full solution for version 1.0. I never said I am ommitting it or haven't thought about it, I am saying I have plans for a full and complete implementation in the future. Like I said before I haven't decided what exactly I am going to do with tabs in version 1.0. There are many ways to deal with tabs and the most probable way it will be handled will be to have fixed length tab stops. So hold on for a bit and see what I do. I will not let tabs fall by the way side, it is only a question of how to logically render them for version 1.0. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
