pcmhacking.net

Your own words clearly show you do not read my words ...

I'm not arguing, you are, I'm just pointing out facts!

Is it possible to add support for command line parameters, so flashing can be started from other program?
For example:
c:\pcmhammer\pcmhammer.exe /WRITECALIBRATION c:\temp\mymodifiedtune.bin

I am thinking about adding button to Universalpatcher Tuner-window, so I can change tune and then click "Write", without jumping between programs.
Maybe automatic saving + backup in background...

I will do this for my own use anyway, if not added to official Pcmhammer

If you do it anyway, please do send a pull request on github I guess it'd need to pop up the config box if the interface isnt configured or it cant initialize it. Some kind of workflow. I would assume the gui would still pop up so you can see what its doing? or are you thinking CLI output?

I like this idea a lot. If there is no interface configured we could pop up the interface picker dialog box. It gets more tricky if the user has configured an interface that is no longer attached to the PC or something like that. Or if the file isn't present at the given path - surely no such bug would ever happen with Universal Patcher, but other people eventually might try this too.

And then there's the question of what to do if there's already an instance of PcmHammer.exe running (or worse, doing something). I know there's a way to send a message to the already-running instance, but I haven't looked into that for a long time.

For the first iteration, the easiest thing would probably be to just launch the UI and put it into the same state as if the user had clicked the Write Cal button and picked the file. And encourage users to close the app when the write is complete. We can make it more sophisticated over time.

I dont have permissions to send pull request.

Edit: Code removed

This is the most common mistake made when trying to contribute to an existing Github project ...

You must first have a place where you have permissions in order to push changes, so the proper steps are simply stated like so,
Fork a repository, clone that fork local, create a local branch, make your modifications, commit the changes, push that branch to your fork, then create a pull request from your fork ...

FMI Click: How to Git with PcmHacks in Visual Studio

Gampy wrote:This is the most common mistake made when trying to contribute to an existing Github project ...

You must first have a place where you have permissions in order to push changes, so the proper steps are simply stated like so,
Fork a repository, clone that fork local, create a local branch, make your modifications, commit the changes, push that branch to your fork, then create a pull request from your fork ...

FMI Click: How to Git with PcmHacks in Visual Studio

Thank you.
I think I have done it now

joukoy wrote: Thank you.
I think I have done it now

I did not review the code, but the Pull Request looks awesome!

Still trying to understand github, removed previous pull request (I think) and created new.
There must be better way to check if device is ready, than checking if "Write Calibration" -button is enabled, but it seems to work...

normally you would make a branch on your copy of the tree, which I think you have done, and you can create the merge request on the branch, and it will track further changes without you doing anything. so your local work flow becomes do your edits, do a test, commit the changes with a message about what changed, then push that to github. at this point that new change stacks on top of the others, and we merge your request, normally also deleting our copy of your branch and its done. Mostly I work with gitlab, but I think its the same.