When I have one WinGrid in a Form, I can use the arrows when the ContextMenu is displayed to navigate between tools.
When I have multiple WinGrids in a Form, using the arrows when the ContextMenu is dispayed actually starts navigating in the WinGrid. It's like there's a problem with the focus. Even if I move the mouse to a sibling tool, the ContextMenu disappears...
I've attached a movie to show the problem with the arrows. When you see the selected tool or row change, it is done with the arrow keys (up and down).
I've tried to upload the video, but it gives me an error after 100%...
In the meantime, take a look at the video @ http://screencast.com/t/yFGTpPz0SMd
Hello,
Thank you for your patience and for the video provided.
I do not think, that this is happening, because of the two or three instances of the 'WinGrid' control, I tried that scenario. How are you showing the context menu exactly, are you just assigning it to the control? Can you reproduce this in a small sample project, so I can take a look at it?
I am checking about the progress of this issue. Please let me know If you need any further assistance on this.
Hi Boris, thx for the update. I have been in holiday and currently processing a lot of work. Ok if I get back to you about this next week or the week after?
Hi,
Sure, please, take your time!
I am still following this. Did you have the time needed?
Hi, currently checking this. I'll first check whether it has something to do with merging toolbars. The problem in our case is that single merging is not enough, we actually need multiple merging. As a workaround, we copy tools from toolbarmanager to toolbarmanager. Maybe this will have something to do with the problem...
It doesn't seem to be a problem with merging or copying tools. I disabled all those things and the problem remains. I also checked if any event handlers could be taking the focus away, but that's not the case.
Making a small reproducible example would be great off course, but I would like to check on some other things first as creating an example will be a lot of work (+ there's the probability that it will not be reproducible in a small example ;-)).
It is strange that a keydown is triggered on the Grid instead of on the ContextMenu... Is there a way to check this? Shouldn't the focus be on the ContextMenu instead of on the WinGrid? Are there events to catch the right click, or an event saying the ContextMenu is rendered? Maybe I can try to explicitly give it focus... Or check the control that has focus...
Lieven,
Sure, please open a new thread when you have more information on this case.
Hi Boris, I'm slowly creating an example in pure Windows Forms resembling our application. If I can't reproduce it in that example, I'll need to create an OpenEdge ABL Windows Forms project trying to reproduce it their. If it's reproducible in the OpenEdga ABL example, I'll need to contact OpenEdge.
If you want, you can close the thread and I'll open a new one when I have the example project... But I'll definitely get back to you on this one.
Lieven
I am still following this. Did you have time to take a look at it?
This could be happening if you are running some other code ot some point, because after describind the scenario, I think that it is a normal one.
OpenEdge is not supported, we've seen some issues with it through the years. However, I will be happy to take a look at a sample.
Sorry, above reply was for another thread. Don't know if you can delete it...
I'll try to create a working small program to hopefully reproduce it. Actually, I have an MdiTab containing a Form. The Form contains a UltraTabControl with five tabs. In each tabs there are 2 or 3 WinGrids. Each WinGrid has its own Context Menu.
If the MdiTab only contains a Form with one WinGrid and nothing else, then the ContextMenu seems to work fine.
I have to add that we're using OpenEdge together with their .NET bridge, so bugs can also come from the dual OpenEdge .NET world...