Alan, try: On Click or On Data change (for your boolean) set timer(1) or some other small value
in the form method, On Timer call process(current process) or Call Process(-1) Chip > Hello again Bernd, > > I tried several other things but never got anything to work other than my > original code. I even tried setting a timer and running your code there, > but it still didn't redraw each line of the display. > > Thanks again, > Alan > > On Thu, Jan 3, 2019 at 5:37 AM Alan Tilson <[email protected]> wrote: > >> Hello Bernd, >> >> Your solution seemed much more elegant than mine, which was to cut and use >> a named selection, but for some reason it doesn't work for me. The boolean >> variable that I'm clicking on goes grey and nothing else changes. If I >> click another window and come back the boolean and the rows do update. >> >> Any ideas about what might be different? >> >> I tried HIDE WINDOW / SHOW WINDOW which caused a flicker but not a redraw >> as did HIDE PROCESS / SHOW PROCESS. >> >> I also tried Open Window / CLOSE WINDOW... didn't work. >> >> This does work with some side effects, especially if the user has scrolled >> down... >> >> CUT NAMED SELECTION(Current form table->;"tempNS") >> USE NAMED SELECTION("tempNS") >> HIGHLIGHT RECORDS >> >> >> Thanks from North Carolina, >> Alan Tilson >> >> On Thu, Jan 3, 2019 at 2:18 AM Bernd Fröhlich via 4D_Tech < >> [email protected]> wrote: >> >>> Alan Tilson: >>> >>>> Has anyone had issues with REDRAW WINDOW working differently or not >>> working >>>> in v17? I have an output form with a boolean variable in the header that >>>> affects the text color of the fields in each line of output as well as >>>> determining which of a few optional fields are displayed. If I call >>> REDRAW >>>> WINDOW after changing the boolean variable the records list does not >>>> change. If I click on another window and come back to the original >>> window >>>> everything updates. >>>> >>>> This worked fine in v13. >>>> >>>> Am I missing something? >>> >>> 4D V6 or V7 was the last version where REDRAW WINDOW was redrawing the >>> whole window, then 4D began to "optimize" the redrawing. Maybe it >>> is faster >>> now, but it definitely is no longer working as expected. >>> My workaround: >>> >>> // Methode: RedrawWindow >>> // Angelegt: BF 16.09.03 >>> // Objekt: Dienstroutine >>> // Beschreibung: Umgehung für das seit 4D 2003 nicht mehr zuverlässig >>> funktionierende Redraw Window >>> // ---------------------------------------------------- >>> >>> C_LONGINT($lLeft;$lTop;$lRight;$lBottom) >>> >>> GET WINDOW RECT($lLeft;$lTop;$lRight;$lBottom) >>> SET WINDOW RECT($lLeft;$lTop;$lRight-1;$lBottom) >>> SET WINDOW RECT($lLeft;$lTop;$lRight;$lBottom) >>> >>> >>> Gives a short flicker, but is the only way I know of to actually redraw a >>> window. >>> Maybe someone else has found another solution without the flicker? >>> >>> Greetings from Germany, >>> Bernd Fröhlich >>> ********************************************************************** >>> 4D Internet Users Group (4D iNUG) >>> Archive: http://lists.4d.com/archives.html >>> Options: https://lists.4d.com/mailman/options/4d_tech >>> Unsub: mailto:[email protected] >>> ********************************************************************** >> >> > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** ------------ Hell is other people Jean-Paul Sartre ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
