Widgets

API documentation

1. Used OOM policies, Who is handling OOM? and Description of flow

It uses OP_STATUS on functions that is usually being called from core (f.ex. from the formscode).
Inputcode and related functions which is called from UI/input is raising a memorycondition without returning anything. (This is because input is coming from the platformcode which we don't want to take care of core OOM in.)

2. Heap memory usage

The baseclass OpWidget is derived in 2 classes to reduce binary size and heapmemory usage a bit when not using QUICK.

3. Stack memory usage

4. Memory ownership

Memory ownership is kept inside the widget.

5. Static memory usage

6. Caching and freeing memory

7. Temp buffers

No tempbuffer is used.

8. Memory tuning

No tuning possible.

9. Tests

The only memorytesting selftest is a leaktest for items in listbox and radiobuttons.

10. Coverage

There is no way to automatically test coverage.