bluetooth_remove_paired.sh

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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.

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.

RESOLVED.

RESOLVED.

Sorry I meant parameters not arguments.

Sorry I meant parameters not arguments.

RESOLVED.

RESOLVED.

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

Thank you!

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 ob...

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.

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 pa...

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.

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

it has been fixed on the merge conflict.
748e088be863e08a1f8d12ff895c2525cd891e31

Why is vScript not a const?

Why is vScript not a const?

Why does not this function have an argument name?

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?

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

I would rather keep it for debugging purposes in case of error.

I would rather keep it for debugging purposes in case of error.

Do you still need this case?

Do you still need this case?

RESOLVED

RESOLVED

RESOLVED

RESOLVED

Thanks.

Thanks.

That is a very good question. As much as possible we have to put the #includes in the CPP files and not the header. The #include in the header will always be imported even if you don't compile the ...

That is a very good question.
As much as possible we have to put the #includes in the CPP files and not the header.
The #include in the header will always be imported even if you don't compile the code (only CPP is compiled in c, not the header) as opposed to just including when needed to compile in CPP.
This also helps the compiler to optimize the code better and faster to compile.
you only need to put it in the header if you inherit from the class defined in the class included or you have a variable/parameter defined of that file in the header.

Sometimes it's only the FS properties (changed to executable) of the file that git takes it as a change.

Sometimes it's only the FS properties (changed to executable) of the file that git takes it as a change.

These changes have been requested by SysEngz. Let them have a look and decide if it's what they want.

These changes have been requested by SysEngz.
Let them have a look and decide if it's what they want.

With Off and Complete being two different properties, should we have Complete say "Off" to the user and not "Complete?"

With Off and Complete being two different properties, should we have Complete say "Off" to the user and not "Complete?"

This file was changed but no changes are highlighted, any idea what happened?

This file was changed but no changes are highlighted, any idea what happened?