Hi Nic,
can you please try attached sample.
Quick explanation:
As long as the timer runs, the session will not timeout on the server but you still need to handle Application.SessionTimeout (see code in sample) because the client will still fire sessionTimeout if it doesn’t detect user activity.
We also have a bug with the timing that is being fixed. The client considers a mouse movement as a sign that the user is alive, but it doesn’t tell the server and the session may still expire.
Hope that helps.
Best regards
Frank
Thanks Cris,
I have logged it as WJ-7366
Best regards
Frank
Thanks Nic,
this issue is logged as WJ-7364.
Best regards
Frank
Hi Nic,
thanks for your description and test case.
I have logged the problem as WJ-7363.
Best regards
Frank
Handle Applicaton.SessionTimeout on the server. I’m not sure if you have to do something else. I haven’t tried this scenario. Frank will verify and get back to you. If his office in Germany is dry.
I’m OOTO until middle of next week.
I have seen it working, we have several tests. I will send you one later on today.
Make sure the timer is ticking and *there is a handler attached* Basically every time there is a round trip all pending updates are sent back.
Best,
Luca
Luca,
Just to update you on this. I’m still stuck on Windows 7 (new machine on order :)) so I tried the timer work around you suggested. It doesn’t appear to make any difference. I still do not see the changes made on the second thread. Maybe it just won’t work without websockets?
Nic
Looks like you have a busy weekend ahead of you then 🙂
Thanks – I look forward to playing with all the new toys next week.
Nic
Hi Nic,
It’s not there yet. We’ll have a big update probably on Monday or Tuesday with a lot of fixes and new implementations and I will make sure that the time scale (or at least the basic configuration) is added to the chart.js extension component distributed in the installer and distributed source code.
There should also be the windows 10 (Classic-2) theme with metrics similar to windows (vista, xp,8 and 10).
Best,
Luca
Hi Luca,
When I drop the combobox, the default properties are:
AutoSize = True
Font = @default, 13px, Regular
Size.Height = 30
At runtime, the height looks bigger than the textbox to the right of the combobox. Please see the attached project I am playing with.
By the way, I’ve also noticed something about Label when adding a Height property in the Theme Builder. I’ll send it later.
Regards,
Cris
Actually no, let me correct my last statement. Even if AutoSize=false and the height is smaller than the theme height, Wisej resizes the control correctly. The bottom part gets truncated only if the height is smaller than the internal elements, in the combobox case it’s the button which has a minimum height.
Hello Cris,
What is the font of the page/form? I found a potential problem in the calculation of the preferred height but I can’t reproduce this specific issue.
This is how the system calculates the height of controls:
The problem you are seeing means that the theme height is bigger than the control’s height, which is impossible since the property PreferredHeight always returns the biggest height and that is what is used when AutoSize = true.
The only way I can reproduce this problem is by setting AutoSize=false and a height that is smaller than the height set in the theme.
Can you please check if you have AutoSize=false and also the font please?
Thanks,
Luca
Thanks. Reproduced and logged: WJ-7355.
Luca,
Thanks for the pointer. I’ve got so used to most stuff being handled by the installer I forgot that Material-3 must be manually added.
All good.
Nic
Ciao Luca,
thank you for your answers. I give you the details you asked for:
I take this opportunity to ask some other questions:
Thank you very much!
Hi Luca,
You are correct that size doesn’t change at runtime. The runtime screenshot was taken from Chrome zoomed at 125%. Didn’t know and notice that it was set like that. Sorry for the false alarm
But the issue for combobox (logged as WJ-7347) is still the same.
Regards,
Cris
OK, see it. That should be the blank area between the last column and the visibility menu. If you set the columns to AutoSizeMode=Fill then they will spring to fill the grid. I also see the “$h” text in the column header of the row header column. Which I have seen before but could never reproduce but now I can after resetting some style properties. So that will also be logged and fixed.
Actually from your screenshot the controls did indeed change size. Can you send me the test project? Chrome or IE? I can’t reproduce. See my screenshot below.

Best,
Luca
Hi Luca,
As shown in the image attached, it is to the left of the grid menu (as you call it).
Also, take note of the extra characters appearing on the upper-left corner of the DGV.
Regards,
Cris
Do you mean the column with the grid menu?
If yes, that’s not a column, it’s the column visibility menu (ShowColumnVisibilityMenu property – can set it to false to hide it). With one of the early Material-3 themes the icon was not visible so it looked like an extra column.
If not, please send me a screenshot and also check what name the column got if it’s visible in the columns editor.
