Opiniones sobre Component Toolbox

Puntuación de revisión media: 3.5 (5)

3.5 de 5 estrellas

5 estrella
60%
4 estrella
0%
3 estrella
0%
2 estrella
20%
1 estrella
20%

Comentario positivo más reciente

jimfryeUSA5 estrella
I have purchased this suite as well as the Solutions PIM v3.0. I mainly use VFP in my development. The tech support by email is quick and very professional. I find the controls to be excellent and was... Leer más

Comentario crítico más reciente

jmilamtxUSA1 estrella
From talking to the customer support line, this is not the first time that this has been reported as the prior reviewer stated. They just do not want to spend time fixing anything in the non .Net... Leer más
jimfryeUSA5 estrella
I have purchased this suite as well as the Solutions PIM v3.0. I mainly use VFP in my development. The tech support by email is quick and very professional. I find the controls to be excellent and was very happy to see that there was quite a bit of documentation for Foxpro Developers. I cannot say the same of many vendors that claim to support VFP! So I have to give this product my highrst recommendation. I am looking forward to using their new .net controls in my C# apps as well.
Larry McDermott5 estrella
Great set of tools!
jmilamtxUSA1 estrella
From talking to the customer support line, this is not the first time that this has been reported as the prior reviewer stated. They just do not want to spend time fixing anything in the non .Net version without charging the customer.
Craig Gluck5 estrella
One of the things we here at DBI take great pains in is to make sure our controls work in a variety of other languages besides VB and VC. We also test with VFP, Access, some of the Borland languages, and an occasional third party language (i.e. PowerBuilder). As such, we occasionally have to make adjustments to the controls so that they are compatible in the other languages. And then you have to contend with the variety of operating systems. It seems every new release or security patch tends to cause new compatibility issues. And then when you add compatibility with other third party products.... Well, it is not always possible to be all things to all people. And fixing a problem for one situation (i.e. a re-size issue) could cause problems within other areas. As such, a custom version would usually have to be created for the situation.. (Thus, the charge for a customization). As the primary engineer on the product, thousands of the product has been sold, and this is the first time I have heard of this issue. As for our price, if you are only going to use one or two controls, then it may be considered expensive. But with 60 controls in the package, that is less than $10.00 per control. Many of our customers find that quite the bargain. Craig Gluck Lead Developer at DBI
John Milam - www.applogix.com2 estrella
This is a fairly expensive set of controls, but there are many controls in the package so I though they would be worth the money. We use some of the controls, but any of the controls that allow text editing, such as the ctNEdit, ctMEdit, ctCombo, etc have a bug in the program that does not allow the correct font size to be set if the control is resized, utilizing any standard resize control, such as the ReSize control from Larcom & Young. Basically the text is the correct font size if the control does not have focus, but once the control retains focus, the font does not size correctly. If you have any need to resize controls on your form, these controls are not for you as they do not work. I contacted the support department and after the tech spent a few days investigating the problem, they responded that fixing this bug was outside the scope of the control and I would have to contract with one of their engineers to customize the controls. I don't feel that paying additional money for a vendor to fix their own controls is a good business practice. We are presently looking for controls to replace these controls or we will return to using the standard VB controls.