lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev patch that allows text inputs to be non-sticky


From: Leonid Pauzner
Subject: Re: lynx-dev patch that allows text inputs to be non-sticky
Date: Thu, 29 Jul 1999 21:11:20 +0400 (MSD)

28-Jul-99 07:18 Vlad Harchev wrote:
> On Tue, 27 Jul 1999, Vlad Harchev wrote:

>  Here is a patch that contains other small patches posted by me in this thread
[...]

Reading your patch I see too many places in different files
where textarea_drawn is set to FALSE, especially these two in mainloop:


> diff -ru lynx2-8-3dev4-fixed-old/src/LYMainLoop.c 
> lynx2-8-3dev4-fixed/src/LYMainLoop.c
> --- lynx2-8-3dev4-fixed-old/src/LYMainLoop.c  Thu Jul 15 09:50:48 1999
> +++ lynx2-8-3dev4-fixed/src/LYMainLoop.c      Wed Jul 28 07:02:14 1999
> @@ -742,6 +748,10 @@
>               getresult = getfile(&newdoc);
>  #endif /* TRACK_INTERNAL_LINKS */

> +#ifndef NO_NOSTICKY_INPUTS
> +             textarea_drawn = FALSE; /* for sure */
> +#endif
> +
>               switch(getresult) {

>               case NOT_FOUND:
> @@ -1453,7 +1463,9 @@
>        *  All display_partial calls ends here for final redraw.
>        */
>       if (curdoc.line != Newline) {
> -
> +#ifndef NO_NONSTICKY_INPUTS
> +         textarea_drawn = FALSE;
> +#endif
>           refresh_screen = FALSE;

>           HText_pageDisplay(Newline, prev_target);



Two entries above seems chosen in a wrong (non-standard) location.

Does the resetting should be done before HText_pageDisplay()?
If yes, "partial display" output will be affected at getfile() stage
[try lynx -debug_partial -partial_thres=2].

Also, there is the second HText_pageDisplay() call of "refresh cycle",
is it relevant or not?
[BTW, the first document when running with -trace go that cycle -
is it intentionally or what? (very old question)].






reply via email to

[Prev in Thread] Current Thread [Next in Thread]