Wow do I feel dumb – I had not even noticed the tag input control which is exactly what I wanted. Thanks Mark!
Problem is Windows 7 is end of life, hence IE may not have updated to the latest version.
Hope this helps
Ewan
Hi Matthew,
you can use for example the AnimationEnd event and reset the Animation for your control and add a new one.
Here is a simple example.
Best,
Jens
I have the same problem , and you provide the wisej NavigationBar example “Wisej.NavigationBarTest” project does not work too
BTW, i am using wisej 2.0.13
Conrad,
I have rechecked and started with a blank 2.0 project, added the NavigationBar and could add items
without any problems. (see simple sample attached).
Please make sure that you are referencing only Wisej.Framework and Wisej.Framework.Design
and remove all references to Wisej.Web, Wisej.Web.Design, Wisej.Core and Wisej.CoreDesign.
Hope that helps. If it does not, please send your sample to frankATiceteagroup.com and I will
have a closer look.
Best regards
Frank
Did you drop the Navigation bar from the Wisej Toolbox or Wisej 2 Toolbox ?
All our extensions including source Code can be found here (branch 2.0 for Wisej 2.0):
https://github.com/iceteagroup/wisej-extensions
Best regards
Frank
Hi Conrad,
did you follow the steps in our readme file for the Migration ?
Maybe you´re still referencing the 1.5 versions of the extensions ?
Best regards
Frank
Hi Junarism,
thanks for reporting this problem.
It´s logged as #1830 and will be fixed in the next release.
Best regards
Frank
Hi Daniel,
can you please update from GitHub ?
Are you using it with Wisej 2.0 ? If yes, which version ?
Thanks in advance.
Best regards
Frank
Sorry for the late replay.
Here are some info:
HTH
You probably want to use the FlexLayoutPanel and the TagInput control to do this. Or you can maybe use the FlexLayoutPanel with your select2 control.
Hi Gabriele,
I can´t reproduce that issue. Can you please share some code snippets
or wrap up a test case ?
Thanks in advance.
Best regards
Frank
Hi Frank
thank you, I thought it was an error of my project
regards
Cristian
Hi Cristian,
those are just debug logs, they don´t do any harm besides a (slight) Performance decrease.
See older discussion here: https://wisej.com/support/question/how-to-hide-missing-appearance-browser-warnings
You can disable logging by Setting debug to false in web.config or in Default.json
Best regards
Frank
NuGet packages are not deployed with the project usually. Use Tools->NuGet Package Manager in Visual Studio.
The AspNet authentication sample was created using the AspNet template that comes with Visual Studio. Then simply add
<modules> <add name="Wisej" type="Wisej.Core.HttpModule, Wisej.Framework"/> ... <handlers> <add name="wisej" verb="*" path="*.wx" type="Wisej.Core.HttpHandler, Wisej.Framework"/> ...
That’s all Wisej needs. In general, unless you have a specific requirement, you don’t need to use the old ASP.NET authentication. Simply use any authentication method available to .NET in Wisej, on the server side, and save the authentication in a session variable. There is no need to use cookies or ASP NET. It’s a lot more secure in Wisej since nothing stays on the client exposed to the browser.
In any case, you can use any authentication you like.
Hi Tobias,
the blog article for the NavigationBar and other new controls has just been published:
https://wisej.com/blog/new_controls_navigationbar_and_more/
Find the NavigationBar example at GitHub:
https://github.com/iceteagroup/wisej-examples/tree/2.0/NavigationBar
Best regards
Frank
Hi Gabriel,
the blog article is now available here: https://wisej.com/blog/new_controls_navigationbar_and_more/
Find the sample at GitHub: https://github.com/iceteagroup/wisej-examples/tree/2.0/NavigationBar
Best regards,
Frank
With Wise 2 you can also just do this in your Mdi InitializeComponent()
this.InitScript = “this.mdiClient.mdiTabView.getChildControl(‘bar’).exclude()”;
It expects an editable control. The code is using a panel.
