Hi All,
I am using the DropDownManager.DropDown method to display a dropdown window below a cell in a grid. When I drag the window containing the grid across to my second monitor and then activate the dropdown on the grid the dropdown is popping up over on the edge of the other monitor. It seems as if the new position is being calculated correctly but for some reason it cannot go any further than the edge of the screen. Has anyone come across this issue before?
Thanks,
Denis
Hi Denis,
This sounds to me like you might be doing something far more complicated than you need. Why are you using the DropDownManager? If you have a dropdown in a grid cell, you can drop it down using the PerformAction method of the grid.
Hi Mike,
My grid cell is actually using an UltraTextEditor, when I start typing in the text area I use the DropDownManager to display a dropdown with a multi-column grid below the cell. It works fine when using a single screen but for some reason the dropdown window does not disply on the second screen when I drag the grid window over.
You could do the same thing using a DropDownEditorButton, rather than calling the DropDownManager directly. But maybe you don't want a button in the cell.
Anyway, I'm really not sure why the dropdown is showing up on the wrong monitor. As I see it, this is either a bug in the DropDownManager or an error in your code. Since the grid and the editors use the dropdown manager all over the place internally and it works on dual monitor systems just fine for lots of people, it's probably something your code is missing. Perhaps you are using the wrong overload of a particular method. Or perhaps there is code internal to the DropDownManager that handles things like this.
The best thing I can suggest is that you Submit an incident to Infragistics Developer Support and include a small sample project demonstrating the behavior and maybe they can figure it out. :)
Seems it was an error in my code. In the DropDownManagers DropDown method I was setting the Infragistics.Win.DropDownPosition to BelowExclusionRect, changing this to RightOfExclusionRect fixed the issue.
Cheers,