Losing changes on rebuild

[Spico]

I want to improve the widgets for KNX but on each rebuild I lose the changes i have implemented.

how can I preserv my changes.

[bkenobi]

Are you referring to changes you have made to the source, compiled, and overwritten stock files with?  If so, you would either need to compile your own version each release or keep a backup of the files you customized to copy in after each update.  If the changes you make are ones that would be suitable for all users, you could also consider forking the main code and submitting it for incorporation into the main branch.

[Spico]

I have submitted some code already, but each time i rebuild the solution, it resets the complete environment.
how can i avoid losing the changes i have made here. for example the adresses of som KNX nodes like a lamp.
as also the parameters i need to configure to find the eibd server and so on, also the installed packages i need to work with like KNX

[bkenobi]

If you modify a builtin app (e.g. smart lights) and then update HG, the module will be overwritten. I'd recommend creating a new instance and modifying that so updates won't overwrite it.

[Spico]

What exactly do you mean by instance?

a new module?

[bkenobi]

It must have a different program ID.  If you export the built-in app and then import it, you will have a second copy/instance of the same app but the new one will have a different program ID.  So, when you update HG next time the new instance won't be affected by the update.  If you want to tweak the code, you need to make the change to that new version.

[rainsee]

I'd recommend creating a new instance and modifying that so updates won't overwrite it.