All Answers

Hi Dmitry,

To activate your Wisej Web Developer License, open Visual Studio, create or open a Wisej project and open any form in design mode – the designer will ask you to enter the license key.

To activate your Wisej Web Server License, copy the server license key in the “Wisej.LicenseKey” value Web.config – the server will automatically activate the license when the application runs the next time.

Best wishes
Thomas

Hi Luca,

You are right. All I had to do is to prevent BindingContextChanged to execute when InitLayout runs. Now every complex data binding control raises BindingContextChanged event twice, be it on Windows Forms and on Wisej. I don’t attach the fixed sample because I intend to attach it to another report, about another issue I’m facing.

Hi Luca,

Yes, this is exactly what i meant, i thought about the 3 control combination myself, but i’d like the combination to behave like the field control, e.g. like the textbox. In fact, if possible, inheriting from the textbox so it is bindable etc.

Do you think the animation part will be heavy for many such controls on a form?

Best, Alex

Something like the field in the middle here? http://rosskevin.github.io/bootstrap-material-design/material-design/labels/

It has to be built. It’s essentially 3 controls: the label, the subtext and the field. Wisej already has the placeholder, but the placeholder that moves up is not a placeholder, it’s a label on top of the field.

I can see for fun if it’s feasible to create a container that takes a label, a subtitle and any edit control and wraps the control into something similar to the link above.

Best,

Luca

The only reason I can think of is that WebSocket is not on. Even if WebSocket is enabled, when the app is first loaded – this is the first http request that causes Program.Main to be called – it’s not in WebSocket mode and there is no connection yet, so starting a task still works but the push update doesn’t.

Also, when you call action.Invoke() maybe the affected controls were not marked dirty for some reason. One way to check is to verify that the controls that have to be updated on the client are indeed marked dirty: ((IWisejComponent)control).IsDirty.

Let me know.

/Luca

Any reason why this extension wouldn’t work to execute a task and always force a UI update at the end?

public static System.Threading.Tasks.Task StartTask(Action action)
{
return Application.StartTask(() =>
{
try
{
action.Invoke();
}
finally
{
Application.Update(Application.Current);
}
});
}

Hi Massimo,

thanks for reporting this problem and providing a sample, too.
I have logged issue WJ-8380 for it and a fix will be included in the next Wisej release.

I will inform you when it is available.

Best regards
Frank

Yes but it has to be done on the client. You can attach a javascript event to a Button using the JavaScript extender (use the “execute” event) component and use the fullscreenapi included in qooxdoo like this:

http://www.qooxdoo.org/5.1/api/#qx.bom.FullScreen

We’ll probably post an example. You can query whether the browser is in full screen mode using Application.Browser.IsFullScreen.

It is not possible to change the fullscreen mode in an ajax call, it must be done on the client processing a user event (a click).

For Application.Update(IWisejComponent) it doesn’t matter which component. It needs it just to retrieve the session. The Application object itself is a IWisejComponent that you can save using Application.Current and then reuse in an out-of-bound thread to push updates to the client.

Control.Refresh(bool) at runtime is the same as Update(). At design time it forces the update of the non-client areas and refreshes the current selection frame. We use it in design mode when the theme changes or a property that would affect the form title, or a panel title, change since the titles are non-client areas.

Control.Invalidate() is also similar, but it invalidates the cached JSON definition and forces the server to resend the full set of properties back to the client. The client also has a copy of the existing values, so only the different values will be applied (unless the javascript property is implemented using getter/setters).

HTH

/Luca

Please try form.Activate(). I’ll log this as a bug. Now BringToFront() only works for child controls.

You can but you have to process the entries returned by Bing. Look at the source code of the wallpaper extension at /extensions.

This is the API we use: https://stackoverflow.com/questions/10639914/is-there-a-way-to-get-bings-photo-of-the-day

In the C# code you can see where we parse the response in LoadImages. You can test the metadata (title or text) and filter what you like.

Sorry another question.

What does control.Refresh() do?

Hi Luca,

Thanks to your suggestion.

I’ve migrated my custom control of my VindowsForm application. In my new custom checkboxcolumn i changed the icons and other display styles. I just noticed a problem (even in your example). The edges of the cell are disappeared. I could not see them.Do you have any suggestions?
Thanks

If I do Application.Update the first parameter you pass is a control. Does it matter which control is used if it is just pushing updates?

Form vs Button on a form?

Hi Felix,

thanks, it´s logged as WJ-8378 and a fix will included in the next Wisej release.

Best regards
Frank

That’s by design. Automatically checking all child nodes and children of children would potentially break a lot of code since it’s not a standard behavior in winforms or in most treeview controls we looked at. It also would require the opposite functionality – detect when all children are checked and automatically check the parent.

You can find a lot of references about this related to asp.net, winforms, telerik, and many other component libraries.

It can probably be added as an option.

Best,

Luca

Now it works perfectly.

Thanks Luca.