public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Trenton D. Adams" <tadams@extremeeng.com>
To: "'Jonathan Larmour'" <jlarmour@redhat.com>
Cc: "'Julian Smart'" <julians@redhat.com>,
	"'eCos'" <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] NASTY bug in eCos ConfigTool 1.3.1.2 Win32
Date: Wed, 13 Jun 2001 11:15:00 -0000	[thread overview]
Message-ID: <000e01c0f434$43582220$090110ac@BURN> (raw)
In-Reply-To: <3B27AC1A.7734E77D@redhat.com>

Define the difference between "unexpected behaviour" and a "bug"?  In my
opinion, they are the same.

The crash factor I discussed however is definitely a BUG! :)  It may not
have been sent to anyone yet though because of the list lag.

-----Original Message-----
From: jlarmour@cambridge.redhat.com
[ mailto:jlarmour@cambridge.redhat.com ] On Behalf Of Jonathan Larmour
Sent: Wednesday, June 13, 2001 12:08 PM
To: Trenton D. Adams
Cc: 'Julian Smart'; 'eCos'
Subject: Re: [ECOS] NASTY bug in eCos ConfigTool 1.3.1.2 Win32


"Trenton D. Adams" wrote:
> 
> Ok, I'm starting out with a project that has already been saved.
> 
> Now I change from RAM to ROM, or the other way around.
> 
> Now you know the little '*' that usually appears to indicate you've 
> made a change?  Well, it doesn't appear.  If I click on save anyhow 
> and then exit, and come back in, the RAM/ROM option I changed is back 
> to the way it was before the change.  If I don't click on Save but I 
> do exit, it asks me if I want to save.  If I select yes, then the 
> option is actually saved, and is there when I come back in.  I have 
> also tried going "File|Save As" and selecting the same filename, but 
> that doesn't work either.

I think I know what this is, and although it isn't a bug as such (more
unexpected behaviour), it should be fixed.... The problem is that if you
change the startup type from RAM to ROM, the config (as indicated by the
'*') doesn't notice. If you click anywhere else in the configuration
pane, _then_ it will notice and the '*' will appear.

It's caught me out before too, but I never requested it be fixed I don't
think :-|.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223)
271062 Maybe this world is another planet's Hell -Aldous Huxley ||
Opinions==mine Come to the Red Hat TechWorld open source conference in
Brussels!
Keynotes, techie talks and exhibitions
http://www.redhat-techworld.com/

  reply	other threads:[~2001-06-13 11:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-12 15:02 Trenton D. Adams
2001-06-13  5:14 ` Gary Thomas
2001-06-13  6:06   ` Julian Smart
2001-06-13  7:44     ` Trenton D. Adams
2001-06-13 11:08       ` Jonathan Larmour
2001-06-13 11:15         ` Trenton D. Adams [this message]
2001-06-13  7:42   ` Trenton D. Adams
2001-06-13  7:54     ` Gary Thomas
2001-06-13  7:59       ` Trenton D. Adams
2001-06-13 11:05   ` Jonathan Larmour
     [not found] <4.2.0.58.20010613154832.00c13bc0@pop>
2001-06-13  8:15 ` Trenton D. Adams
2001-06-14  8:20   ` Julian Smart
2001-06-13 10:40 Dan Conti
2001-06-13 12:19 ` Jonathan Larmour
2001-06-13 13:47   ` Lewin A.R.W. Edwards
2001-06-14  3:42 ` Gary Thomas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000e01c0f434$43582220$090110ac@BURN' \
    --to=tadams@extremeeng.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=jlarmour@redhat.com \
    --cc=julians@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).