Book a Demo

Author Topic: BUG: NOT taking yes for an answer!  (Read 3651 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
BUG: NOT taking yes for an answer!
« on: January 19, 2007, 01:29:26 pm »
In testing some issues with name rendering on a previous post, I create some long names with spaces (to help with wrapping).  EVERY time I saved the spaced name EA asked me the question about if I really wanted to have a name with spaces.  Because of the the testing I was changing the element (but not the name) many times within a minute, for about 5 minutes...

To say the least it became VERY ANNOYING.  The question should ONLY be asked if I change the name.  If the fact that I wanted a name with spaces can't be persisted (across sessions) it should still ONLY be asked once a session (unless I change the name from unspaced to spaced).

Annoyed... ::)
Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: BUG: NOT taking yes for an answer!
« Reply #1 on: January 19, 2007, 02:39:07 pm »
Perhaps a bit annoying for the poor overworked developers, but a nice idea.

Perhaps this could be on a per session basis. That way there would not necessarily have to be a change to the schema. Another advantage would be that another user would also be asked the question, rather than relying on whatever the first user answered.
No, you can't have it!

thomaskilian

  • Guest
Re: BUG: NOT taking yes for an answer!
« Reply #2 on: January 21, 2007, 11:24:21 am »
There's an option so you don't get asked at all, right?

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: BUG: NOT taking yes for an answer!
« Reply #3 on: January 21, 2007, 01:04:55 pm »
Quote
There's an option so you don't get asked at all, right?
Yes Thomas,

Tools|Options...|Objects   [ ]No warning for space in class name goes to the other end of that scale.  I actually do need to be warned if I have a space in the Class name.  But only if I introduce a space.  I especially don't want to be reminded if I don't change the name.

In other words, not never warn does not imply always warn.

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

darren.sampson

  • EA User
  • **
  • Posts: 39
  • Karma: +0/-0
    • View Profile
Re: BUG: NOT taking yes for an answer!
« Reply #4 on: January 21, 2007, 06:38:39 pm »
To fix this, there's no need for a change to the schema.

All that EA needs to do is note if the name of the class changes - if the name hasn't changed, there's no need to provide informational messages or persist the name when saving.  This class name "dirty bit" info only needs to be kept between saves - it doesn't need to be kept for the whole session.

I'm with Paolo - this is very annoying and needs to be fixed.  It's just one of many UI annoyances though.

Darren
See the new Jobs Section on:EA Wiki...

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: BUG: NOT taking yes for an answer!
« Reply #5 on: January 22, 2007, 05:29:36 am »
The schema change (or at least stored information change) would apply if the setting were to be permanent. That is, if the user would only be warned about spaces when the name was originally assigned, and never thereafter, rather than for the balance of the session only. In essence, the dirty bit is being stored.
No, you can't have it!

mikewhit

  • EA User
  • **
  • Posts: 608
  • Karma: +0/-0
  • Accessing ....
    • View Profile
Re: BUG: NOT taking yes for an answer!
« Reply #6 on: January 22, 2007, 07:34:04 am »
It's basically querying a name containing spaces regardless of  whether you have just altered it - looks like a logic bug ... 'if' in the wrong place or something.