WARP Generate Signature File Wants to Save Inside A Project in an Internal Directory

[utkonos]

Version and Platform (required):

• Binary Ninja Version: 5.1.7363-dev
• OS: macOS
• OS Version: 15.4.1
• CPU Architecture: x64

Bug Description:
Saving a new signature file using WARP initially tries to save the file to a location inside the internal directory structure of a project.

Steps To Reproduce:

1. Open any database that is part of a project.
2. Right click -> Plugins -> WARP -> Generate Signature File
3. Note that the save file dialog is offering to have you save the signature as a GUID filename in an internal location under the hood of the project.

Expected Behavior:
Signatures directory in the user directory

Screenshots/Video Recording:

[emesare]

Had to swap out the interaction handler for another external file picker, likely want to fix this with #6491 maybe generation should get another prompt to ask the user if they want to save the signature to the user signature directory or to the project they are in? Not sure.

[utkonos]

It would be really cool if WARP used the interface that Type Archives use with "Create Type Archive" when operating in the context of a project. It still has a "Save External File..." button that could default to the user's signature directory.

[emesare]

It would be really cool if WARP used the interface that Type Archives use with "Create Type Archive" when operating in the context of a project. It still has a "Save External File..." button that could default to the user's signature directory.

Good point, I think #6491 should require that we have that default directory (in WARP's case, the users signature directory) be used with the "Save External File..." button.

[utkonos]

This widget probably needs a better default location when used in the context of a project:
#6774

[utkonos]

A WARP signature file that is saved to a project should also be used in databases in that project when analysis is done