Hey, I've just noticed right clicking in an app running under the dev releases no longer works. Still works under 1.4.1 though.
Is this a bug? Is anyone experiencing the same issue?
Cheers.
No right click in wine1.5.26/27?
Re: No right click in wine1.5.26/27?
Works in the apps I use. In what app are you having this problem?
-
- Level 1
- Posts: 5
- Joined: Wed Apr 03, 2013 1:07 am
Re: No right click in wine1.5.26/27?
It's a radio automation app called DirEttore. Right clicking over a given track cued will give options such as play before, play after, remove, open cue editor, etc... all are designed to make changes on the fly.dimesio wrote:Works in the apps I use. In what app are you having this problem?
As I said earlier, it's odd because it works in 1.4.1, but not 1.5.26 or 27.
Any ideas what to do from here? I could revert to 1.4.1 and fix the prob that way, but that wouldn't fix the issue related to 1.5.26 or 27.
Cheers.
Re: No right click in wine1.5.26/27?
Run a regression test and file a bug. http://wiki.winehq.org/RegressionTesting
-
- Level 1
- Posts: 5
- Joined: Wed Apr 03, 2013 1:07 am
Re: No right click in wine1.5.26/27?
Thanks, but looks too complicated for this fella, so opted for the path of lesser valour and slipped back to 1.4.1. All good now.
Out of interest, is there a date when wine1.6 stable is to be released, or is it a matter of 'when it gets here'?
Thanks so much for all the awesome work you guys dedicate to this app!!
Baldrick.
Out of interest, is there a date when wine1.6 stable is to be released, or is it a matter of 'when it gets here'?
Thanks so much for all the awesome work you guys dedicate to this app!!
Baldrick.
Re: No right click in wine1.5.26/27?
I don't think any dates have been set. The cycle for previous stable releases has been 18-24 months; 1.4 has only been out for about a year.
However, if you're asking because you expect this problem to be solved in 1.6 without anyone filing a bug, don't. 1.5.x will become 1.6 after several weeks of code freeze, and any bugs that weren't identified and fixed by that time will still be there in 1.6.
However, if you're asking because you expect this problem to be solved in 1.6 without anyone filing a bug, don't. 1.5.x will become 1.6 after several weeks of code freeze, and any bugs that weren't identified and fixed by that time will still be there in 1.6.