On Friday 10 January 2003 05:28 am, Rick Romero wrote: > This is currently listed as bug #434 > http://bugs.winehq.com/long_list.cgi?buglist=434 > in bugs.winehq.com. You can add yourself to the list, there are a > couple others there also interested in Foxpro working. (Or at least, > I've sent them there :) Okay thanks, I've voted for the bug and encouraged a few other people to do the same. This bug is described as "macromedia flash 5.0" which, if I understand the comments correctly, was resolved some time ago as well as Adobe Illustrator. Seems that that foxpro problems are discussed in the comments but otherwise the bug report doesn't seem to apply to foxpro. Can we change the description of the bug report to show the 'foxpro' keyword perhaps? > I'm glad someone else can make it work with +relay on :) Yes, slowing down the operation of VFP seems to resolve the mouse issue. I was just thinking... as you know it is necessary to switch to a different app and then switch back to VFP in order to see that the command window is active - otherwise you don't see the cursor at all. Now, when the cursor is blinking it is blinking like it is on speed or something. I wonder if all these symptoms are somehow related. > Hopefully Duane can close out this bug, as FoxPro is the last > application (that I'm aware of) to exhibit it. I'm crossing my fingers ;) -- Paul McNett - p@ulmcnett.com Hollister, California, USA _______________________________________________ wine-users mailing list wine-users@winehq.com http://www.winehq.com/mailman/listinfo/wine-users
