IBM®
Skip to main content
    Country/region select      Terms of use
 
 
   
     Home      Products      Services & solutions      Support & downloads      My account     

developerWorks  >  Lotus  >  Forums & community  >  Best Practice Makes Perfect

Best Practice Makes Perfect

A collaboration with Domino developers about how to do it and how to get it right in Domino

One of the pleasures of this work is that occasionally I get to fix one of those annoying things that have been vexing people for a while. Today, I checked in my fix for in-view editing in Designer so it doesn't modify the design note if you didn't actually change the value. Nothing is ever certain until it's released, but it should be in the next point releases of 7 and 8 (but not in the 8.0.1 beta). [BTW as far as development is concerned, 7.0.3 is already done. We're working on 7.0.4]

If you have design locking enabled, the design element still gets modified, though, since it is locked to let you get into edit mode before we know what you'll type.

I've also added an INI setting to disable in-view editing in Designer. I know people have suggested changing the timing post-click before starting the edit mode (or making this timer adjustable), but I didn't like to mess with this because it seemed a bit risky. The code is shared with the client, which uses the same timer.

I'm looking forward to switching over from "classic" Designer work to the new Java-based UI, which should make it easier to correct some of these little problems (by just failing to include them in the new code).

Andre Guirard | 9 October 2007 11:45:52 AM ET | Plymouth, MN, USA | Comments (8)


 Comments

1) Esc key works fine
Mika Heinonen | 10/9/2007 1:45:08 PM

I don't quite understand the problem here. When pressing the Esc key, the changes will not be saved. And when pressing the Enter key, it should really alert people since it's the "Execute", "Master Save", "Force Submit", "Launch Nuclear Missiles" key.

2) Mouse and Focus change
Mika Heinonen | 10/9/2007 1:48:20 PM

And the mouse button to change focus is of course also an "Enter" key. One problem exists in the current way it works though: pressing Alt-Tab to switch windows looses the focus and saves the entry too.

3) THANK YOU
Julian Robichaux | 10/9/2007 4:27:32 PM

Thank you SO MUCH for fixing/changing this.

Unlike Mika, I am constantly getting bit by this little piece of functionality. Even though I know the Escape key works, there have been several times when I have a design element highlighted, and then I accidentally single click it (putting it in in-view edit mode) and then immediately click another adjacent element, which signs the first element with my name and changes the modified date. Without warning. Woe unto me if it was a scheduled agent or one that runs with agent signer access using a process that I'm not allowed to run (or one that sends e-mails).

While you're in the code, can you also segregate the right-click Agent "Run" option a little more too? There have been one or two times that I've right-clicked an agent to do the "Test" option, and accidentally hit Run instead -- on workstations with small fonts, all it takes is one or two pixels of mouse float to make that mistake. Maybe "Run" could be all the way at the bottom, underneath a separator?

Never hurts to ask, right? In any case, thanks again.

4) Nice One!
Ian Scott | 10/9/2007 5:32:28 PM

I support two mission critical databases which reside on a server in their own domain under their own certificate hierarchy and which contain agents that perform restricted operations. If my UserID signs those agents the system will grind to a halt. Needless to say I've been living in absolute terror of signing them by accident.

Yes, Mika, we know about the escape key but the double click can happen before one is aware of it. I've been lucky, I think, but I've also trained myself to use the keyboard when navigating the agent view.

I can barely wait for this. Thank you 8-D

5) Thank you!
Kendall | 10/9/2007 11:58:17 PM

Thanks, Andre!!!

6) Did escape even work in 7.0?
Fabian Robok | 10/10/2007 1:35:52 AM

I seem to remember, that even hitting escape did not protect the code from being signed in the gold release of Notes 7. Once you hit it, you were toast ...

One more thank you for this change from me. Though I trained myself hard to use the escape key now, this is definitely a nice one. And I wouldn't vote against Julian's proposal as well (but only if it can be done in the right-click menu AND in the Agent menu).

7) WOO-HOO!
Joe Litton | 10/10/2007 7:27:38 AM

Yeah, we've been getting bit by this all over the place. We'd searched the 'net and the documentation and all config options we could find to try and find a way to keep that blasted update from happening ...to no avail.

Thanks for including this fix in the update to SEVEN as well as 8!

8) thanks!
Charles Robinson | 10/16/2007 10:34:03 AM

"I've also added an INI setting to disable in-view editing in Designer." I already admired you, now you're my hero! Oh wait, I already promised that to Maureen.. and Mary Beth... and Julie... and Bob... I have a lot of heroes at IBM/Lotus. :-)

9) Thanks for fix to prevent a futher waste of precious time
Anthony Reed | 12/19/2007 2:55:49 AM

in environments where change-control is applied, this would cause waste of time. For example if you accidentally "change" a design elements name. You would then have to cancel your check out and check an unchanged database (or design element) out of your CC system, and the resulting effort if you had already made changes to other elements.

Even in a more chaotic environment an accidental and unintended "change" is made and ignored. later-on someone else starts looking for the latest copy to change and picks the wrong one..

Sure pressing ESC is easy but accidents happen..

 Add a Comment
Subject:
   
Name:
Comment:  (No HTML - Links will be converted if prefixed http://)
 
Remember Me?     Cancel

Search this blog 

Disclaimer 

    About IBM Privacy Contact