home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!uknet!cam-cl!doc.ic.ac.uk!bh2
- From: bh2@doc.ic.ac.uk (B Hogan)
- Newsgroups: comp.sys.acorn
- Subject: Re: StrongED II version 1.10
- Message-ID: <182movINNmu@frigate.doc.ic.ac.uk>
- Date: 2 Sep 92 15:31:43 GMT
- References: <1992Aug26.154648.2138@alf.uib.no>
- Organization: Dept. of Computing, Imperial College, London, England
- Lines: 38
- NNTP-Posting-Host: gummo.doc.ic.ac.uk
-
- In article <1992Aug26.154648.2138@alf.uib.no> guttorm@hp825.bih.no (Guttorm Vik) writes:
- >StrongED II is now finished. I've sent it off to all my registered users today,
- >and I'll release it to the rest of the world in a months time.
- >It's actually quite good..
- > _
- >(-)rmStrong
-
- But have you got rid of those bloody stupid error windows? They have got
- to be one of the worse bits of user interface I have yet come across:
- completely non standard
- look totally out of place
- an unnecesary quirk
- they are damn annoying because you can't get rid of them when they are
- sitting right over the bit of text you want to edit (and dragging them
- often crashed the machine on version 1.00)
- ...lots of expletives...
- very, very, etc, stupid.
-
- Looking through StrongHelp I noticed the comment on Wimp_ReportError
- saying not to use it "because it's non-multitasking". So what!?!
- I just hit escape to get rid of it, total time on screen less than
- half a second (including reading the error). StrongEd error, total time
- on screen about 5 seconds (10 times longer!) of sheer mind blowing
- frustration as I try to find something to do with this bloody stupid
- plinthy thing that is sitting in the middle of my screen. Arrrrrggghhh!
-
- If the new version of StrongEd is sufficiently complete and reliable for
- me to start using it I may be forced to hack the Dialogue module so that
- that it simply calls Wimp_ReportError. It will make me feel so much
- happier :-)
-
- Bryan H.
-
- Email: bh2%dirty.doc.ic.ac.uk@doc.ic.ac.uk (hopefully)
-
- PS. Just remembered a problem I found with V1.00 - it doesn't acknowledge
- load messages. This means some programs think that the Wimp$Scrap transfer
- failed and generate an error (fortunately in a standard error window :-).
-