Home » Developer & Programmer » Forms » Wrong icon for warning message (Forms 10, Window XP SP3)
Wrong icon for warning message [message #379391] Tue, 06 January 2009 05:29 Go to next message
l0b0
Messages: 13
Registered: November 2006
Junior Member
When exiting a form after changing something, I always get the message "Do you want to save the changes you have made?" (APP-16167 I guess). However, in Forms 6 the dialog window used the appropriate caution.gif image (yellow triangle with exclamation mark), while in Forms 10 it uses stop.gif. Has the severity of this message really changed between these versions, or is it referring to the wrong image file in Forms 10? If it's the wrong image, how do I change it?

Forms 10 vs 6:
./fa/5545/0/
Re: Wrong icon for warning message [message #380002 is a reply to message #379391] Thu, 08 January 2009 18:47 Go to previous messageGo to next message
djmartin
Messages: 10180
Registered: March 2005
Location: Canberra ACT Australia
Senior Member
Account Moderator
In my opinion, it was Forms 6 that was wrong.

This 'save' message should NOT be treated as a warning message but a critical message.

David
Re: Wrong icon for warning message [message #380091 is a reply to message #380002] Fri, 09 January 2009 02:07 Go to previous messageGo to next message
l0b0
Messages: 13
Registered: November 2006
Junior Member
Thank you for your reply, David. I personally agree with you, but my given objective in this case is to provide a transition as seamless as possible for the users (and this icon issue was specified), so I still hope to find some way to change it.
Re: Wrong icon for warning message [message #380414 is a reply to message #380091] Sun, 11 January 2009 21:53 Go to previous message
djmartin
Messages: 10180
Registered: March 2005
Location: Canberra ACT Australia
Senior Member
Account Moderator
I agree with the concept of seamlessness but will the users even notice? I expect that it is only because someone is being paid to note differences between the old and new versions of the system that this current point was even found.

My treatment of issues of this type is to (1) lie, (2) obfuscate, and (3) procrastinate.

Tell them (1) that Oracle "appears to have noted the incorrect usage in its previous version and has now fixed it", (2) that you can fix it by changing an Oracle intrinsic but that changing this Oracle intrinsic would void the warranty [Basically, you would have to find the 'stop' image in the JAR file somewhere and change it to 'attention' image. Unfortunately, this would probably muck up the other 'stop' alerts. Alternatively, you will have to find the 'value' for this icon in the 'alert' call and change it to another value. Hey, search Metalink, someone may have found all these things already.], and (3) introduce a three level system of problem classification.

They break down into 'must have', 'should have', and 'could have'.

Level 1 is where the system is crashing during normal operation. This may or may not be corrupting new or existing data. It may or may not be causing the database to crash. Basically, these are big, critical, MUST be fixed problems.

Level 2 is where the behaviour is causing small localised errors. Examples are where the value being returned from an LOV is causing a 'field not long enough error', but only for one of the many entries in the list. That is, the form item is smaller than the displayed item in the LOV. This was a common error in a system that I helped convert and is not tested for in Oracle 6 so it wasn't a problem in Oracle 6.

Level 3 is for things like this 'different' but "not of your making", cosmetic presentation issue.

In the conversion in which I had the long LOVs values, there were also matters of font display and function key changes. If they had been changed in this one in-house system then ALL the other systems, some of which were supplied by Oracle, would also have had to be changed when they were upgraded. I just gave them an obscene quotation for doing the work and made sure that it was at the bottom of the rectification list. Low and behold, when the system was released to the users they never noticed the change in the alert icon and they never noticed the slight change in font size and colouring.

Granted the testing manager was not happy when I returned his 'system fault' sheet with '3rd order problem, request refused' written across it.

David
Previous Topic: HOST command for ldapcompare
Next Topic: Hyper link in oracle Report
Goto Forum:
  


Current Time: Sat Dec 03 18:09:42 CST 2016

Total time taken to generate the page: 0.27702 seconds