C1 Community

I believe I've discovered a bug with C1Input.C1TextBox regarding the Enabled setting.

To reproduce, follow these steps using C1Input version 2.0.20073.33104.

1. Place a C1TextBox within a GroupBox and set GroupBox.Enabled = False.
2. Create a mechanism to enable/disable the GroupBox in runtime.
3. Run the app and enable the GroupBox.

Notice how the C1TextBox does not become accessible even after enabling the GroupBox. I can only get the C1TextBox to work if I enable it explicitly. However, even when I do that, the C1TextBox still looks as if it's disabled. The entry text is still grayed out.

I noticed this bug when upgrading from T107 to T108.

Please see the attached ZIP for a demo project using VB in VS 2008.

I believe I've discovered a bug with C1Input.C1TextBox regarding the Enabled setting.

To reproduce, follow these steps using C1Input version 2.0.20073.33104.

1. Place a C1TextBox within a GroupBox and set GroupBox.Enabled = False.
2. Create a mechanism to enable/disable the GroupBox in runtime.
3. Run the app and enable the GroupBox.

Notice how the C1TextBox does not become accessible even after enabling the GroupBox. I can only get the C1TextBox to work if I enable it explicitly. However, even when I do that, the C1TextBox still looks as if it's disabled. The entry text is still grayed out.

I noticed this bug when upgrading from T107 to T108.

Please see the attached ZIP for a demo project using VB in VS 2008.

---

http://helpcentral.componentone.com/cs/forums/p/74929/203782.aspx#203782

Does anyone know if this was officially submitted and is being worked on or not?  I have the same problem with the C1DropDown control, which makes sense because they're probably using the same codebase.

Is there a place we should go on the C1 website to see a list of currently submitted outstanding issues, some sort of bugtracker?  I tried searching through the knowledgebase but that was kinda hopeless...  Any hints would be appreciated.

Ah, nevermind for part of it, I just used the updater and looked through the changelogs and see it was indeed reported fixed in a recent build.  So, forget I asked about that, but the second question is still useful to me - any bugtracker we can view publically?