http://bugs.winehq.org/show_bug.cgi?id=3611
--- Comment #22 from Austin English <austinenglish(a)gmail.com> 2010-05-26 16:02:37 ---
This is your friendly reminder that there has been no bug activity for 6
months. Is this still an issue in current (1.2-rc1 or newer) wine?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=2596
--- Comment #43 from Austin English <austinenglish(a)gmail.com> 2010-05-26 16:02:36 ---
This is your friendly reminder that there has been no bug activity for 6
months. Is this still an issue in current (1.2-rc1 or newer) wine?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=2022
--- Comment #25 from Austin English <austinenglish(a)gmail.com> 2010-05-26 16:02:34 ---
This is your friendly reminder that there has been no bug activity for 6
months. Is this still an issue in current (1.2-rc1 or newer) wine?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=421
--- Comment #374 from el <elton(a)schiert.net> 2010-05-26 14:51:00 ---
Looking at your patch it can be seen that it is impossible for this algorithm
to draw an ellipse that is an even number of pixels high. You always draw a
certain distance below and above the center and the center is a signed integer,
e.g. it sits directly on a pixel. Thus you always draw an odd number of lines.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7807
--- Comment #20 from Henri Verbeet <hverbeet(a)gmail.com> 2010-05-26 12:36:42 ---
This is probably fixed by e6611e22fb037a879205f1330d1a3485f9f18705.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=421
--- Comment #373 from Ed Kolis <edkolis(a)gmail.com> 2010-05-26 10:17:09 ---
(In reply to comment #372)
> (In reply to comment #370)
> > Ok, I have take a look at your screen shots.
> > The 1pixel error must come from center/radius calculation but I simply do :
> > LONG a = (right - left) / 2.0;
> > LONG b = (bottom - top) / 2.0;
> > LONG cx = (right + left) / 2.0;
> > LONG cy = (bottom + top) / 2.0;
> >
> > So maybe, I have to use a cast somewhere because right, left, bottom and top
> > are integer...
>
> Pardon me if I'm wrong but wouldn't 2.0 be a float? That would cause two
> implicit casts which could cause the rounding issue.
Assuming type conversion and order of operations work similarly in C/C++ as it
does in C#, then if right and left are ints,
long a = (right - left) / 2.0;
would be equivalent to
long a = (long)((double)(right - left) / 2.0);
So first you subtract left from right, then cast that to a double, divide by
2.0, and finally cast THAT to a long. There would be two implicit casts
(int=>double and double=>long), but only the latter would potentially cause
rounding error.
Actually, it would not cause rounding error; it would cause truncation error,
unless your LONG type's implicit cast operator from double is set up to call a
rounding function, since IIRC the default behavior of downcasting like that is
to truncate... perhaps the issue is actually the fact that you're not calling a
rounding function?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=17481
Summary: 3dmark freezes on loading first test and crashs
Product: Wine
Version: 1.1.14
Platform: PC
URL: http://www.futuremark.com/download/3dmark03/
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ogldelphi(a)mail.ru
Created an attachment (id=19576)
--> (http://bugs.winehq.org/attachment.cgi?id=19576)
backtrace and dbg symbols
backtrace with debug symbol is in attachment
Debian sid+ experimental distribution
wine 1.1.14
nvidia 7300GT card with binary drivers 173.14.09-5 from sid
It didn't work on my computer at work but works at one in home, don't know why.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7807
Vitaliy Margolen <vitaliy(a)kievinfo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ogldelphi(a)mail.ru
--- Comment #19 from Vitaliy Margolen <vitaliy(a)kievinfo.com> 2010-05-26 08:31:06 ---
*** Bug 17481 has been marked as a duplicate of this bug. ***
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=421
Loïc Hoguin <essen(a)dev-extend.eu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |essen(a)dev-extend.eu
--- Comment #372 from Loïc Hoguin <essen(a)dev-extend.eu> 2010-05-26 08:06:03 ---
(In reply to comment #370)
> Ok, I have take a look at your screen shots.
> The 1pixel error must come from center/radius calculation but I simply do :
> LONG a = (right - left) / 2.0;
> LONG b = (bottom - top) / 2.0;
> LONG cx = (right + left) / 2.0;
> LONG cy = (bottom + top) / 2.0;
>
> So maybe, I have to use a cast somewhere because right, left, bottom and top
> are integer...
Pardon me if I'm wrong but wouldn't 2.0 be a float? That would cause two
implicit casts which could cause the rounding issue.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=421
--- Comment #371 from dufoli <olivier.duff(a)gmail.com> 2010-05-26 07:55:09 ---
@El: can I send you email to exchange quicker and plan a test because I have
nothing to test my code and you seems to have a perfect example.
For not filled ellipse, can you test the value of physDev->penStyle
The only test between filled ellipse and not filled is (physDev->penStyle !=
PS_NULL) for not filled and for filled ellipse: (physDev->brushStyle !=
BS_NULL)
The other tests are quite the same.
I think I have found for filled ellipse the 1 pixel error. It come from the
fact is the inside of ellipse which is draw... I will fix that.
I have to work for other style as intermittent line too.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.