15 May 23:46
Re: Display of Field Updates on Form
From: Bill Desjardin <bill@...>
Subject: Re: Display of Field Updates on Form
Newsgroups: gmane.comp.lang.inug-4d.tech
Date: 2008-05-15 21:46:19 GMT
Subject: Re: Display of Field Updates on Form
Newsgroups: gmane.comp.lang.inug-4d.tech
Date: 2008-05-15 21:46:19 GMT
Paul & Miyako, Thanks for your input. I tried the resize form ideas without any results. The only way I could get the fool thing to work was to do a SAVE RECORD & LOAD RECORD combo. Luckily, I am inside of a transaction and can roll back the changes later, if needed. Bill On May 15, 2008, at 12:33 PM, MIYAKO wrote: > Hello. > > REDRAW and REDRAW WINDOW are no longer relevant and have no > practical effect. > CALL PROCESS(-1), or RESIZE FORM WINDOW(0;0), as you have rightly > pointed out, > is the current way to redraw. > > to be more specific, you need to fire a form method, which both of > the above effectively does. > > the real question is, why would you need to redraw outside the > context of a form event? > > an understandable situation would be, that you have updated the > values within a plugin. > in such cases you may execute Variable:=Variable just to notify 4D > which Variable requires a redraw. > > I have no definite explanation for the case Bill is seeing, > (obviously an On Clicked event has been fired), > perhaps it has to do with the layout order (level) of each objects > on the form > and the manner in which 4D draws individual objects (from back to > front). > > maybe only Variables are subject to such immediate updates > whereas records require LOAD RECORD. > > miyako > > On 2008/05/16, at 3:57, Paul Mohammadi wrote: > >> Bill, >> >> I curse 4D's ability or rather inability to update form elements on a >> daily basis... sometimes they work flawlessly, sometimes they choke. >> REDRAW command is pathetically ineffective. >> >> The one sure fire way I found out that the form elements are drawn >> correctly is by resizing the window by 1 pixel... Create your own >> wrapper REDRAW_FORM where the form window is re-sized 1 pixel and >> then >> immediately re-sized back 1 pixel, this way the original window XY is >> maintained and everything on the form is updated... drawbacks are... >> output windows and subforms need to re-page their data from the >> server >> creating needless I/O but otherwise It should work. > >> On May 15, 2008, at 11:22 AM, Bill Desjardin wrote: >>> To All, >>> >>> I am seeing a strange situation re display of field updates on a >>> form opened by a MODIFY RECORD command. I have some buttons on >>> the form, that when clicked, update the values stored in some >>> fields of the record. Some of the fields immediately display the >>> updated values on the form, but others do not. I have some >>> fields that always show the updates, some fields never show the >>> updates and some that show the updates some of the time. These >>> results are on Mac OS 10.4.11 using 4D 2004.6r2. If I switch to >>> Windows 2000 or XP, the display results that show sometimes on >>> Mac do not display at all. I have tried all of the trickery that >>> I can think of without being able to obtain reliable results. >>> Any ideas? >>> >>> Bill Desjardin >>> ********************************************************************** The 4D v11 SQL Roadshow - coming to a city near you! http://www.4D.com/roadshow/index.html 4th Dimension Internet Users Group (4D iNUG) FAQ: http://www.4d.com/support/faqnug.html Archive: http://dir.gmane.org/gmane.comp.lang.inug-4d.tech Unsub: mailto:4D_Tech-Unsubscribe@... Post: mailto:4d_tech@... Options: https://lists.4d.com/mailman/listinfo/4d_tech **********************************************************************
RSS Feed