Hi again, Do you mean something like this: Existing EditFields: TextfileldScroll and TextFielNoScroll
A Window Property : myEdifield as EditField And then in the Window Open event if globals.UseScrool = true then dim myEditFiled as TextFieldScroll else dim myEditField as TextFieldNoScroll end if OR are you mean using classes? In the case of classes, I can't set the scrolls in the class, that only in the "used" editfield. Sven E On 2007-04-23, at 19:35, Sven E Olsson wrote: > > On 2007-04-23, at 18:43, Dennis Birch wrote: > >> On 4/23/07, Sven E Olsson <[EMAIL PROTECTED]> wrote: >>> Thanks for your reply, >>> >>> I have tested to use "pairs" of EditFields, It just sound easy and >>> fast to do, and so it is in an new project. But in my case, I have >>> tried this for two days, and not get it to works, one reason is that >>> I have a splitter function on that window,that give me other issues. >>> (it looks like tab panel issues) >> >> I obviously don't know all of the issues you're dealing with in your > > Only one... Now it is the splitter .. I get no edit filed to showing > up, only the transparent splitter background, and when I move the > splitter then it appears.. > >> application, but I've done something similar in the past, so perhaps >> my experience can help. >> >> What I've done is create a Window property like "pEditField As >> EditField", and then assign one of the different types of EditFields > > But here I also get issues with the splitter > > I should muck with this some day more.. and the we see how to do.. > > > > Sven E > _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
