Hi Frank,
Fixed.
Thanks.
Hi Frank,
LinkColumn and CellFormatting are now fixed but noted other issues though.
If column.headertext is wider than the column width, the header text seems truncated as shown in the attached image and affects the horizontal alignment…
Also, can’t resize the height of the column header even the ColumnHeadersHeightSizeMode is set to EnableResizing but can still resize row width even if the RoHeadersWidthSizeMode is set to DisableResizing.
Thanks.
Hi Frank,
This is now fixed.
Thanks.
Cris,
this has been logged as WJ-7427 and WJ-7434, both fixed in the latest build (1.2.25).
Best regards
Frank
Cris,
logged as WJ-7431, fixed in build (1.2.25).
Can you please retry ?
Thanks,
Frank
Hi Alex,
this issue is WJ-7426, also fixed in the latest build (1.2.25).
Best regards
Frank
Diego, Nic,
WJ-7425 including in the latest build (1.2.25) fixes this issue.
Best regards
Frank
Hi Cris,
this problem has been logged as WJ-7424 and a fix is included in build 1.2.25 (just uploaded).
Best regards
Frank
Hi Alex,
good news: WJ-7421, WJ-7422, WJ-7423 have all been fixed in build 1.2.25.
WJ-7429 (“Reusing a disposed control doesn’t throw the ObjectDisposed exception.”) is fixed as well and also included in this build.
This now leads to an exception in your sample that was previously not exposed.
To avoid it, you can modify your code:
if (t == null || t.IsDisposed)
t = new TextBox();
Best regards
Frank
We´re happy to announce a new beta build (1.2.25).
In addition to a rather large list of bug fixes (see below) you will find the following additions:
| Item | Type | Priority | Severity | Title | Resolution |
| WJ-7423 | Bug | Low | Trivial | Changing the parent of a child control at runtime causes the control to lose the parent. |
Complete |
| WJ-7421 | Bug | Low | Trivial | Classic-2 theme doesn’t show the navigation buttons in the DateChooser control. |
Complete |
| WJ-7422 | Bug | Low | Trivial | Activating a new MdiChild while it’s created doesn’t make it visible the first time it’s shown |
Complete |
| WJ-7416 | Enhancement | Low | Major | Wisej: Treeview performance is bad | Complete |
| WJ-7424 | Bug | Low | Trivial | Action in Treeview AfterCheck Event is always “Unknown” | Complete |
| WJ-7425 | Bug | Low | Trivial | Hiding a docked MenuBar or ToolBar doesn’t adjust the layout. | Complete |
| WJ-7426 | Bug | Low | Trivial | Single quote in a ComboBox shows as \u0027. | Complete |
| WJ-7427 | Bug | Low | Trivial | Label with borders doesn’t show the padding space when set. | Complete |
| WJ-7428 | Bug | Low | Trivial | The Clear and Classic theme use the light icon for the DateChooser navigation buttons making it not visible. |
Complete |
| WJ-7429 | Bug | Low | Trivial | Reusing a disposed control doesn’t throw the ObjectDisposed exception. | Complete |
| WJ-7430 | Bug | Low | Trivial | The ToolBarButton is initialized with preset Margin and Padding – should start with the Default values. |
Complete |
| WJ-7431 | Bug | High | Major | Altering the e.CellStyle passed to the DGV CellFormatting event alters the original DataGridViewCellStyle. |
Complete |
| WJ-7432 | Bug | Medium | Minor | The DGV LinkBehavior.HoverUnderline inherits applies the AlwaysUnderline style. | Complete |
| WJ-7433 | Bug | High | Minor | TabPage.AutoScroll doesn’t work. | Complete |
| WJ-7434 | Bug | Medium | Trivial | Padding set in the theme is not applied to controls with the Padding property. | Complete |
| WJ-7435 | Bug | Low | Trivial | Padding set in the theme is not used to calculate the AutoSize. | Complete |
| WJ-7418 | Bug | Low | Trivial | Long non-wrapping messages in a MessageBox touch the right border. | Complete |
Hi Diego,
The bug that you have identified with the ToolBarButton is that it initializes Padding and Margin to 0,0,0,0 overriding the theme. It also serializes those values and the null icon. It has been fixed and should be available shortly.
Another problem reported above by Nic, is that the designer doesn’t take in consideration the padding value from the theme. This is also fixed.
About showing the theme value in the property editor, only the BackColor, ForeColor, Font show the value from the current theme as the default value. Most themeable properties that happen to be overridable by the component are overridden when they value corresponds to the “default” value. The padding should show (-1) to indicate the default. Usually when a property has been set to something different than the default it is displayed in bold.
The reason for this is that Wisej avoids sending the property back to the client if it is the default and lets the client and the theme handle it. For the colors and the font, there is some additional code that allows them to be shown in the property editor and still don’t go back to the client when unchanged.
Best,
Luca
Hi,
In addition to the above issue in toolbar, if you are in ToolBarButton Collection Editor and click add, the padding value is always set to 0,0,0,0. Should it not take the padding setting from the theme file, if there’s any?
Thanks.
Hi Alex,
You are right, you don’t see the exception because it’s an assert failure in debug mode. It should probably be moved down and make it an exception. 7422 refers to another problem we noticed testing your test case.
Thanks!
Best,
Luca
Hi again,
In fact after reading my original post and your answer, it is not clear to me if WJ-7422 refers to my reported problem A or B2…. 🙂
Alex
Hi Frank,
After all Text_# forms are closed, if I open up a new one I don’t see the Textbox, but I do not get any exception.
Alex
Hi Cris,
this will be implemented together with the column resize modes.
So it´s already on our TODO list.
We´ll inform you when it´s ready.
Thanks,
Frank
Hi Alex,
thanks for your input and sample.
I have logged the following 3 issues:
WJ-7421 Classic-2 theme doesn’t show the navigation buttons in the DateChooser control.
WJ-7422 Activating a new MdiChild while it’s created doesn’t make it visible the first time it’s shown
WJ-7423 Changing the parent of a child control at runtime causes the control to lose the parent.
We also found a potential error in the test code you provided:
If all the text_# forms are closed, the single TextBox instance is disposed, so the next time a form is created, you will get an Object Dispose exception.
Maybe you can check this ?
Hope that helps.
Best regards
Frank
Hi Birol,
The main original purpose of wisej was to be used as a replacement of VWG in our projects and the projects executed by our service partners. We have hundreds of applications around the world (since 1998) based on our migration technology. So, for us (iceteagroup.com) Wisej will succeed even if we fail to sell many licenses.
Having said that, we will put in place source code safeguards where if we cease to maintain the product, every customer with a valid license will receive the full source code. We will also make available the source code from the start (at a price) and named escrow deposits for a fee since it has a per-user cost.
We have done the same for our PPJ Framework since that’s the first question we have been getting for about 16 years from corporations around the world that obviously don’t want to get locked in.
I hope this helps.
Best,
Luca
Hi Alex,
A wisej application is configured exactly as an ASP.NET/MVC app. So yes, you need an app folder, a /bin, and a web.config + a start up page and application.json.
The start up page (usually Default.html) can be configured in web.config to be the default document or can be addressed directly in the url, just like any web site.
Additionally, wisej supports a simple “pretty url” system through the json config file. Where you don’t need to specify the extension. For example: mysite.com/client1 or mysite.com/client2 will cause wisej to process client1.json and client2.json and if the json specifies an html page, wisej will internally redirect to that startup page. Tne html startup page is needed since the browser must load a page with a reference to the wisej.wx bootstrap script.
To answer you question about Main. The Program.Main method is execute when a new session is created. So it’s executed only once when an application is loaded the first time for a specific user.
Your client#.json files can each refer to a different startup method in the same class and redirect to the same startup html file if you wish. You can have Program.Main1(), Main2(), etc. There is no need to duplicate the apolication in Wisej. You can have several sub application within the same project. See also the configuration page in the /docs.
HTH
Best,
Luca
Sorry this issue is taking a while. Working on it.
