Which edition is loaded?

[Hal]

I searched the forum, but didn't see this problem mentioned anywhere, so, if the answer is obvious and I wasted your time, I'm sorry.

When you use the menu option "Browse Editions" (i.e. via rt click on a class in the Visual Organizer or via rt click on a method name in the method list of a browser), how can you tell which edition is the active one?

If I drill down to the editions of a class or method in TrailBlazer, the active edition is marked with an *. But all other windows that display class or method editions don't seem to identify the active edition.

If it makes any difference, I am using version 7.5.1 under Windows.

[Eric Clayberg]

The loaded edition is shown with a small blue ball next to it as seen here...

[Hal]

what about the currently loaded method in the view you get when you browse the editions of a method?

[Eric Clayberg]

what about the currently loaded method in the view you get when you browse the editions of a method?

It uses the same small blue ball.

[Hal]

I see everything works correctly in when I use a virgin ABT.ICX, so something in our maps must be causing it to work not for us.

We see a red dot beside EVERY edition after loading out maps. I have traced the problem to the loading an edition of EtTools that overrides #checkPassword:in: (to simply answer true).
#checkPassword:in:
^ true

I can't see why that change would cause us not to be able to see the active edition.

The "Explain Prerequites" menu options in the Manage Applications window also disappear when we load that app, too. I can't figure that one out either. Got any ideas?

[Eric Clayberg]

Got any ideas?

If you are loading a modified version of a base app, I have no idea what its effect might be. All bets are off at that point from my POV.

I would suggest re-loading the unmodified base version and sticking with that.

[Hal]

reloading the original version of the app does not return the system to how it used to be, so something else must be happening as a side effect of loading the app.

At least we know the action we are taking that is causing the problem.

[wembley]

The development tools applications set the browser mapping when they are loaded -- for example, EtTools class>>initializeAfterLoad, AbtToolsAdditionsApp class>>updateBrowserMappings, or StsPowerTools class>>setBrowserMappings. If you loaded a different EtTools, you overrode the browser mapping set in StsPowerTools.

[Hal]

Thanks for the explanation.

Reloading the 7.5.1 edition of the StSPowerTools application gave us back the "explain prereq" menu options and we can now see the blue ball beside the active method edition.