It only happens on design time (on visualstudio designer)
On runtime seems to be correct
Thanks, it’s all connected to the same regression with background images not setting a layout or using tile. Will send you a dev build to verify with your app.
Thanks,
Luca
Can’r reproduce this. Tried with IE, Chrome, Edge, FireFox. We didn’t change anything to the JustGage extension in this release. The text is not an html element, it is drawn on the canvas by the justGage widget.
Another image sample
Thanks for the answer Luca. As a side question, how do you track errors like this? Do you catch the JSON packet and analyse it or do you have to set breakpoints on Wisej Javascript library?
Hi Faith,
we have logged WJ-8387 for that problem. Will inform you when it´s fixed.
Best regards
Frank
Hi Ser, Andrew,
sorry for that. This regression is logged as WJ-8388 and we are working on a fix.
Will inform you when it is available.
Best regards
Frank
Hi Harald,
thanks for uncovering that issue. We have logged it as WJ-8386 and I will inform you when a fix is available.
Best regards
Frank
Hi David,
Thinking about this, the IEventFilter interface does replace the IMessageFilter but… Since Wisej has the client (browser) and the server totally decoupled , unlike a WinForms desktop, filtering the client events will only affect the server and will do nothing to the client. To emulate the modal state on the client you need to “mask” everything below the z-index of the modal panel. Wisej/qooxdoo have a block feature that works on any widget but it’s not directly exposed to Wisej.Web.Control since we use it for modal dialogs and messageboxes.
I’ll try to send you an example of a “modal panel”.
Best,
Luca
Great catch. The size problem is caused by the png icons “pushing” out. The size in the theme is 16×16 which works fine the first time the nodes are loaded. When the nodes are updated/replaced, the code in the widget fails to enforce the icon size. Will log the bug shortly.
The other error is a client side error that I haven’t tracked down yet. It appears that the client widget is trying to display nodes without an element since they have been disposed. This is a bug too.
Thanks!
/Luca
Hi Tiago,
The extensions that are Wisej.Ext.* are not bound to Wisej.Web, they only use Wisej.Core and are/will be compatible with Wisej.Mobile. The extension only for Wisej.Web are Wisej.Web.Ext, the ones only for Wisej.Mobile will be Wisej.Mobile.Ext.
HostService was supposed to be a product, but we decided to make it a free extension with source code. It’s more than an example since there is an implementation of the System.Web Worker Request as an Owin middleware with additional code tailored to work with Wisej without having to change web.config. Most of the code in there, while relatively simple (which is a good thing), requires a ton of trial and error to make it work correctly with System.Web and as an embedded server. The same is true for the AspNetControl wrapper, our implementation, as opposed to VWG, is a lot simpler but it took a lot of refining and hitting walls with AspNet controls using very advanced undocumented features, like the stimulsoft designer.
Making it available with source code allows developers to build their own customized server or application.
Best,
Luca
Hi Andrew,
WJ-8376 is fixed in Wisej 1.3.82.
Best regards
Frank
Hi Mark,
WJ-8372 is added in Wisej 1.3.82
Best regards
Frank
Hi Andrew,
fix for IE 10 (WJ-8370) is included in Wisej release 1.3.82.
Best regards
Frank
Hi Mark,
ScrollToX and ScrollToY have been added to the TextBox in Wisej 1,3.82
Best regards
Frank
Hi Tiago,
WJ-8366 is fixed in Wisej 1.3.82.
Best regards
Frank
Hi,
VB templates have been fixed in Wisej release 1.3.82.
Best regards
Frank
Hi Edmond,
tile property has been added (WJ-8364) in Wisej release 1.3.82.
Best regards
Frank
Hi Tiago,
WJ-8357 and WJ-8360 are fixed in the latest Wisej release (1.3.82).
Best regards
Frank
Hi Tiago,
both WJ-8355 and WJ-8359 are added in Wisej 1.3.82
Best regards
Frank
