OpenEuphoria

Edita help window

• Posted by CChris <christian.cuvier at agriculture.gouv.fr> Apr 10, 2007
• 530 views

I just looked at the "nw" local options/definitions in Edita, and I'm quite
 puzzled.

First of all, when the file being viewed is not an Eu file (welcome.txt), it
 spits out the unformatted contents of the file. This displayshoumd be
 suppressed I think, and F1 should go straight to the keyboard shortcut window.
It would be even better if the behaviour of F1 was predictable, using Ctrl-F1
 to access the options/definition window when these words make sense for the
 current file. By the way, I didn't even try if I'd get a meaningful output
 using say a C++ file. Since there is syntax coloring for other languages,
 I'd expect pragmas/#ifdefs and such to be displayed there.

Then I opened a standard Eu file and tried selecting different lines there, 
and see what F1 does.

1/ If the line is a comment or blank, the result is a set of commented lines
 in file, not always the same. I don't really get it. Shouldn't all
 commented lines outside of routines be displayed? Just try the first few
 lines of misc.e.

1'/ Then how could comments obviously related to routines/constants be
 displayed? They are the most important thing to read, very often.

2/ So you can't display constants, procedures etc at the same time, since
 the current line must be a constant declaration, procedure declaration etc.
This is hardly useful. Don't rely on the current line contents and supply 
a set of checkboxes instead (plus a select all button).

3/ Staggered constant declarations don't display, namely the platform()
 return values in misc.e.

A gallant try, but... imho the design has some serious flaws. And I stopped
 the tests fast, because I'd consider the above as blocking.

I'm using what I think is the latest release - it has refolding and IDs as
 23/12/05. The About box should really display the version number somewhere.

CChris