Project

General

Profile

Bug #1886

Custom signal declaration requires WMouseEvent at the end

Added by Jan Goyvaerts over 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Documentation
Target version:
Start date:
04/30/2013
Due date:
% Done:

0%

Estimated time:

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', '', '', '', '');

#1

Updated by Koen Deforche over 8 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

#2

Updated by Koen Deforche about 8 years ago

  • Status changed from InProgress to Resolved
#3

Updated by Koen Deforche about 8 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF