Ian Williamson | 11 Aug 22:08
Picon
Favicon

RE: win32 bugs

I'm back from "vacation" (You all missed me didn't you!)...

Mario,

I have some patched for problems with the Win32 compile that will cause all
kinds of strangeness.

[For example, if the files in the plugins directory are built with a "debug"
build, then the zinf.exe is rebuild with release (the plugins directory will
NOT be automatically rebuilt).]

I'm also going to be looking into those compile errors you listed.  I get
them too, but thought them harmless enough (for now).  If you want to
co-ordinate Win32 fixes let me know directly and we'll work together at it.

I'll get Ed my latest build fixes today and hopefully they can get into the
tree soon.

IanW

> -----Original Message-----
> From: zinf-devel-admin <at> lists.sourceforge.net
> [mailto:zinf-devel-admin <at> lists.sourceforge.net]On Behalf Of Mario
> Pintaric
> Sent: August 6, 2002 10:16 PM
> To: zinf-devel <at> lists.sourceforge.net
> Subject: Re: [Zinf-devel] win32 bugs
>
>
> Build issues resolved for me using VC++ 6.0.  Fairly clean compile.  Here
(Continue reading)

Mario Pintaric | 13 Aug 09:56
Favicon

Re: win32 bugs

Hey Ian,

I actually take weekends off, crazy huh.  I'll be looking at the issues
pointed out over the course of this week as time permits.  The build
problems were relatively minor.  One of the warnings has already been
tackled in some sources (name truncation problem in template identifiers).
I looked into it, turns out the M$ compiler, up to version 6.0, has a bug
and will ignore pragmas to turn this warning off, so the most common warning
can safely be ignored.  Though it will manifest itself during debug, since
the affected identifiers won't be visible.

I've noticed that on my setup, debug and release builds dump everything into
the same directories.  This might explain some issues that are being seen
since you can thus easily go out of sync with your own work.

I'm not using BUILDALL.DSP.  Haven't looked into why this is broken, but it
is.  I use it's equivalent from the GUI Zinf project.

 I agree with Ed on freezing the code given where things are at.  With fixes
in place, the current version of the player would look pretty good.  Sounds
good too.  I've compared the player to some other alternatives ... at lower
bit rates it sounds much better then everything I've tried other then the
most current builds of Winamp.  My main interest in the project actually
started because this player seems to be so focused on the music rather then
the gizmos attached to it.

I have noticed some minor issues with the GUI of the player on Win32.  There
are some redraw issues with the Aqua skin (the track position indicator).
The latest changes for volume updates are, well, cute in the way they ramp
up the volume to the current setting, but the current volume setting is not
(Continue reading)

iwilliamson | 13 Aug 19:07
Picon
Favicon

Re: win32 bugs

> I've noticed that on my setup, debug and release builds dump 
> everything into
> the same directories.  This might explain some issues that are 
> being seen
> since you can thus easily go out of sync with your own work.

This should already fix in CVS.  Completely separte build trees.

> I'm not using BUILDALL.DSP.  Haven't looked into why this is 
> broken, but it
> is.  I use it's equivalent from the GUI Zinf project.

I'd like to find out what's wrong with that.  I added it and it works perfectly for me (and Ed I think).  It's the
only way to build the project properly (Though there are still some hiccups).

IanW

-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31

Gmane