Dialogarguments is null or

Richard Cornford. Jc wrote: The "this. The - form - property of form controls is a reference to the containing form or null if the control is outside of the form. I typically use a different way to reference objects. It is a Microsoftism that, while supported by some other browsers, is not universally supported. A standard bracket notation property accessor:- document. It is the cross-browser formulation to use in this context the Microsoft parenthesised version should never be used, least it becomes a bed habit that makes cross-browser scripting seem harder than it really is.

This discussion thread is closed Start new discussion. Similar topics. NET Framework. NET Add-in. K last post: by. Remove maximize option from MS word document window. Are there any ideas on a fix?

Should I submit a bug report? Cheers, Kris. CKEditor 4. Forums CKEditor Support. Last post. Posts: 4. Error when opening dialogs. Hi, I'm using version 2. I even tried invoking the dialog from JScript which most of the examples seem to do , or casting thisXDocument to an object which one example did and sort of made sense , and no luck. What exactly is this dialog supposed to be accomplishing?

Yours seems to be a pretty rare question, so might I propose using the InfoPath form to get the data you want, or if you must use a dialog, to use a WinForm dialog instead? Either of those approaches carries the benefit of not having to make your form full trust. Reasonable questions and suggestion Jimmy - thanks. The requirement isn't all that unusual in fact I've seen several posts from people addressing the same need - it's obtaining authentication data from the user if an integrated authentication doesn't work.

The full trust is actually needed for other reasons the main one being that the form makes a call to a web service. Your suggestion of using a Windows form is a good one and one that I've seen mentioned in one other place. I haven't tried this before from InfoPath but presumably it's just a matter of creating an assembly with a public method that launches the WinForm, captures the data and returns it to the caller.

I'll give that a go - has to be easier than all the nonsense I've tried so far to get this HTML dialog to work. Creating and using a WinForm in an InfoPath project is a piece of cake. You don't need a separate assembly. Drag in controls, expose their values with some properties, and add OK and Cancel buttons that set the DialogResult property and call this.

My window. What gives? If this is the case, it seems as though there are restrictions against accessing dialogArguments and returnValue. Check out the comments on this previous answer for example. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 9 years, 2 months ago. Active 9 years, 2 months ago.