OpenEuphoria

2. Re: David Cuny's Editor - Possible bug

• Posted by "Cuny, David" <ATB.DCUNY at HW1.CAHWNET.GOV> Apr 23, 1997
• 824 views

jconsuegra at redestb.es wrote:
> I'm currently using David4s wonderful editor. My environment is Win NT
4.0.

> When I switch to the graphics mode (by changing "RESOLUTION" to 1),
> I lose the mouse control, (only  if the screen is not maximized).

> I get the mouse control back, hitting ALT-Enter (to maximize the screen).

Perhaps this has something to do with not having a mouse driver in DOS mode?
When
my work machine was replaced with a PC running Windows95, I was suprised to
find that
there was no mouse available in DOS. Apparently, the people who set up my
machine
didn't think I needed a mouse driver, since the software gets pulled down to
the
lowest common denominator, and a 16 bit mouse driver put the code into 16
bit mode.

However, the problem mysteriously went away the next morning.

> In that mode, when clicking on some place of the text to move the text
> cursor, there is an spurious cursor that remains on the old position until
> there is a cursor move. (i.e. moving the arrow keys).

If this is happening in graphics mode, check to make sure you have the
latest
version - although I would *not* recommend running the editor in graphics
mode,
other than to see what the GUI features look like.

I re-wrote the cursor code to be much smarter than it had been. The first
graphic release left a lot of cursors all over the screen.

> I miss a couple of features that I've seen on other editors I'm using:
> - The ability of commenting-uncommenting a block of text
> - The ability of record a sequence of keystrokes to play them back. (Some
> kind of macros...)


I've wondered about the comment/uncomment thing myself, having run across it
in
the PowerBuilder editor. I'll consider it, but feel free to remind me in the
future if you don't see it show up - I've been *very* busy, and haven't had
a
chance to code anything in the last week or so.

On the other hand, I don't think I'll be adding macros to the editor. Even
if I
felt compelled to add them to the editor, I don't really use macros, so I
don't
have a good feel how to implement them.

Conceptually, they would not be that difficult to code - you could create a
sequence called MACRO, and the key routine would check there first to see if
keys are pending before trying to read from the buffer. The main trick would
be to keep the mouse state in sync.

> I've even deleted EDIT from the hard disk...

Please, no! For example, you can't edit binary files with my editor without
it
crashing. I appreciate the vote of confidence, but it's best to be safe...


Thanks for the feedback!

 -- David Cuny