There's not much significant difference between the two except - The one I
suggested just refreshes the entire window (listView+ other extra items on
the UI) but the one which you wrote would just refresh the listView. From
the end user perspective , you won't realize the significance since
listV
~
}
to args.response.success()
like this:
==
success: function(json) {
var item = json.createaccountresponse.account;
args.response.success({
data: item
});
}
==========
Jessi
Hi Pranav,
That worked nicely. Thank you.
What is the advantage of
$(window).trigger('cloudStack.fullRefresh');
over
$('.list-view').listView('refresh');
On 25 July 2013 12:31, Pranav Saxena wrote:
> Hey Ian ,
>
> So you got to code this up for fetching the latest state for the listvView.
> Wh
Hey Ian ,
So you got to code this up for fetching the latest state for the listvView.
What you have done is also right but I would suggest you try something like
this in your "success block" -
$(window).trigger('cloudStack.fullRefresh');
Let me know if this solves your problem.
Thanks,
Pranav
Hi,
I've modified the "add account" screen to use a custom ui. The custom
UI displays a table of all LDAP users along with the required and
optional input fields.
When I add the user the user doesn't appear on the table of users
until the page is refreshed.
What is the correct way of handling th
