Quote: Originally Posted by intuitionsys
Well as for FMOD doing its voodoo with Xine I haven't been able to reproduce what it was doing so I'll just chalk it up to "whatever" and move on. I had Xine going through FMOD with a ring buffer but it still had clicks between buffers that couldn't be completely eliminated, so I'm saying to heck with it for now and will just close the instance and let Xine open the device itself. I won't get spectrum data but I doubt anyone really cares about that while watching a movie anyway.
I wish I could help with your S4 problem but I've never worked with that chipset before. I do know that many chipsets will change the refresh rate for both outputs to 60Hz when composite/s-video out are enabled and there is squat you can do about it.
Oh hey btw have you given your frontend a name yet? I've seen talk around this section about your player but nobody has referred to it by name
Silverwolf 2 is plodding along as I find free time here and there so hopefully the ~3 month timeframe is still accurate. The thing that is really taking time right now is completely re-engineering the skinning and UI. Alot of the backend guts will just be code from 1.x ported to Qt4.
The player, for lack of a better name, is called LlamaBox. In regards to the S4, I pointed out 60Hz because that is a good thing. If that switcher changes it to 60Hz then something is right. Anyways, a BIOS flash fixed the problem.
As far as Qt goes.... It is the reason why I wrote my own toolkit. Speaking of that: I just spent today writing a really nice line drawing algorithm. It is based off bresenham's algorithm, but it draws lines with various weight and cap styles. This is needed on my VFD panel where there is no API for drawing primitives. (I've been limited to 1-pixel wide lines on this device until now).
But, The toolkit is coming along nicely. I added selection to the listview widget and I'm in the process of adding a TreeView. I have one huge stumbling block ahead: adding the theming engine. I must decide where to draw the line between the widget level and theme level.
Have you enjoyed using Qt's Styles? Are you making your own QStyle or are you just making your own widgets? When you make your own widgets, do you use the primitives provided by QStyle or do you just do it all by hand? This is the kind of experience I need to decide where to draw this line.
This line must lie somewhere between: "The style draws every widget, the widgets do not draw themselves" to "There is no Style".
The first method has two obvious disadvantages: Custom widgets must be used with a Style that supports them. Derived widgets cause a problem and there isn't any code reusability. The second method doesn't even provide Styles.
So, the answer is some place in the middle, where the Style provides primitives like borders, glyphs, fills, etc.. The hard part is quantifying all of these elements and finding a reasonable granularity.
Oh yeah, and I need to write this kernel module for the HQCT Radio.
EDIT: If you post or read information on this thread that you believe is important or critical then please let me know so I can add it the the first post. Might as well do this right. So, let me know -- even if you just read something from this thread and it helped you out.
EDIT, PART II: If you think of a name better then LlamaBox (there is undoubtably one) the let me know. It doesn't have to relate to anything -- just sound cool. But please PM it to me, or I guess I could start a thread. Now I am just rambling.