Well we've gone back and setIds on all of our widgets and windows but we've encountered a problem with context menus (in smartGwt)
We are creating context menus dynamically based on the datasource associated with the window.
Code:
Menu menu = new Menu();
menu.setID(listGrid.getID()+"ContextMenu");
It seems that when we create the Menu and call setContextMenu the Menu is created but somehow attached to the root canvas (as can be seen in the developer console). But if we delete the Window and the hence the associated ListGrid, the attached ContextMenu seems to be still hanging around (again as can be seen in the Developer Console). If we then try to reopen the window and dynamically create a new menu (with the same Id as before - as its being created off the same window) it fails during the setId as there is a menu with that Id already created.
But it seems like it might be a bit of a hack, is there a way to get access to these context menus ? How come they are not associated with ListGrid object ?
I really hate that every time I post here it turns off email notifications!!!!
Anyway, I updated and am getting the same problems. I only get to play with automated testing between official assignments, so it's a slow process for me. I can't send in the app I have, and stripping it down to a test app is not something I've had the time to get done so far.
If you're not running the latest nightly (eg maybe you are working with 7.0), you need to be running the latest nightly.
If you are running the latest nightly, we need a runnable test case.
FYI:
I updated to 5/18 build, in prep to work on this some today. The problems I was having have gone away. I had previously tried the 4/13 and 4/22 builds, both had the same problems.
What kind of "news" are you looking for? This is a 5 year old thread where people are claiming issues with an ancient version of the product, but without a test case. It's likely that if there was an actual bug, it's long since been fixed.
Start by reading the Automated Testing and Selenium overviews in the docs. If you believe you've found a bug, create a new thread for it, and make sure to include all of the necessary details to allow the problem to be reproduced - see the Debugging overview for assistance with this.
Comment