Community
Participate
Working Groups
An important item on our list is gotoMarker() support. In order to support gotoMarker() in our graphical editor, we often cause an item in our editor to be selected, which causes the appropriate property sections to be displayed in the properties view, but after that, there is some work required to ensure the correct tab is visible and the correct widget on that page gets focus, for example. Some of this is a bit hairy currently since it's hard to query for the complete set of visible tabs/sections, and some simple additional API would make this much easier for us.
Do these belong to you? Forward as necessary. Thanks,
Correct me if I am wrong, but why is this not a duplicate of Bug 119085 ? You say your gotoMarker() selects elements in the graphical editor, which displays tabs and sections. Now you want to make use of a proposed active tab and section setter to bring the UI you need into focus.
Well, this one might depend on the other but does not really mean it is a duplicate. If you make it a duplicate it means everyone using the properties framework will need to implement goto marker in some way but if the basis is already in the framework, it means less code for everyone else to implement.
OK, so if the tabbed properties view implements IGoToMarker, what is your propsal for the IMarker ?
The last entry on this bug was a question for the reporter. Is this request no longer useful, or is there some other reason why the conversation stopped?
It would still be very useful. Basically the view should handle IGotoMarker but every page would need to contribute some kind of logic that identifies if the marker belongs to it or not. The framework then would give focus to the first page that says so (maybe by delegating the gotoMarker() call to that particular page.
This feature was on an IBM internal list for 3.4. No further follow up occurred since July 2007.
It would still be useful.
(In reply to comment #2) > Correct me if I am wrong, but why is this not a duplicate of Bug 119085 ? > > You say your gotoMarker() selects elements in the graphical editor, which > displays tabs and sections. > > Now you want to make use of a proposed active tab and section setter to bring > the UI you need into focus. > I am back to why a view needs to provide an implementation for IGotoMarker . Clearly it is the editor which implements IGotoMarker and it will need to reveal the tabs and sections in the properties view. This would be solved by Bug 119085 . And there is no reason why you cannot extend TabbedPropertySheetPage and make it implement IGotoMarker . Right? Why does the framework *have* to provide an implementation for IGotoMarker?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
