Missing disambiguation pages for GUI members

**Version of the documentation in which you are reporting the error**
2026-08-28 main:bcc3cd348b

**Describe the technical error**
We currently do not have disambiguation pages for GUI member names that are used for two of the three member types (object, event/method, property). If there are clashes, F1 simply prefers objects and then event/method, never showing a property.

This can lead to great confusion. E.g. a user might have a [`Clipboard` object](https://docs.dyalog.com/21.0/object-reference/objects/clipboard/) and want information about its [`Text` property](https://docs.dyalog.com/21.0/object-reference/properties/text/), but pressing F1 on `Text` gives the documentation page for the completely unrelated [`Text` object](https://docs.dyalog.com/21.0/object-reference/objects/text/).

We therefore need disambiguation pages for the following GUI member names:

* Event vs Property:
* VScroll
* HScroll
* Event vs Object:
* Scroll
* Locator
* Timer
* Property vs Object:
* Text
* ImageList
* Font
* Bitmap
* Icon
* Cursor
* Text
* Bitmap
* Metafile

This will require changes to the F1-help table too.

Start with the existing GUI member pages linked in the issue, then locate the F1-help table that controls member-name lookup. Add disambiguation pages for the listed event, property, and object name clashes, and update the table so F1 can reach each relevant member. Verify that names such as Text, Scroll, and VScroll resolve without preferring the wrong member type.

Written by the indexing model from the issue text.