Re: build issues?

Ed Sweetman wrote:
> if libtoolize creates these files, perhaps they shouldn't be in cvs. 
> They're probably best to be automatically generated at the time 
> configure is.
> 
> Everything seems to build fine now with no warnings or errors during 
> configure generation.
> 
> compiling with --disable-nls is broken however. configure does not 
> generate an error when boost is not available, since you cant compile 
> without it, this is something it should do.  configure doesn't look for 
> metakit at all.
> 
> searching for music results in the thread crashing without an error 
> message. Database is thus, not created.  Double clicking the 
> uncatagorized/catagorized trees in the musicbrowser causes zinf to crash.


Actually this may not be the case, it's just that the database is 
Extremely slow for some reason. it's taking many minutes now at 100% cpu 
to scan the files.  I straced the process to see what's going on right 
now and it seems to be doing numerous seeks on the same file reading the 
same strings.


Also, the problem may also be in the fact that it scans . and .. as 
well, meaning it recurses backwards out of the directory given to it as 
the top level directory.  This is a pretty big bug in the scanning code.

> Volume starts up at around 80%, if i had this on non-cooperative 
> (default now) this would have nearly damaged my speakers ( 50% should be 
> a good default if it's not going to be defaulted at 0).
> 
> The last directory in which a file was added (when adding tracks to a 
> playlist) is not saved anymore. Making adding directories (since you 
> cant) very annoying and time consuming.  I'd suggest making the window 
> not destroy itself when you press ok, rather it stays open until you hit 
> cancel.
> 
> Time and thus current position is not updated during any file playback. 
>  You can jump around in the file, but this is not reflected at all by 
> the player.  Total time is displayed of course, just not the current time.
> 
> dragging files in the playlist window doesn't drop them in a new 
> position and causes some kind of corruption with an event that displays 
> the dragging document image.  It will show up randomly and just move 
> down the screen a bit and disappear.
> 
> 
> All of this is not using the gtkmm version, but the default gtk+ ones.
> 
> 






-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf