Hi,
Last week I bought IgniteUI license and I downloaded 2013.1 version (2013.1.2217). I replaced Infragistics.Web.Mvc reference, all ig .css and all ig .js in my project, substituting them with the ones just downloaded from Account/KeysAndDownloads products dashboard.
Bad work: ig datepicker started to not work. When I click on the control I am able to see the datepicker, but after a date selection control is unusable, like if I have one possibility: "select one date because you have one shot". After selection I have to click out of the control, re-click on the control, re-click out of the control and then I am able to click on the control and see the datepicker. Of course if I select a date I have to redo all the operations...boring and unusable!!!If I use IE9 I am less lcuky, because I can see the datepciker disabled after I select a date...
I did not change anything else, so I am using:- jQuery 1.9.1- jQueryUI 1.10.2
Do you have some ideas? I also noticed a bad beahvior on IE9 for igGrid...on IE10 all right, but on IE9 footer is out of layout (all paging fetures aligned to the left). I checked loaded CSS and I can see igGrid css missing...I forced it into IgLoader resources and of course it works, but I don't understand why now I have to explain igGrid into the resources while it was an automatic loading with igLoader before...
I am a little confused about this update...of course it is not the fact IgniteUI is now licensed, but the version to which I upgraded it.I passed from 2013.1.2039 to 2013.1.2217 (css and js files passed from April 19 2013 to August 15 2013).This is what I tried to do: with the last dll (Infragistics.Web.Mvc version 4.13.1.2217) I replaced infragistics.ui.editors.js and...surprised: datepicker started to work again...If I come back to the previous version everything works, also grid footer...
Could you help me?
Flavio M.
I downloaded last 20131.2292 version.
I read bug fix in the list and I tested it: it seems to work now ;-)
Thank you all
Any news?
Sorry,
the problem on the igDatePicker is not still sovled at all. Replacing DropDownTriggers("focus") with DropDownTriggers("") I have to use a button type different from "None" to be able to see calendar selection...
May I am missing some properties to be set with DropDownTriggers("focus") ?How can I set DropDownTriggers("focus") and ButtonType(TextEditorButtonType.None) in the same time?
Thanks
Hi Martin,
I found one reason for the first problem, the datepicker one.
I tried to create a new project, selecting IgniteUI startup, and adding the same snapshot I have in my project about datepicker. To be sure I replaced all js and css with the ones I have now (last IG version) and BINGO! Same result.This is my snapshot:
@(Html.Infragistics().DatePickerFor(m=>m) .ID(ViewData.TemplateInfo.GetFullHtmlFieldId(string.Empty)) .HtmlAttributes(new Dictionary<string, object> {{"class", "datepicker"}}) .ButtonType(TextEditorButtonType.None) .Width(140) .DateDisplayFormat("date") .NullText("Inserire data") .MinValue(new DateTime(1990, 01, 01)) .MaxValue(new DateTime(2049, 12, 31)) //.DropDownTriggers("focus") .Render())
It works right commenting the DropDownTriggers. And, of course, it works righe if I specify a null string for the dropdown triggers.I saw this on Known Issues:
To disable all triggers for the drop-down, the dropDownTriggers option must be set to an empty string or to null.
But I don't understand why it works right with old files and it works bad with the new ones...but it does not matter, important thing is that now IT WORKS ;-)
Although, I am still confused about the problem related to the igGrid css loading, but now it is partially solved specifing on the IG loader igGrid resource. I will try to elaborate a similar project to reproduce the issue and then I will write here. No problem related to the Out of stack spaceas you said. I now what is this, but I can ensure it is not this kind of problem (also because in the console I can't see any kind of css or js error).
Thanks for now,
Uhm...
I will retry to delete all js files, all css files and the DLL one. Then I will let you know if something changes...
Thanks for now