All Answers

Forgot to add  that Wisej implements AutoSize for TextBox, ComboBox, DateTimePicker editable controls allowing you to set the height dynamically in order to build modern looking apps with larger fields given that monitors nowadays are much larger than when I started programming…

WinForms always forces the height according to the font unless you set Multiline=true for the TextBox.

Thanks. The client is not getting updated because the property is always 0 since it changes relative to other controls and Wisej’s differential filter updates it only once. Easy to fix, will be in the next update. It’s WJ-7678.

Seems like when I do grid.CurrentCell = null before selecting, the Row ( and RowHeader) is at all not selected in the UI.

when I comment grid.CurrentCell = null the RowHeader of the last selected Row is still marked after selecting and the newly selected Row is selected but the RowHeader not.

At both tries in Debug i can see that the selected-Property is changing.

Best Regards

Corvin

Hi Luca, thank you for your answer. Yes, in fact I was asking about those systems labels localization. It’s great to know that they will be included in a future release. Thanks again for the great work!

Regards,

Abelardo Cecena

Hi Abelardo,

Looks like I misunderstood your question. You were asking about localizing the system’s message box and I answered something else. ?

As of now we have localized the system strings only to German. However, Wisej supports the custom localization of system labels as well, except that the message box button labels haven’t made it out of the TODO list. I will make sure they are included in the next update. To localize the system labels, simply add the localized strings using these IDs:

MonthCalendar control:

“$Next year”
“$Next month”
“$Last year”
“$Last month”

MessageBox, not recognized yet, but you can add them and they will work with the next update.

“$OK”
“$Yes”
“$No”
“$Cancel”
“$Retry”
“$Abort”
“$Ignore”

Best,

Luca

Hi Abelardo,

Thank you for your kind words.

Wisej uses the standard localization resources in .NET. You can store your own resources for strings or any other object, and you can use the localization tool at design time.

At design time, on a form, set Localizable to true, then select the current culture in the Language property and change the labels in the form. You can localize more than just the labels, you can set the size, location, change images, etc. In addition to Visual Studio built-in localization, you can use any third party tool to manage the localization resources, my favorite is ResXManager.

Take a look at the localization example here: https://wisej.com/examples/

NOTE: Consider that if you are using the designer to localize the labels, the localized labels are loaded only once when the form is created since the labels are loaded in InitializeComponent() which is called by the constructor. To test the localization you have to create a new session. You can force a new session adding ?sid=new to the URL. You can also change the language by adding lang={language} to the URL, i.e. /?lang=fr.

Best,

Luca

Hi Chris,

See attached sample app. You need to update Wisej first – there are a couple of enhancements and fixes related to the HtmlPanel and ComboBox that are necessary for this sample to work properly.

To scroll to the bottom any scrollable panel you can simply use panel.Call(“scrollToY”, int.MaxValue).

HTH

Best,

Luca

I played around with doing it with the ListBox and individual labels and ran into a couple of other problems.  One is just it makes switching channels kind of a pain since either I have to store each individual message and readd them or store multiple controls and turn them on and off.  Right now I just add them to an overall channel HTML property and set the HTML Box to that whenever there’s a switch.  With the ListBox specifically, I can’t have the text coming up from the bottom and the latest message ends up highlighted.

That was another part of the reason I ended up doing a div inside the HTML back in VWG since I needed to get the text bottom-aligned, and it didn’t have a way to do that.  I don’t know if that would be an issue with the example you’re working on though.

Thanks, Luca, that did the trick! I was using BeforeLabelEdit and I was returning if I was on the node I want to cancel edit for, had not seen the e.CancelEdit.

Best,
Alex

PS. Have u checked your spam folder lately? 🙂

Hi Chris,

You don’t need all that. There are several simpler ways in Wisej to achieve what  you need, you can use an HtmlPanel, a ListBox or a Panel (AutoScroll=true). I am preparing a sample app showing all three options. I will send it later on today or tomorrow – it uncovered a couple of issues that need to be fixed for Panel.ScrollIntoView() to work properly.

The ListBox way adds items with html text and selects the last item.

The panel way, adds labels with html text docked to top and scroll the last added one into view.

The  html box way, adds html text and scrolls the inner div to the bottom.

One of the problems in VWG was that most changes to the content of any control caused the re-creation of the dom (that’s the flickering). Wisej never recreates the dom, the widgets always manipulate it through a fast-dom indirection.

Best,

Luca

Hi Alex,

Did you try TreeView.OnBeforeLabelEdit? You can set CancelEdit = true to prevent edit mode.

Best,

Luca

Hi Frank,

All good with Nodes.Clear() now! Thanks.

Alex

Hi Robin,

That’s the way it’s supposed to work. The button (check and radio too) seem to block the click event when not focusable. Will fix.

Thanks,

Luca

Hi Frank,

This is now fixed. Thanks.

Just one thing with the new ‘Focasable’ property. I was envisioning that when this property is set to ‘false’ then the control would not be able to take the focus but that operations on the control would still work and events would still fire. For example if you set the Focasable property to false on a button then clicking the button would still fire the Click event but the focus would remain on the current control. This would be useful if you want to perform an operation on the current controls but have the control not fire the lost/got focus events.

Thanks,
Robin