Hi, just upgraded to 2013.2 and noticed that all grid cells that contain an editable drop down list (ValueTypeList with images) will now set the default cell button image to the selected value item image and not the default built in grid drop down arrow image. Did this change after 2012.1?
I know we can set the CellButtonAppearance.Image to whatever we want, but it also appears we cannot set the size or turn off scaling or resizing?
Hi,
This is a known bug that will be fixed in the next service release. You can check the service release schedule here.
It looks like it's supposed to go out today. :)
Sorry, it's not. I just downloaded and installed the 2013.2.2010 service release. If I have a ValueList with items with images that are set to a column on InitializeLayout, the mouse hover (enter element) will automatically show the image of the current value list item and not the default built in grid drop down arrow. This clearly broke somewhere between 2012.1 and 2013.2.
The only workaround appears to be to set the DisplayLayout.Override.CellButtonAppearance.Image property with a custom image of our own.
The service release was delayed. It was actually released yesterday (12/19/2013). So if you downloaded it before then, you don't have the fix.
I had downloaded it just now, 12/19 the .2010 service release.
Hm, that's puzzling. I just tried it out with and without OSThemes and it's working fine for me in the latest build.
I have attached my sample here so you can run it and see if you get the same results. If you are getting the problem using my sample, then something is wrong with the build on your machine. If my sample works, then there must be some other factor in your application that is causing the issue.
Not that it matters, but first I flipped your sample to reference the version-free dlls of .2010 on my machine (probably not the issue as it ran just fine) but... I then set UseOSThemes = FALSE and that causes the cell button image to change in your sample.
Hello lhardtke,
Please note that I created a private case for you with reference number CAS-128668-K2C5V3 . You could find your case at https://es.infragistics.com/my-account/support-activity/
Your development issue has ID 159748. You can view the status of all development issues connected to this case from the "Development Issues" tab, when viewing this case on the "My Support Requests" page of our website.
Let me know if you have any questions.
Regards
Okay. Again, I apologize for the confusion. I knew fixed the bug internally and I thought it made it into the SR.
If you want to get an untested build with the fix in it, Infragistics Developer Support can arrange that for you. Otherwise, it will definitely be fixed in the next SR, which should be released in January.
No, our next production release is early Q2, but I just didn't want it to slip thru the cracks.
My apologies. I just double-checked and I was wrong. The fix for this issue is not in the latest service release. The issue is fixed internally, but it didn't make it into the SR in time.
The fix will be in the next SR. Is this holding up your development?