Not a BIG deal.. but can we not have your defaults?

BLOMASKY

When I add a Query or relationship on a form, I get an edit option...

When I create a new query, I get the filters all filled in....

New forms have buttons to export to CSV, and other stuff I never use...

I am sure you are doing this cause you figure most people might want it... BUT... how about either NO defaults, or have a configuration option to let us select which ones we want.

Not a BIG deal.. but...

Bruce

pureist

yes. good idea.

BenHayat

These are the areas that slows you down when programming in Aware, doing repetitive work where defaults can save you lots of time.

pureist

BenHayat wrote
These are the areas that slows you down when programming in Aware, doing repetitive work where defaults can save you lots of time.

Yes, but the amount of time spent removing 'defaults' you don't want, is often greater than adding in options you do want.
you can't pre 'guess' the 'defaults' correctly.

BenHayat

pureist wrote
BenHayat wrote
These are the areas that slows you down when programming in Aware, doing repetitive work where defaults can save you lots of time.

Yes, but the amount of time spent removing 'defaults' you don't want, is often greater than adding in options you do want.
you can't pre 'guess' the 'defaults' correctly.

I meant, the defaults should be created by developer in configurator.

crisg0112

This has been a time-consuming exercise when you have a V6 app and change to V7. All your query columns are filterable and sometimes (ok mostly) I can't remember which column was supposed to be filterable or not

RLJB

FYI, ability to set global defaults in config tool was raised with Vladimir at conference. Also for other things like setting your own default field width.