Project

General

Profile

Actions
Copy link

Bug #757

closed
TA PL

JSignal1.createCall - Unexpected behaviour

Bug #757: JSignal1.createCall - Unexpected behaviour

Added by Thim Anneessens over 15 years ago. Updated about 15 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Pieter Libin
Category:
-
Target version:
3.1.10
Start date:
03/15/2011
Due date:
% Done:

0%

Estimated time:

Description

Hello,

Because of the defered initialization of _dynamic in JSignal1, the createCall method does not return an accured result if no listener has been added yet.

itemSelected=new JSignal1(this,"thumbnailClicked"){};
String call="function(){"+itemSelected.createCall(""3)"}";
// call="function(){}"
itemSelected.addListener(this, listener);
call="function(){"+itemSelected.createCall(""3)"}";
// call="function(){Wt.emit('o129','thumbnailClicked',0);}

Kind regards,
Thim.

KD Updated by Koen Deforche over 15 years ago Actions
Copy link
 #1

  • Status changed from New to InProgress
  • Assignee set to Pieter Libin

Hey Thim,

This actually a gotcha that also applies to Wt. The only solution possible would be to force the signal to be connected if createCall() is called. In fact, we could do this without actually exposing it, to keep the current effect of being able to use JSignals for pure client-side connections.

Pieter, this should be fix by not relying on 'isExposedSignal()' in the createUserEventCall(), both in Wt and JWt.

Regards,
koen

PL Updated by Pieter Libin over 15 years ago Actions
Copy link
 #2

  • Status changed from InProgress to Resolved

fixed in the latest git

KD Updated by Koen Deforche about 15 years ago Actions
Copy link
 #3

  • Status changed from Resolved to Closed
  • Target version set to 3.1.10
Actions
Copy link

Also available in: PDF Atom