Description
Create method or property to detect what type of widget(grid in my case) is used for entity
Use Case
Fields in Grid widget has specific behavior, some functionality are not supported for fields in grid, some functionality are added(column hidding, column size). My specific problem is ^Zoom functionality and security. Grids needs another implementation .
Importance
Type
Proc Code
Operating System
Not Applicable
Status
Open
Seconded.
I currently deal with this using a .seq file table generated by a program with access to the IDF entities, I can help with converting this for you if you would like.
Iain
Is the already available function $entityproperties() what you are looking for?
If not, why?
Gianni
giani, $entityproperties() returns grid only properties which hasn’t default values
So it isn’t possible detect grid by this function
Maybe this helps?
http://unifaceinfo.com/forum/uniface9/zoomsmod-detect-grid-widget-use/#p6050270
To harvest informations like the one above, the DUR project (dITo Uniface Reflection) uses a 2phase compile.
After the first compile and cleanup, the registry is insepcted and a lot of information
is written to an include proc with the name of the component.
This include proc is included in the DEFINES trigger of the component so it can be used in all code locations.
When GRID can be detected from the repository, it’s a piece of cake to add that information.
This way, you can extract all kind of info you need for your implementation (and you can have it NOW)
Greetings from Frankfurt/Germany, Uli
Would be nice to have it for field widgets as well. I do not think it is currently possible to get a field’s widget at runtime.
Hi dleveque,
the DUR concept can handle your request as well,
because the information collected is in your own hands.
Pretty easy to adjust to your needs and pretty fast as well.
and … you can have it NOW !!!
Greetings from Frankfurt/Germany, Uli
Uniface developer should be able to get information about widgets by native Uniface proc function instead of implementing this by workarounds.
Other wish that is related: http://unifaceinfo.com/fieldinfo-improvement