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

[Vlad Harchev]

On Tue, 27 Jul 1999, Vlad Harchev wrote:

> >[...] 
> > Maybe you can still consider the ideas in my other message written earlier
> > (basically, (1) paying attention to cursor position and maybe statusline,
> > (2) try to use hightlight(ON) for input fields for something useful).
> > Could be that *then* the state is not necessary.
> 
>  As I described in my previous message, the cursor is blinking in 'entered'
> textinput, and not blinking in 'not yet entered'.
>  As for statusline, its content is the same for activated and non-activated
> textinput. The patch to add status line will be sent in 30 minutes.

 Here is a patch to add proper statusline messages. It has one side effect -
when moving between textinputs statusline flickers (since long string
corresponding to real statusline message is displayed 2 times, and after that
shorter "Inactive text input..." is displayed.
 Feel free to correct the message.

 Best regards,
  -Vlad

--- LYMainLoop.c-old    Mon Jul 26 20:29:02 1999
+++ LYMainLoop.c        Tue Jul 27 09:31:17 1999
@@ -748,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:
@@ -6750,6 +6754,12 @@
     } else {
        _statusline(HELP);
     }
+    
+#ifndef NO_NOSTICKY_INPUTS
+    if (textarea_drawn) {
+       _statusline(gettext("Inactive text input, activate to edit (eg press 
ENTER)"));
+    }
+#endif    
     /* turn off cursor since now it's probably on statusline -HV */
     move((LYlines - 1), (LYcols - 1));
 }