All Answers

Yes, it works! Great! thanks.

Alex

Yes you are right. I tried it in the chrome console and I assume it worked, but “this” refers to the button as you said.

Try the script below attaching to the button that you want to click, otherwise I will set up a test tomorrow:

this.addListener("execute", function(e){

   this.getParent().upload1.upload();

});

Assuming that upload1 has the same parent as this. Otherwise you need to tell the button wich upload control to
use, which is also possible.

Please send me a screenshot, I’d like to make sure I understand what the requirement is.

Hi Luca,

I can’t make it work, and I suppose it has to to with “this”. If I set the javascript to the button, then then “this”, I suppose, refers to the button. But the button does not have an upload control, the upload control belongs to the parent panel which contains both the button and the upload control. I tried also to set the javascript to the parent panel (usercontrol) like

this.button.addListener(“execute”/”click”, function(e) { this.uploadControl.upload(); }

Also tried

function(e) { this.uploadControl.fireEvent(“Uploaded”); } (inspired from your example about the default button).

But no result… The upload control is visible and I am using your experimental build…

Alex

Re – Tabs – Even if you remove all the tabs and leave one. You are still left with One tab header. Yes we can work with this but there are many times when we do not want to see the tab header.

Looking forward to the other updates.

Thanks, Luca, I’ll give it a try.

Alex

Forgot about the filedialog. The FileDialog, FontDialog, ColorDialog, ColorPicker system dialogs are not implemented yet but will be there. We are first implementing a virtual file system capable of browsing:

• Server file System (rooted)
• Amazon S3
• Google Drive
• Microsoft OneDrive
• Custom Implementation (database, for example)

The FileDialog will support multiple customizable roots. You can show to your users a root folder on S3 and a root folder on OneDriver, for example. The Wisej.Core.IFileSystemProvider is public and anyone will be able to add more providers.

Best,

Luca

Hi Luca,

Yes, I am indeed using the experimental build… I’ll wait for your fix-all build then.

Best,
Alex

Tabs cannot be hidden, they can be removed or disabled. The Visible property (hidden) for the TabPage refers to the page being selected and the panel being visible. It’s the same in Winforms and should be the same in VWG.

I have to see if we can add either a new property or a method but I’m not sure about it since it’s pretty standard behavior to remove and re-add a tab when hiding it or showing.

Best,

Luca

Hi Cris,

Thanks for the sample. I haven’t tried it yet.

But about the validation in general, we can’t block the cursor from changing the focus, otherwise you’d have to wait for a server request/response everytime the user tabs around. That’s why we also added the InvalidMessage and Invalid property as well as the ErrorProvider component.

Basically with Wisej you can validate in 3 different ways (this will be a new topic in the docs):

• Cancel the Validating event: Wisej will force (it may fail if you keep clicking due to timing issues :)) the invalid control to gain the focus back, it will automatically set the Invalid  property to true and you may optionally set the InvalidMessage tooltip.
• Do not cancel the Validating event. But you can set the control to Invalid and set the InvalidMessage. This is more “web-like” where the actual full validation is executed on save but you show the invalid state.
• Use the ErrorProvider to display an error icon next to the invalid control, similar to the method above.

HTH

Best,

Luca

It’s probably because you are using the experimental build I sent you to test the performance issues. It works with the build I have which solved the issue with your test app when adding invisible controls. However, there is a different issue related to the fix for the animated gif, the encoding is now wrong and uploaded pngs show as a black box using the sample because System.Drawing changes the RawFormat to MemoryBitmap. Fixed as well in our development build.

Hi Alex,

It is possible from the client side only. Browsers block any attempt at initiating the upload action when executing javascript that was not initiated by a direct user action, ie. a click.

If you drop the JavaScript extender you can add this script to the button that you want to use:

this.addListener("execute", function(e){this.upload1.upload();});

Remember that if upload1 is not visible and you are using the experimental build I sent you, it will not be sent to the client. You have explicitly call this.upload1.CreateControl();

HTH

Best,

Luca

I’m not sure, but I don’t think Global.asax will work since Wisej doesn’t create an ASP.NET session.

Yep, noticed that too. The first day of the week is also automatically localized but we had a mismatch between the code used in .NET and the code expected by the JavaScript library: .NET is passing en-US while the js code is extracting the territory using an underscore (en_US).

Will also add the FirstDayOfWeek property to override the localization.

Hi Luca,

That’s great. It seems that the framework is very flexible and it’s always ready for an enhancement.

Regards.

Thank you, Luca! TCH ! (This Certainly Helps). Actually my main question was whether the Global.asax is supported in Wisej… I suppose I could have tried before asking.

Alex

Great! Thank you, Luca!

Alex