Hi,
are you 100% sure that this is caused merely by going from 2.1.5 to 2.1.9 ?
Can you please check if anything else changed in your environment / settings ?
You can find a few pointers to check here:
https://wisej.com/support/question/httpcontext-current-session-is-null
Thanks in advance.
Best regards
Frank
Thanks Ewan,
we could reproduce and will provide a fix in the next release.
Will keep you updated.
Best regards
Frank
Hi, Frank, attached please find the sample code our programmer prepared for this case. Thanks for your help!
Hi,
this enhancement has been added to 2.0.56 and 2.1.8.
Best regards
Frank
Hi Huynh,
issue #1957 is fixed in 2.0.56 and 2.1.8
Best regards
Frank
Hi Ulisses,
#1960 is fixed in 2.0.56 and 2.1.8
Best regards
Frank
Hi Ulisses,
issue #2036 is fixed in 2.0.56 and 2.1.8
Best regards
Frank
Hi Ewan,
can you please send an example ?
Best regards
Frank
Hi Frank
Still not fixed in V2.1.7
I have two integer columns in my grid which remain read only if you set the column to be read only
Thanks
Ewan
Hi Huỳnh,
Just change the favicon.ico file in your project folder on the same level as Default.html / Web.config.
After setting it to the new one, clear your browser’s favicon cache and refresh.
More information:
https://en.wikipedia.org/wiki/Favicon
Best,
Levie
We can reproduce and confirmed that it’s a regression. Will be fixed in the next build. It was caused by adding support for Enter/Leave events of controls without a proper parent (like popups, embedded controls in grid, etc.)
Hi Weitan,
can you please share some code or create a test case so we can reproduce that issue ?
You can either post it here or send it to frankATiceteagroup.com
Thanks in advance !
Best regards
Frank
Update: Version 2.1.7 fixed all bugs.
I cleaned up example code a little bit, for whom might be interested in how to use DataRepeater later.
Hi,
this enhancement request was logged as #2059.
Best regards
Frank
Hi,
I have logged enhancement request #2058 for that issue.
Best regards
Frank
Hi Ewan,
should be fixed in latest Wisej beta (2.1.7).
Thanks,
Frank
Hi Frank,
all fixes are included in the latest Wisej beta (2.1.7).
Best regards
Frank
There is almost never a need to call Update or Refresh directly with Wisej. Update() simply marks the component dirty and it’s done already by all the properties. You should call Update() only when implementing a custom control and adding a property that should mark the component dirty. Refresh() is similar to Update() but it also invalidates all the previously rendered properties and causes all the properties to be set again on the client.
To answer your question, just changing the data source (when using BindingList like in our case, or a BindingSource) automatically updates the DataRepeater. You can add, remove, assign items and the DataRepeater is updated. No need to reassign the data source.
It’s in the Material-3 theme (https://github.com/iceteagroup/Wisej-themes).
If you open ThemeBuilder, load the Material-3 theme and click on a TextBox it will select the TextBox appearance in the appearance tree. There you will see “inherit: inputElement”. Select it (see screenshot 1) to see the styles and properties.
In the styles you can see that it has a simple border at the bottom of 1 pixel and a css style using an :after pseudo element to remove the focused thicker animated line (see screenshot 2).
Then select the “focused” state and you can see a different css style (see screenshot 2) setting the :after pseudo element to a 2px line animated to expand horizontally to implement the material animation.
HTH
Hi Andrew,
I think it is just the timing of the events that causes this. I am not with Wisej.
This seems to make it work.
private void button3_Click(object sender, EventArgs e)
{
_listForDGV[1].IntValue += 10;
Application.Update(this);
MessageService.SendMessage();
}
HTH – Tim
