Could we have method access to the ‘controller’ property of a table?
The immediate use to me would be that I could use a main UI form, which normally has a controller, in a formAsDialog, without showing the navigation buttons that are on the controller.
(Scenario: the user is choosing records from form b to relate to form a. Desired record hasn’t been entered yet in form b. User clicks button to add a record to form b, and gets a new formAsDialog. When the record is created, it is added to the selections in the first formAsDialog.)
This would have other uses, though: a user could hide/show the navigation bar (the way one would hide/show status area in FMP) to gain some screen real estate. Also, a user (or client) could choose a controller as a preference, and via methods we could load the desired controller as each form displayed.
In any case, I doubt this would be high on the wishlist, but since I came across it I thought I’d share. Anyone else find this prospect interesting?