farkle = function + sparkle. frustroykle = frustration resulting from function destroyed by sparkle

In RQM, if you open a tab, such as "View Testcases", you will notice that there is no Icon to close that tab unless you hover over the area where you "think" it "ought" to be, and then it may or may not "magically" appear. Sometimes, you have to move the cursor around, say the secret mantra, or hold your mouth right before the little "X" will appear. Wait! If it doesn't appear as RED, then it won't work, so you have to wait for it to turn RED!

This is an excellent example of function destroyed by sparkle. If you are under pressure, and QA is ALWAYS under pressure, it's really frustrating to have to fool around with a simple tab closure because someone in development thought it would be cute to have a disappearing icon. This kind of thing makes a product maddening instead of a joy to use.

A good tool is designed with it's ENTIRE focus on the USER experience, not the developers or designers desire to use their newly acquired skills and all the latest gizmos.

Please, if it's really simple, and works like a charm, leave it alone. The "X" that closes a tab is a functional necessity. It works fine. You should have left it alone. Now you need to change it back. Please. For your sake. For your user's sake. Learn from this tiny little, extremely frustrating mistake.