Like others I have spent £154.00 on this suite of controls for lightswitch, however some of the most basic requirements are not met, particularly with the Grid control. Firstly, Column headers display the underlying field name, rather than the Display name set for the underlying embedded control and there is no way to change this. How user friendly is that, given that database field names are sometimes likely to be less than intuitive. The default behaviour does not even split out words from the name i.e. ProductDescription does not display as 'Product Description'. This issue has been highlighted since November 2011 and is still not fixed!
Additionally, numeric values will not align right, even if you set both horizontal alignment and text alignment on the underlying control! So, no numeric data in our lightswitch grids, please!
You can't hide the search bar (what if you are providing your own functionality?).
Amazingly, the Display Name property exists for a grid, but it does not 'Display' anywhere! What if you have several grids on the same screen? How on earth does a user know what they are looking at?
These are the most basic, yet crucial things. Under these circumstances, this product should not be RTM where developers are expected to pay in good faith that at least the most basic requirements are met.
It wouldn't be quite so unprofessional had these issues been adressed based on previous posts highlighting them, but this has not transpired.
Infragistics, give me one good reason, given these issues and the lack of response, why I should use your grid in a production app, let alone pay for it (which I have),in its current state. These are not bugs, just basics. Truthfully I am tired of having expectations raised by slick p.r. blurb and pretty pictures only to be let down by what seems to be pure trivia.
Sort it. Now. Please.
Hello Ian,
I have been looking into your post and I do understand what you mean. The IG LightSwitch package is quite new, like the platform itself, and is currently undergoing its basic development. This is reason that there still are no Service Releases available, however the issues that had been submitted, have been worked on and some, like the column headers issue you mentioned, are already fixed internally.
I have also been looking into the other issues you mentioned. For the grid’s display name, since no such functionality has been intended, I can submit a Feature Request on your behalf, whereas for the numeric values alignment - I can log it directly with development, so they can attend to it right away.
As I mentioned above, still there aren’t any Service Release projections for the LightSwitch package and this is why, the only way we can provide you with any fixes would be with an untested version of the installer, which you would use to replace the RTM you currently have installed. If you’d like the untested version, I can suggest requesting one after the alignment issues have been fixed.
Looking forward to hearing your thoughts on the matter.
Hi Peter,
To be frank, although I appreciate the fact that you have responded, the content of your reply is rather worrying. I'm certain you didn't mean '....undergoing its basic development....' in the literal sense although I will reiterate that given the shortcomings of the grid for most basic functionality, this should never have been released as a paid-for product!
How can a product go through full-cycle testing and not catch these most basic of errors? Besides which the grid is your silverlight version wrapped as a lightswitch extension: does even the underlying silverlight version exhibit these issues?
It is also unacceptable that there are as yet no planned service releases for a product which is plainly not fit for purpose. How many other issues may I (or my customers) discover with respect to this suite of controls?
Given this, I would like someone at Infragistics to initiate the process of refunding me as soon as possible. I am hugely disappointed and frustrated that I cannot present an application to my customers built using these controls because of such ridiculously basic missing functionality and I also find it very hard to understand how such a product could be released to the marketplace in such a condition.