Bug #1886
closedCustom signal declaration requires WMouseEvent at the end
0%
Description
When declaring a custom signal, the WMouseEvent type must be set at the end. Otherwise the first argument will be omitted.
A custom type signal of
JSignal6<WMouseEvent,String,String,String,String,String>
requires a JS call with the event for the first user argument. Otherwise the first argument will be lost (ie 'select-sheet').
var e=event || window.event; Wt.emit(Wt, { name:'optimus-dispatch', eventObject: Wt, event:e}, e, 'select-sheet', 'sheetId1', '', '', '');
However, when inverting the types:
JSignal6<String,String,String,String,String,WMouseEvent>
The required JS call does not need the event argument at all. WMouseEvent is properly populated.
var e=event || window.event; Wt.emit(Wt, { name:'optimus-dispatch', eventObject: Wt, event:e}, 'select-sheet', 'sheetId1', '', '', '', '');
Updated by Koen Deforche over 11 years ago
- Category set to Documentation
- Status changed from New to InProgress
- Assignee set to Koen Deforche
- Target version set to 3.3.1
Hey Jan,
You are correct. This was not documented properly (for JWt).
Regards,
koen
Updated by Koen Deforche about 11 years ago
- Status changed from InProgress to Resolved
Updated by Koen Deforche about 11 years ago
- Status changed from Resolved to Closed