Poll #14

FLTK matrix user chat room
(using Element browser app)   FLTK gitter user chat room   GitHub FLTK Project   FLTK News RSS Feed  
  FLTK Apps      FLTK Library      Forums      Links     Login 
 Home  |  Articles & FAQs  |  Bugs & Features  |  Documentation  |  Download  |  Screenshots  ]

Show All Polls | Show Comments | Submit Comment ]

Poll #14

How should the next/previous word function work in Fl_Text_Editor?
Look for the first letter/number only (current behavior) 49 / 25%
Look for the first non-whitespace character 45 / 23%
Look for the first non-whitespace, non-punctuation character 96 / 50%
190 total votes.
This poll is closed.

User Comments

Submit Comment ]

From Anonymous, 07:29 Apr 15, 2003 (score=5)

excuse me I'm french & my english is low so... i have a problem with snavigator because it doesn't want to compile without "GLU & GL" so where can i find this directoty?? Thanks
Reply ]

From Anonymous, 08:31 Apr 02, 2003 (score=3)

Why not add an extra argument so the user can decide for him/herself? By default, I would prefer the first option.
Reply ]

From Mike Sweet, 19:00 Apr 04, 2003 (score=2)

That might be an option for 2.0, and FWIW you can override the key functions in the current release to provide any kind of handling you want.
Reply ]

From Anonymous, 15:32 Apr 05, 2003 (score=1)

I believe we should keep it the way it is and maybe add a derived class for editing 'program code' that also looks for typical programmers characters (Fl_Code_Editor?). While we are at it, we could derive further and add a C editor (Fl_LangC_Editor) with syntax highlighting (although that should probably not be part of the regular library). Just a thought.
Reply ]

From Anonymous, 05:23 Apr 07, 2003 (score=1)

I agree. The best approach would be to let the user decide what he wants the delimeters to be.
Reply ]

From Dan Mergens, 18:46 Jul 31, 2003 (score=1)

The default behavior should mimic the generally excepted behavior. Compare to Microsoft's Ctrl+->, VIM, etc. I believe they use first non-whitespace. Of course, letting the user have options beyond that is always a good idea.
Reply ]


Comments are owned by the poster. All other content is copyright 1998-2023 by Bill Spitzak and others. This project is hosted by The FLTK Team. Please report site problems to 'erco@seriss.com'.