[LucianMember]

Yes,
There are a couple of workarounds. 🙂

But you must have something out of the box in this framework.
A simple confirmation yes/no modal popup is just a common use-case nowadays.

Thx

[LucianMember]

Hi,

The following doesn’t work — taken from and tested in your example:

if (event.type === 'hide') {
                eventData += ', Dialog result: ';
                if (event.args.dialogResult.OK) {
                    eventData += 'OK';
                } else if (event.args.dialogResult.Cancel) {
                    eventData += 'Cancel';
                } else {
                    eventData += 'None';
                }
            }

Please provide a working sample with Ok and Cancel buttons that sets event.args.dialogResult properly. Or whatever other marker to indicate which button has been clicked.

Thx

[LucianMember]

The sooner, the better. 🙂
Then… because one of your selling points is the integration with Knockout, makes sense to pinpoint that as well.

Thx

[LucianMember]

That’s one mystery less.

Very much appreciated,
Lucian

[LucianMember]

I thought so, but I wasn’t sure about how to call setContent. Let’s say I’ve seen something like this before in the jQuery world. 🙂
Next… can we use the property initContent to achieve the same thing? How?

Now.. I have to mention a little something I found awkward.
I hope you’re already addressing the way jqx api is called and work towards offering to developers a simple unified way of doing it.
What I mean is sometimes we’re supposed to call a method like this: $(“#jqxwindow”).jqxWindow(‘setContent’, ‘abc’);
while in other cases we should be using this syntax: $(‘#tab’).jqxTabs().show();
Why is that? 🙂

[LucianMember]

That’s what I have expected indeed, although it’s not obvious in the source code.
I have a hunch how that might be possible but it’s better to ask for a POC. 🙂
If you could share a link to a demo would be great.

Thanks

[Author]

Posts