Avoid Tips Window Opening via API When Using ProjectManager and FrontEndTool

[VincentDary]

Hello,

I am using a custom rewrited GhidraRun which instanciates a ProjectManager and next a FrontEndTool, during this step the Tips Window is poped, I would like to avoid the Tips Window opening, of course via the Ghidra API. Any way ?

[dragonmacher]

I don't think we have any programmatic way of doing this. But, you can add a value to the preferences file to turn them off. The preferences file can be found at {user home}/.config/ghidra/ghidra_{version}/preferences

Add/edit this line:

SHOW_TIPS=false

[VincentDary]

@dragonmacher thank for the remember about this option but I was hoping an easier and more portable way to do this via the API. I prefere to avoid using path and user config file writing for this kind of stuff, in my context I am running a custom Ghidra app based on GhidraRun without to modify any user preference minus the Window tips, but not in a persistent way.

Maybe you have a hack to shoot the window at runtime :) ?

[dragonmacher]

You can try turning them off programmatically via the preferences. As your application is starting:

Preferences.setProperty("SHOW_TIPS", Boolean.toString(false));
Preferences.store();

The plugin that shows the dialog is going to read this property.

[VincentDary]

@dragonmacher Thank you very much, In my context It works very well ;) since I can call this code just after Application.initializeApplication() before instanciate ProjectManager and FrontEndTool.

After a test, I have seen that is persistant in the preference user file, so I would like to restore the value when Ghidra app is quitting to have a non persistent behaviour, What is the best way to handle Ghidra application quitting event ?

[dragonmacher]

What is the best way to handle Ghidra application quitting event ?

I believe your application launching code will block until the application is finished. If so, then you can put the code after that. If that is not getting called, then you can try adding a Window listener to the main frame and do the work when the window closes.

[VincentDary]

Thank's for the tips :), no my launching application code is not blocking, , I have followed the same style as GhidraRun which launch the program manager (and optionally a project) and said good by, but with an extra initialization code which run a FrontednTool, start multiples plugin tools like the CodeBrowser and other stuff...
I will try a window listener on the FrontendTool main frame, seems a good idea, thanks.

[VincentDary]

@dragonmacher Other thing in the same style of the SHOW_TIPS, I have tried to deactivate the help opening at first start via setting to false the property SHOW.HELP.NAVIGATION.AID, but seems to not work, the value is get in DockingHelpBroker(), maybe the help is open in another place at first start.

[dragonmacher]

I can't say for sure without debugging it. You are really rolling your own adventure here, exploring uncharted uses of the code base.

[VincentDary]

@dragonmacher, ok, thank's for everything.

Yes your are totally right, I am exploring uncharted uses of the code base, but it seems to work very well, I hope it won't be too difficult to maintain with the future Ghidra versions.