Force deploy of file currently open

[Petr Švestka]

While deploying "on save" checks either timestamp or the hash of content(?), it make sense to add a way how to enforce deployment.

Example: I need to merge changes from a sandbox to another. I have files from the first sandbox and a project with the files of the target sandbox. If I just copy over the files with those with the change, save doesn't trigger deploy all the time.

If I had a button "Enforce deploy of this file", it'd make my life a bit easier.

[Scott Wells]

Petr, I'm planning to address this in issue #83 so that if you perform a full deployment (CTRL+SHIFT+ALT+F10), one new option for deployment context (currently module, module + dependencies, and project) will be current selection (current file, selected node in the Project view, etc.). Because of the nature of this action, the result will be a force deployment.

If you feel that properly addresses your request here, we can resolve this one as a duplicate of #83. If not, please feel free to add additional details on how your request differs.

[Petr Švestka]

Duplicate of #83.