Just very hard to read all the properties without scrolling. copying them to compare them is even more difficult. A simple 'copy properties to clipboard' would be an improvement.
When you make a new DialogList type of field and select option "Use view dialog for choices", the view selection list below is way too small. It shows only few letters from the beginning of the view name which, in some cases, makes it hard to select the right view ...
It would be nice if there could be some type of indication on the field, like there is for Authors/Readers, when you have the field, on standard forms, as computed, computed for display, or computed when composed and on xpages as Visible/Not Visible, Read Only/Not Read Only, and Disabled/Not Disabled....
When input enable formula returns false the text on the field becomes tan (even in read mode). It makes the text hard to read even on white background. The selected text color should remain at least in read mode or there should be possibility to select the text color when input ...
just like available as in the column options....
I would love it if while creating a view I could select a form and have notes create a view with all of the fields in that form.
This would be extremely useful when I am creating a view with many fields. Especially when that view is specifically used for importing data. Thank You.
Make it possible to change the font color or background color of a field using @Formula.
You could for example warn the user if a required field is empty by changing the backgroundcolor,
red := 255:150:150;
black := 0:0:0;
@If( fieldvalue=""; red:black )
I think there are similar ideas for this but I'm not sure its totally covered....
Basically when you use the type-ahead on the Notes 8 To email field - you find it very useful very quickly.
So it'd be nice to have something similar for standard notes dialog ...
Having just spent an age in maintenance mode tracking down a dodgy numeric field in a MASSIVE form, a simple suggestion for the Notes team is that if a numeric field is empty (i.e. in doc properties its value is ""), treat that as being the same as zero for ...
I guess this is more a fix than an idea, but never late then never:
If I select a color for a checkbox field it is not supported (mines become standard black)
Bold and italic is supported...
I would like to see a property of a field that can be used to set it's 'plain language' label.
It could be accessed via @ThisLabel or by item.label
This would be useful in any formula/script that needs to display a plain language description to the user, i.e. validation messages.......
Whenever I insert/modify a field on a form, I would like to choose the field type (text, number, etc) from a sorted list,
not like the usual field type list you can see even in R8 (see my attachment).
Maybe some Notes programmers are now used to that list, ...
The Field class in LotusScript only contains events. It would be great if it contained properties like Value (read/write) to make it easier to manipulate in the events. For example, if I want to handle the OnChange event in the client, I can use LotusScript but I have to write a ...
This would be an editable field that would not be saved. Essentially it's an area where I can edit some data and then have it parsed or in some way processed but the field itself would not be saved. It would exist only when the document is opened for editing.
Why can the user enter some non-number characters in a number field? Why isn´t this blocked just in time? It should be possible
Only when he save the form/document he will get a "cannot convert text to number" error message and this produces some user-frustrations.
What I would ...
It would be great if it was possible to copy attributes of a selected element in Designer and "paint" it onto other elements, much the way Format Painter does in Office products.
I'm thinking selecting a field and grabbing the "Computed for Display" property and being able to "paint" ...
It's always a tedious job to find a field given its name especially when the form was designed by someone else and even so when it's a complex form.
An intuitive way can be to sort the fields alphabetically in the object list (also display the fields and other elements ...
Imagine that the field properties contains "Remember old data" checkboxes with several options;
Since this is a field property, Notes will create a special field behind the scenes, for example on the format;
$History<original field name>...
Hows about a new field for designer that is a sequence number (similar to an identity field on sql server/db2 etc).
So you could add a new field to a form and select datatype 'Sequence Number'. It auto-generates a sequence number in this field for every document that is ...
Provide the ability to check off a box on the field properties box that indicates that the field is required. Also provide a UI clue that the field is in fact required. See screenshot.