Thanks Fred and Dave, The syntax solved the thrown error but the values are not changing. I put a wait window in the DownClick event with the spinner.value. The window shows the value each time the DownClick event fires both from the spinner and from the button but the value only changes when the spinner is clicked. There must be something else happening that I don't understand. More help?
Thanks, Joe On Fri, Mar 14, 2014 at 12:27 PM, Dave Crozier <[email protected]> wrote: > Thanks Fred, you beat me to it! > > Dave > > -----Original Message----- > From: ProFox [mailto:[email protected]] On Behalf Of Fred Taylor > Sent: 14 March 2014 16:20 > To: ProFox Email List > Subject: Re: Spinner interactive change limit control etc > > Syntax is to name the event, not execute it: > > RAISEEVENT(objectref,"MethodName") > > so: > RAISEEVENT(thisform.spiner1,"DownClick") > > Fred > > > On Fri, Mar 14, 2014 at 9:16 AM, Joe Yoder <[email protected]> wrote: > > > Thanks Dave, > > > > When I read your response I realized that what I need to do is adjust > > the Spinner Low or High values of the opposite control from the > > interactive change events. This prevents the value from going out of > > range and eliminates the need to know the direction of the change in > process. > > > > I was not aware of RaiseEvent before reading your post. I think it > > will solve my problem but haven't figured out the proper syntax. > > Below is what I have in the click event of the down button. The > > commented lines work when enabled but ignore the range limits of the > > control. Both of the active lines throw errors. Can you correct my > syntax? > > > > Thanks, > > > > Joe > > > > *thisform.spinner1.Value = thisform.spinner1.Value -1 > > *thisform.spinner2.Value = thisform.spinner2.Value -1 > > RAISEEVENT(thisform.spinner1, thisform.spinner1.DownClick) > > RAISEEVENT(thisform.spinner2, DownClick) thisform.refresh > > > > > > > > On Fri, Mar 14, 2014 at 4:08 AM, Dave Crozier <[email protected]> > > wrote: > > > > > Do you call the methods directly or use RaiseEvent()? Personally I > > > would bind the click methods to the button or method click. > > > > > > As for working out whether it is an increase or decreas, simply add > > > a "last_value" property to the control and use this to compare > > > against the current value to see if there has been an > > > increase/decrease > > > > > > Dave > > > > > > > > > > > > -----Original Message----- > > > From: ProFox [mailto:[email protected]] On Behalf Of Joe > > > Yoder > > > Sent: 14 March 2014 05:51 > > > To: [email protected] > > > Subject: Spinner interactive change limit control etc > > > > > > I am trying to control the actions of two spinner controls so that > > > the value of one is always less than or equal to the other. My code > > > is in > > the > > > interactive Change events but I don't know how to figure out whether > > > the event fired because of a requested increase or decrease in value. > > > > > > I would also like to programatically increase and decrease the > > > values of both spinners simultaneously with some extra buttons. My > > > button code > > calls > > > the spinner's upclick and downclick methods but they don't seem to > > > have > > any > > > effect. > > > > > > As always - any help will be appreciated. > > > > > > Thanks in advance, > > > > > > Joe > > > > > > > > > --- StripMime Report -- processed MIME parts --- multipart/alternative > > > text/plain (text body -- kept) > > > text/html > > > --- > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CABQeDnXPw7jw===gsgqusdzwn342ipsodokyycgnr7q3gio...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
