|
|
I would like to see an improvement of LotusScript errorhandling and therefore introduce the Try..Catch..Finally block that You do in Java and other OOP languages.
That would give us the option to get rid of the hideous On Error Goto statements and have proper errorhandling as it should be.
|
|
|
When you use PickListCollection in LotusScript, you cannot handle the error "Invalid Selection" when the user does not select a document from the picklist view. The error message is redundant, because the developer can handle this situation using the returned (empty) document collection.
|
|
|
When you use PickListCollection in LotusScript, you cannot handle the error "Invalid Selection" when the user does not select a document from the picklist view. The error message is redundant, because the developer can handle this situation using the returned (empty) document collection.
|
|
|
When you use PickListCollection in LotusScript, you cannot handle the error "Invalid Selection" when the user does not select a document from the picklist view. The error message is redundant, because the developer can handle this situation using the returned (empty) document collection.
|
|
|
When you close the message (in the screenshot), it begins to appear cyclically, once every half-minute.
If the Notes Client has been loaded, then after you receive this message the Notes Client is unavailable, it has to shoot with killnotes.exe. If the Notes Client was not loaded (applacation Symphony starts with
|
|
|
This restriction exists for the following methods NotesUIWorkspace class: PickListCollection, PickListStrings, Prompt, URLOpen, EditDocument, SaveFileDialog, OpenFileDialog. Its meaning is not clear, because DialogBox allowed, and he calmly executed?!!
I propose to remove this restriction, without him it will be very convenient to choose something, but, for example, if you cancel in
|
|
|
I propose that it's method returns the result as Boolean, is quite enough.
It is better add to Desinner Help describe the situations where the method may return False, and this:
- getting NotesDocument object from another instance of the NotesDabatase object;
- addition duplicate
|
|
|
Generation of this error is useless, it also hinders. All error handling should be done in the proper place - on QuerySave.
I propose that the Save method returns the result as Boolean, it's would be very convenient and usefull.
|
|
|
In the Lotus Domino Designer tab will appear on "Problems", in which displayed records of errors. I propose (for LotusScript) at DoubleClick on records not to display the source code of the element of design in XML, but open the corresponding element of the design, automaticaly finding the wrong
|
|
|
Generation of this error is useless, it only hinders. Quite enough to return Nothing.
Similar GetDocumentByID method does not generate errors.
|
|
|
On error, produce a 'core dump' of all defined variables, objects, and a call trace.
The 'core dump' might provide a limited (one-level) listing of defined objects with their property values, and all local and global variable values. Going down more than one level might end up with a huge amount
|
|
|
When you give me the error "File does not exist ", at least tell me which file you are talking about...
|
|
|
while it's possible to use domcfg.nsf to map some types of http errors to special forms in the domcfg.nsf database the level of control it provides is not great and relies on the Domino administrator to work with the designer to edit that particular database and create the mappings etc.
I
|
|
|
When opening a document in the Notes client and a formula prevents the form from loading you will be told which field has the problem. On the web you get something like:
HTTP Web Server: Lotus Notes Exception - Incorrect data type for operator or @Function: Number expected
And then you have
|
|
|
It would be nice to be able to customize this option to go to an interal company Database/FAQ or URL where you could have your own customized KBase entries for your our own users. I hope IBM has enhancement plans for this option.
-Tim E. Brown
|
|
|
The following scenario:
1. A web-form makes ajax calls against a domino agent.
2. User starts to work on a document on his web client.
3. User plays WII tennis match with his collegue.
4. User returns to his document and presses an ajax enabled button. Unfortunatedly in the meantime his web session has
|
|
|
Saving shared actions (with LS) should run compiler a do all error processing analogous to agents, script libraries, etc.
|
|
|
Hi,
how often called a user and said he has the "An error was encountered while opening a window." error message on his screen? You know that a reboot would fix this problem (a re-login will work also sometimes)...
So my idea is to change this error message... something which is usefull
|
|
|
Why do I need to write
"On Error Goto ErrorLab
...
Exit Function ErrorLab: Call CommonError Exit Function End Function" in each function/sub? Let me to write this code in one place and extend it to all LotusScript errors at any Function/Sub
|