Multiple Hot Code files

[Max Lemesh]

Am I understanding correctly that I can only have one Hot Codes file loaded?
I had 2 different hot codes loaded, the codes themselves were also different.
But they didn't work and showed the error which didn't really made sense. Is this an issue with namespaces and I need to define separate namespace for each HC file?

When I remove one of them it workes fine. Simple code replacements do not have this limitation.

If that's the case could there some indication that particular hot codes are in conflict,
and more importantly can we have a checkbox to switch off and ignore certain CR or HC files without deleting them?
and also please can we have a Set Code replacement button in Ingest window, there is a spot for it at the bottom. next to variables.
We can also add it not save and copy windows too

[ahoward]

Did you investigate the lines where it states that there are duplicates?

[Max Lemesh]

It was probably the //?? At the end of hot code

[Max Lemesh]

From the manuals I know that this catch all //?? line is not required. So I can drop it in one of the hot code files?

[Max Lemesh]

Ok, it was not the //??

now it says the duplicate in on line 6

[ahoward]

Please send your code replacement files to support@camerabits.com so that I can review them.

[Max Lemesh]

Here, but it just text, so I'm not sure what is it PM doesnt like here

[Kirk Baker]

Max,

Here, but it just text, so I'm not sure what is it PM doesnt like here

Thanks for the files.  Currently, if you want to have multiple files with multiple hot codes and/or defaults, you have to put them into their own namespace, otherwise they're considered collisions.

I've started an internal discussion on the subject and if we change the implementation, I'll let you know on this thread.

-Kirk

[Max Lemesh]

on/off checkbox next to CR/HC files would be great addition to automatic reload

[Kirk Baker]

Max

on/off checkbox next to CR/HC files would be great addition to automatic reload

If there isn't already a feature request you should add one to the Feature Requests board.

-Kirk

[Max Lemesh]

Added to requests