WebBoxes and Recordsets have IDs that must be unique in the
whole application. This brings some difficulties for big
applications or when including an external module (prepared
by somebody else) because there is a chance that two weboxes
(for example) have the same ID. Maybe this can be solved by
requiring them to be unique only in the context (the scope)
in which they are used.
WebBoxes and Recordsets have IDs that must be unique in the
whole application. This brings some difficulties for big
applications or when including an external module (prepared
by somebody else) because there is a chance that two weboxes
(for example) have the same ID. Maybe this can be solved by
requiring them to be unique only in the context (the scope)
in which they are used.
For example:
------------
webobj x
|
+--> webobj x1
| |
| +--> webobj x2
|
+--> webobj x2
| |
| +--> webobj x1
| |
| +--> webobj x2
|
+--> webobj x3
In this case there should be a way to access the webobjects of
the page like this:
page->x->x1->x2
page->x->x2->x1
page->x->x2->x2
(Currently they can be accessed only like this:
page->x, page->x1, page->x2,
which does not allow two webobjetcs to have the same name (or ID).)