All Answers

Hi Kevin,

Contact email sent. Thanks.

Hi Alex,

A TreeGrid sample was added to GitHub Wisej-Examples repository. Besides the data bound data table example, there is also an unbound example that uses POC objects.

It’s a paid add on: https://fullcalendar.io/docs/timeline-view  and https://fullcalendar.io/scheduler/purchase

The timeline view is not supported in the free version.

I’d suggest an Azure free account: https://azure.microsoft.com/en-us/free/?v=18.23

There is a step by step post here: https://wisej.com/support/question/deploy-wisej-on-azure

But you can use any tutorial related to VS Web application publishing.

It needs ASP.NET support in full trust.

HTH

Hi Kevin,

Please have a look at 3. Rules for finding the .json file at GitHub as there was a small change in Wisej 1.5.4

Hi Luca,

Yes, using

treeView.Nodes.Clear();

treeView.ExpandAll();

before load nodes works as intended.

Is it will be corrected in nest release ?

Regards.

Unfortunately yes, it’s a regression in Nodes.Clear() it makes the parent node’s property IsExpanded false, which is correct. Before calling Nodes.Clear() on an expanded node it left the property IsExpanded true. But… it also collapses the root node, the bug. You can simply do this as a workaround (as you have found out):

treeView.Nodes.Clear();

treeView.ExpandAll(); // doesn’t have to be after adding nodes.

Currently the mixin cannot remove the inheritance of child components (will add an enhancement request). But you can create a new appearance “my-radiobutton”, for example, and copy the states from a theme then override.  This gives you total control. You can then change the AppearanceKey of your RadioButton class. If you override the AppearanceKey property, add [DefaultValue(“my-button”)] to prevent the new from being serialized.

If your image is using the SVG format you will need to specify a size since most SVGs are designed in a scalable much larger canvas, usually larger than 254×254, and Wisej changes their canvas size to match the size of the target element (cannot be the other way around other it would be a circular reference).

A bit more in depth about properties and Visual Studio designer serialization:

• The Visual Studio designer recognizes inherited values only at the container level. If you create a derived container (Form, Page, UserControl), the property values set in the base class, also for child controls, are recognized as the default value and override the DefaultValueAttribute. It’s not a .NET feature or issue, it’s the Visual Studio Designer that works like that (it can be changed easily though). All Wisej controls implement their own designer but still within the Visual Studio infrastructure.
• When not overridden by the the designer and inherited values from a base container class, the designer relies on System.ComponentModel. Which uses either the DefaultValueAttribute or the ShouldSerialize{Name} and Reset{Name} pattern (which gives you a lot more flexibility:

private bool ShouldSerializeShowHeader()
{
    return this._showHeaderCount > 3; // just to make it weird.
}

private void ResetShowHeader()
{
    this._showHeaderCount = 0;
}

* The accessor can be private, protected or public. Makes no different to VS, it will still use these methods because the pattern is in System.ComponentModel. For property extenders, simply add the Control target argument.

• We have added a property filter to the VS designer in another product we have (PPJ Framework used for Gupta migrations, which is now using Wisej for the web version) to implement what is (should have been) the more logical way where the initialization value of the property is the default value in absence of a local definition of DefaultValue or ShouldSerialize. However doing to in Wisej would break existing WinForms code that expects property values to be propagated when the control is used in a container. IMO it’s a lot better to be able to change the value of a base class and update all usage, but that’s not the way VS sees it. If you want to change the default value, as Tiago showed, you need to override or shadow the property and explicitly add DefaultValueAttribute or the ShouldSerialize{Name} method.
• We could add an option to containers to use the base values in the InheritedPropertyDescriptor instance used by VS but I’m not sure it would be beneficial. It’s probably better to use more component-oriented code and encapsulate functionality in a class and expose only what matters. In fact, in Wisej 2.0 we have added the possibility to design any control class, not just UserControl – this way it’s easier to extend say a Button or a TextBox and use the designer.

EOM, HTH

Hi Sergio,

please find related question and solution here:

https://wisej.com/support/question/override-application-invalidsession-error-message

Best regards
Frank

To share my findings.

Decorating with MetadataType attribute does not yield the expected behavior.

Shadowing properties seem to work well. I am not sure if call to Invalidate() is required.

I will go for shadowing the properties.

using System;
using Wisej.Web;
using System.ComponentModel;
using System.ComponentModel.DataAnnotations;
 
namespace UI.Controls
{
    [MetadataType(typeof(DataGridViewExtMetaData))]
    public partial class DataGridViewExt
        : Wisej.Web.DataGridView
    {
        public DataGridViewExt()
        {
            this.AllowUserToResizeRows = false;
            this.AutoGenerateColumns = false;
        }
 
        // works
        [DefaultValue(false)]
        public new bool AutoGenerateColumns {
            set { base.AutoGenerateColumns = value; Invalidate(); }
            get { return base.AutoGenerateColumns; }
        }
    }
 
    public class DataGridViewExtMetaData
    {
        // does not work
        [DefaultValue(false)]
        public bool AllowUserToResizeRows { get; set; }
    }
}

Hi Sergio,

with Wisej release 1.5.4 we have added Appearance “Switch” to checkboxes.

Best regards
Frank

Hi Neil,

issue WJ-9036 is fixed in the latest Wisej release (1.5.4).

Best regards
Frank

Hi Edmond,

WJ-9034 is now fixed in the latest Wisej release (1.5.4).

Best regards
Frank

Hi Saul,

WJ-9020 is fixed in the latest Wisej release (1.5.4).

Best regards
Frank

Handling scroll events on the server is never a good idea. They are fine as information, but I wouldn’t do it as part of a widget functionality.

See attached sample. It shows a few things:

• Composite grids. The DataGridView component is also a container. You can drop any control on it at design time to have the DataGrid incorporate it in its layout (set the Dock property of the new child). i.e. You can add a status bar, toolbar, a tree view, or other grids. This lets you create composite grids and still retain the properties, events, etc.
• How to add javascript functionality to any component in the designer. The added javascript code can do anything: add methods, handle events and more.
• How any widget in Wisej can become resizable on any edge. The bottom (split grid) in this sample can be resized vertically.
• There are two grids, one docked to bottom to implement a summary row and one docked to the top to implement a filter row.

HTH