From: Nomi H. <nlh...@lb...> - 2012-03-01 19:26:23
|
Well, I'm stumped. I installed a Windows 7 virtual machine, downloaded the latest Java, and installed and ran OBO-Edit with no problems. Mary Dolan is here and she runs Windows 7 and she hasn't had trouble with OE, either. So there must be some combination of Windows 7 version and Java version, and maybe some other factors, that are causing problems for some users on Windows 7. I'm not sure what else to try. I would suggest updating your Java, but it sounds like Karen's student already has a recent Java. Are those of you with these Windows 7 problems able to run old OE versions (e.g., 2.0) successfully? (Not that I have any idea what to do with that information.) Nomi On Feb 23, 2012, at 3:07 PM, Nomi Harris wrote: > Hi Karen, > > Sorry your student is running into strange behavior on Windows. It's true that I don't regularly test on Windows, but we do have Windows users and they have not reported this problem. > > It could be that binary files in her oboedit_config directory left over from a previous version of OBO-Edit are to blame--we see this fairly frequently, and we recommend that when you install a new version of OE, you remove a particular subdirectory of oboedit_config called perspectives. (The latest OE pops up a dialog to ask if you want it to do this for you.) I suggest that she try renaming her oboedit_config (should be in her home directory) and relaunching OE and see if that takes care of the problem. If not, then I will try to investigate. By "editing window" do you mean the Text Editor? I don't see why it should behave differently when it's undocked, but it could be because of that stale binary file issue. > > Nomi > > On Feb 23, 2012, at 2:28 PM, Karen Eilbeck wrote: > >> Hi Nomi >> I have a student in my office who is trying to use obo-edit on a windows >> machine and she is getting some pretty weird behavior. She thinks there is >> a keyboard listener problem. >> Whenever she goes to type/edit she gets a window that says "do you want to >> proceed, etc etc", the same behavior you get when you go to file and click >> 'new ontology'. So basically any editing becomes a task of clicking away >> spurious windows. >> >> She tried the most recent beta, and we went back to the last version 2.1 and >> it was the same situation. >> >> Any ideas? I imagine there aren't that many developers testing on windows >> anymore... She is using java version 1.6 build 26. She also has java 1.7 on >> her machine. >> >> Any insight would be good. >> >> Hope you are well. >> >> --K > > On Feb 23, 2012, at 2:31 PM, Karen Eilbeck wrote: > >> We just noticed that if the editing window is not docked in the main window, >> but floating, then there are none of these typing problems. >> >> --K |