Dr. Seuss might say:
Two Clicks, One Click, Which Click(s) Will You Pick ?
Two Buttons, One Button, Are You A Click Glutton ?
3 Likes
Yes, I hadn’t noticed that. In that case I agree — I’d be quite happy for the ugly grey “+ Add Spouse” boxes to disappear completely and just use right-click when I actually want to add one.
That would solve the clutter.
The only thing it wouldn’t solve is the other part of what I was getting at: distinguishing someone I’ve researched and established has no spouse or partner from someone I simply haven’t researched yet.
I’d still like some way of recording that distinction, even if it has nothing to do with the “+ Add Spouse” box.
So since all of this back and forth is getting you precisely no where, other than other users telling you it isn’t really useful, have you actually taken time to write this brilliant idea up and tried emailing it to support?
Your are not really making a good argument for why a a feature that seems to be very limited in usefulness is something that RM just has to jump on to the expense of other more widely useful features that they might have in the pipeline.
Write this up, explain why this is going to be generally useful to the wider user base. Provide links to any previous requests that you can find here, or just general discussions of said feature. Keep in mind that many users have many brilliant (or so they think) ideas that just have to be integrated into RM. Many of them far more promising than your suggestion. Tell support/dev how your idea is so much better and deserves the time and effort you are asking them to give it. You also may want to explain any perceived impacts on the existing program. For example, the persons in your database for whom you choose to collapse the ‘add spouse’ box are all going to require database alterations in order to store the preferred status. The user interface will need to be altered to allow that section to fold in or expand based on the database flag. Should this feature state be searchable, if so this is going to cause alterations to search or advanced search…and that is just to name a few things.
When big scale changes start to need to be made to a accommodate a feature with limited use it isn’t really going to work in your favor…so any ideas on how to mitigate future problems from requested change would be a good think to add to the document. Also remember that there is probably a roadmap of things the devs plan to add/change for at least the next version and possibly more than that so it could literally be several years before you see such a feature.
Ah, Dr. Seuss. Splendid.
Monty Python seems rather more appropriate here: The Argument Clinic for the method, followed by Dead Parrot for the argument once everyone has noticed it stopped moving some time ago.