Make sure the button report set masks use OR in all circumstances, to prevent...

Make sure the button report set masks use OR in all circumstances, to prevent user confusion. While the first set of the buttons report item can be a direct assignment, it is not immediately clear to new developers why this is the case.

Demos/Device/ClassDriver/KeyboardMouse/KeyboardMouse.c

@@ -217,7 +217,7 @@ bool CALLBACK_HID_Device_CreateHIDReport(USB_ClassInfo_HID_Device_t* const HIDIn
 		  MouseReport->X =  1;
 
 		if (JoyStatus_LCL & JOY_PRESS)
-		  MouseReport->Button  = (1 << 0);
+		  MouseReport->Button |= (1 << 0);
 		
 		*ReportSize = sizeof(USB_MouseReport_Data_t);
 		return true;		

Demos/Device/ClassDriver/Mouse/Mouse.c

@@ -155,7 +155,7 @@ bool CALLBACK_HID_Device_CreateHIDReport(USB_ClassInfo_HID_Device_t* const HIDIn
 	  MouseReport->X =  1;
 
 	if (JoyStatus_LCL & JOY_PRESS)
-	  MouseReport->Button  = (1 << 0);
+	  MouseReport->Button |= (1 << 0);
 	  
 	if (ButtonStatus_LCL & BUTTONS_BUTTON1)
 	  MouseReport->Button |= (1 << 1);

Demos/Device/ClassDriver/VirtualSerialMouse/VirtualSerialMouse.c

@@ -217,7 +217,7 @@ bool CALLBACK_HID_Device_CreateHIDReport(USB_ClassInfo_HID_Device_t* const HIDIn
 	  MouseReport->X =  1;
 
 	if (JoyStatus_LCL & JOY_PRESS)
-	  MouseReport->Button  = (1 << 0);
+	  MouseReport->Button |= (1 << 0);
 	  
 	if (ButtonStatus_LCL & BUTTONS_BUTTON1)
 	  MouseReport->Button |= (1 << 1);

Demos/DualRole/ClassDriver/MouseHostDevice/DeviceFunctions.c

@@ -123,7 +123,7 @@ bool CALLBACK_HID_Device_CreateHIDReport(USB_ClassInfo_HID_Device_t* const HIDIn
 	  MouseReport->X = -1;
 
 	if (JoyStatus_LCL & JOY_PRESS)
-	  MouseReport->Button  = (1 << 0);
+	  MouseReport->Button |= (1 << 0);
 	  
 	if (ButtonStatus_LCL & BUTTONS_BUTTON1)
 	  MouseReport->Button |= (1 << 1);