Bug #761

message values are recalled in views when switching models

Added by Pascal Baltazar over 8 years ago. Updated about 8 years ago.

Status:ClosedStart date:2011-04-23
Priority:HighDue date:
Assignee:Théo de la Hogue% Done:


Category:-Spent time:-
Target version:MVC for 0.6
Branch: OS:


when switching between two models on a view, the last values that have been sent to messages are output by the jcom.views

unless I'm missing something, this should'nt happen

see attached patches

Archive.zip (2.31 KB) Pascal Baltazar, 2011-04-23 12:00 pm


#1 Updated by Théo de la Hogue over 8 years ago

Actually it's more a way it works than a bug,
I call the "refresh" method of the TTViewer class
each time the adress it binds changes... It make sense
for me but we can separate the mechanims if needed.

However this would implies more patching for users
because each time the model/adddess will change you
will need to send the refresh message to each jcom.view...

any idea about the user interface for this features ?

#2 Updated by Théo de la Hogue over 8 years ago

answering to this email :
"maybe some people here have an opinion on this subject ?

in my understanding, messages (instead of parameters) don't have any persistence - they just exist at the moment when they are emitted...
and thus shouldn't be refreshed...

maybe I'm misunderstanding, though...

(and BTW, if I'm wrong, the very simple workaround is to use a jcom.receive instead of jcom.view)

opinions ?


Ok I have misunderstood the request : this have to be only done for jcom.view which binds on "messages" !
so It make perfect sense for me now...

I'll take care of this soon as possible.

#3 Updated by Théo de la Hogue over 8 years ago

  • Status changed from New to Resolved

now the value is refreshed only for jcom.view binding parameters or returns

#4 Updated by Pascal Baltazar about 8 years ago

  • Status changed from Resolved to Closed

works now !

Also available in: Atom PDF