In the firmware we add a TODO to be able to grep them easily and make sure we do not forget any commented code.
RESOLVED.

RESOLVED.

RESOLVED.

Sorry I meant parameters not arguments.

RESOLVED.

RESOLVED.

RESOLVED

RESOLVED

RESOLVED

Thank you!

A very important concept.
I refer you to the Qt connection concept for detailed information.
https://doc.qt.io/qt-5/signalsandslots.html
The idea is, the connect has 4 parameter
1 - Signal owner object
2 - Signal member function
3 - Slot owner object
4 - Slot member function
When the signal owner is emit-ed, the slot owner will call its slot by the passed parameter from the signal function.
It is very important to use the connection concept, in opposed to the simple call, in case the signal owner and slot owner, objects, are in two different threads.
It is the Qt way of thread-safe calling.

Ummm,
Haven't ever thought about it, this is a very good point.
Will look into it, since the actual friend class will not ever be available in the production code.

if the parameter is not used, the name will not be specified so the compiler won't complain about the parameter not being used.

Note the difference between parameters and arguments:

• Function parameters are the names listed in the function's definition.
• Function arguments are the real values passed to the function.

The vScript parameter will accept the arguments which will be changed in the function, so has been defined as a reference with no const.

it has been fixed on the merge conflict.
748e088be863e08a1f8d12ff895c2525cd891e31

Why is vScript not a const?

Why does not this function have an argument name?

I understand that the friend classes are for dev testing, are we planning to disable them later during the release?