Hi Sven,

have you checked (the different) usys.ini ?

In most cases the defaults are taken from these usys.xxx

SUccess, Uli

As far as I can see I have changed all the ini-files now, and I get the same result..

Hi Sven,

which uniface version are you using exactly (I will set up my own experiment area for this issue)?.

Success, Uli

P.S. what about deleting all these widget mappings "slider=uslider(...)" just for one unused widget?

I am using 9.3.02.01 (P209 0310_2). I am not sure what you mean by "P.S. what about deleting all these widget mappings "slider=uslider(...)" just for one unused widget?" /Sven

Just remove the definition of widget who are not used and check after.

Ah, yes I see. The thing is though that most are used, but some very seldom

Hi Sven,

it's only to see if we can get rid of these entries or if "the lab" had hardcode these widgets in the Tool Palette.

Success, Uli

It is quite possible to remove a widget, but it seems not possible to get rid of the default ones in the beginning like the fairly useless "Field"-widget choice. I guess I'll have to accept having those around plus the ones we mostly use as I wrote about earlier.. bummer..

Hi Sven,

the "Field" is not as useless as it may look like.;

Paint a "Field", rename it to a modeled field and it will inherit the modeled properties.
No need to find the "correct" widget in the first place.

Success, Uli

After all, the tool palette roots when uniface introduced widgets for the first time (UnifaceSix)
usability may look different nowadays

True (about the inheritance) but we don't use fields direct from model 99.9% of the time =)

FYI

I checked the GFP implementation and found that the tool palette of the GFP has a set of hard coded buttons which cannot be changed, And as you found out, you can configure the tool palette to a certain extend.

Jasper