Home - Forums-.NET - FlyGrid.Net (Windows Forms) - IDropDownService problem

FlyGrid.Net (Windows Forms)

.NET Datagrid - Fast, highly customizable, industry standards .NET data grid control for WinForms

This forum related to following products: FlyGrid.Net

IDropDownService problem
Link Posted: 11-Sep-2006 07:27
I have a grid with a custom \"drop down\" column that displays a control by calling IDropDownService.DropDownControl(...).

The control that is so displayed is also a grid with a single column that displays a list of checked items by also calling IDropDownService.DropDownControl(...).

It appears that when the second call to DropDownControl occurs, the original, nesting, cell is collapsed; thus, nothing can be seen.

Is there something I'm missing, or can't DropDownControl handle nesting?[/b]
Link Posted: 11-Sep-2006 10:13
Can you provide me with a sample code or more details (please send to )?
Where is used nesting - in dropdown or in the base grid?
Flygrid is working in databound mode?
What happens when dropdown is closed - what data or cells is updated?
Link Posted: 11-Sep-2006 10:37
Thanks for your reply.

I will try to put together a simple example that demonstrates this problem.
Link Posted: 11-Sep-2006 10:42
Thanks, this helps us to quickly find and fix problem in FlyGrid or in your code.
Link Posted: 12-Sep-2006 09:39
I tried to send develop@9rays.net an email with a zip file attachment containing a README.txt and a VS2005 Solution that demonstrates the problem. I got the following response... (please advise)

----------------------------------------------------
Your message could not be delivered.

Your message is larger than the recipient's computer can accept.
Please split your message into smaller messages and resend in
separate e-mails.

Your message was rejected by aspmx.l.google.com for the following reason:

     5.7.0 Illegal Attachment q18si6514901qbq

The following recipients did not receive this message:

    
Link Posted: 14-Sep-2006 04:46
Thanks for the sample. This problem already solved, fixed version will published to the ned of this week.