All Answers

I have understood your solution, bat i can’t find “theme builder” application. i have installed version 2.1.60.

Moreover I haven’t understand how add a theme to my solution.

Sorry for question.

Nello

Hi Page,

How did you create InheritedDataForm? It looks like the sizes (and locations) are all off.

I just tried by:

1. Right-Clicking Project
2. Add -> New Item -> Wisej 2
3. Select Inherited User control
4. Select BaseDataForm

This gave me a control that was identical to BaseDataForm (superclass), with flowLayoutPanel1 in the appropriate place.

The reason InheritedDataForm probably looks okay in your browser is because it’s larger than the Designer and the anchoring keeps it at the bottom of your screen.

I think if you try creating a new inherited control with this method it will solve your issue!

Let me know!

Best,

Levie

Thank  you

i will try

Solved updating the javascript html2canvas.js of the extension

bye

Add Application.Update(this); after ShowLoader = true otherwise the update doesn’t go back until the request is finished. It works only if WebSocket is enabled.

Another option if to show the loader and set the AspNetPanel1.PageSource in the Appear event of the page or form. This way everything is loaded in the browser before loading the aspnet panel.

#2269 is included in Wisej release 2.1.66

Best regards
Frank

Thanks,

this will be fixed in our next build. Issue number is #2269.

Best regards
Frank

Hi Anz,

Did that link help to solve your issue?

Let me know!

Best,

Levie

VWG used a completely different client-side system based on unreadable XSLT used to transform XML into a large HTML string then inserted in the browser using innerHTML. The first creation of the whole page was basically a large HTML string. Subsequent updates used smaller snippets of XLST again used to transform XML into HTML strings used to replace the HTML of the control to update. That’s why textboxes were losing the focus when a property changed and resizing a column in a grid with many rows and columns was painfully slow. Apart from the fact that it was close to impossible to maintain and extend. I worked on the VWG source code for years.

Wisej instead uses a different approach, in line with any other Single Page Application (SPA) system out there today. Every control is a javascript widget object, which is rendered by accessing the browser DOM through a FastDOM system that minimizes the access to the browser’s DOM. Having a real javascript object system has all the benefits that you can imagine, but obviously creating hundreds of objects in the browser is slower than creating zero (VWG didn’t have any javascript class, just a large flat set of functions).

This is to explain that if you compare a plain HTML page (i.e. VWG)  with a page composed with objects (Wisej) the HTML page is faster at first creation. Subsequent work with the application instead it’s faster when you just change properties instead of recreating the HTML every time.

In some of our projects that were on VWG we were able to reduce the initial gap substantially (probably to a 30% difference) while the subsequent interaction was always faster and way more reliable in Wisej.

There are some things you can check:

• hidden controls that are made hidden after Form.Load. Wisej optimizes the creation of client widgets and doesn’t send them to the client until they are made visible the first time. But if the form is loaded and then the controls are set to Visible=false they still reach the client.
• comboboxes or listboxes with many items, you can make them use virtual scrolling or enable the lazy loading option.
• too many color or font assignments when the value is the same as the inherited value, it still causes the browser to resolve the color (VWG didn’t have a color system) and the font (VWG didn’t have a font system), etc.

Contact me at support at iceteagroup.com and we can look in more details at your app.

Just use

AspNetPanel1.PageSource = “Recepcion\Ingreso_BusquedaASP.aspx”

No need to call Update and no need to use ShowLoader in the same request/response. In web applications the browser is updated only after the server is done.

I don’t understand the question. Can you attach a small runnable sample that shows the issue you need to solve?

In general, I suggest you use Newtonsoft or the Microsoft JavascriptSerializer to handle JSON.

The Wisej JSON serializer is a lot faster than the others but it’s tailored for Wisej and it serializes property names using camel casing (which is the standard in Javascript). That’s why you see “dISCOUNT”. You can change its behavior using the WisejSerializerOptions or the built-in JSON class.

AcceptButton causes the buttons to be clicked when pressing Enter. CancelButton causes the button to be clicked when pressing Esc.

In WinForms they also automatically close a form only when created using ShowDialog() while they do not close a form when created using Show(). We decided early on not to duplicate many little inconsistencies like this one. The action to take when the AcceptButton (or CancelButton) are clicked with Wisej depends on the app. All you need to do is add a Click event and call Close() if that is the behavior you need in the app.

I checked the log, there are errors, please see below.

wisej.js?v=2.1.58.0:63569 WebSocket connection to ‘ws://localhost:60754/app.wx?url=http://localhost:60754/&sid=3ewjiois2ixhqoueevecdth4’ failed: Error during WebSocket handshake: Unexpected response code: 200
WisejCore.sendWebSocketRequest @ wisej.js?v=2.1.58.0:63569
qx.js?v=2.1.58.0:174522 003376 Wisej: WebSocket Error
qx.log.appender.Native.process() @ qx.js?v=2.1.58.0:174522
dx.all.js:126 Uncaught Error: E1041 – The ‘devexpress-gantt’ script is referenced after the DevExtreme scripts or not referenced at all. See:
http://js.devexpress.com/error/20_1/E1041
at u (dx.all.js:22)
at Object.Error (dx.all.js:22)
at i (dx.all.js:126)
at t.value (dx.all.js:126)
at t._renderComponent (dx.all.js:15)
at t._updateDOMComponent (dx.all.js:15)
at t.endUpdate (dx.all.js:15)
at t.endUpdate (dx.all.js:10)
at t.endUpdate (dx.all.js:10)
at t.endUpdate (dx.all.js:10)

Thanks.

Hi Luca,

perfect! Thank you!

bye

Cristian Zerbinati

Hi Dino,

Any chance for a small sample? Also are you setting the DataGridView’s RowCount somewhere? If I remember correctly we made a sample for you using a Custom Cell Renderer.

Let me know!

Best,

Levie

My purpose is to take “en-US” culture and change just ShortTimePattern. Can you please give me some code lines doing that?

What I don’t understand is that behaviour:

CultureInfo ci= getCulture(); //that function clone a culture and change ShortDatePattern
Application.CurrentCulture = ci;  //I expect after that line to have in Application.CurrentCulture the same settings

Still, even in debuger, after the second line I got:

?ci.DateTimeFormat.ShortDatePattern
“dd.MM.yyyy”
?Application.CurrentCulture.DateTimeFormat.ShortDatePattern
“M/d/yyyy”

The issue is that you are changing “en-US” without changing the name and .NET compares only the name in System.Globalization.CultureInfo.Equals(). If you create a new culture you need to give it  a new name – or use a sub name, like “en-XX”.

Usually there is no reason to create a new culture, they are all already implemented in Windows, you can simply assign CultureInfo.GetCultureInfo(“ro-RO”). Or set it in default.json (default is auto, it’s detected from the browser), or add to the URL “?lang=ro-RO”.

Or you can try to assign a different culture and then your modified culture to bypass the Equals() check.

Solved with realse 2.1.60 of Wisej

thank you

Cristian Zerbinati

Hi Anz,

Check this out and let me know if you have any trouble: https://wisej.com/support/question/aspnetcontrol

Best,

Levie