theme.ui architecture
Robert... I was toying with UI other day, wanted to implement drag'n'drop functionality. I quickly cut'n'pasted code from freeampUI to Theme's Win32Window.h/cpp, so the window started to accept WM_DROPFILES. But then I even quicker got frustrated to death, could not figure out how to get the filenames to PLM. Spent time looking at class hierarchy and could not see a way (well, I'm not speaking inherited virtual functions and other wacky C++ encapsulation/data hiding stuff very fluently). Can you think of something? Else, I think theme.ui is too damn complex. I think I'll want to draw a hierarchy diagram. -- Valters "WaTT" Vingolds
Re: theme.ui architecture
I was toying with UI other day, wanted to implement drag'n'drop functionality. I quickly cut'n'pasted code from freeampUI to Theme's Win32Window.h/cpp, so the window started to accept WM_DROPFILES. But then I even quicker got frustrated to death, could not figure out how to get the filenames to PLM. Spent time looking at class hierarchy and could not see a way (well, I'm not speaking inherited virtual functions and other wacky C++ encapsulation/data hiding stuff very fluently). Can you think of something? That's still on our todo list -- don't worry about it. As you found out its not a trivial task due to some weird windows circumstances. Else, I think theme.ui is too damn complex. I think I'll want to draw a hierarchy diagram. I've seen worse. :-) The way the UI is brought up initially is too complex, and I will be revamping that code to make the apply button in the config dialog work. Other than that, I'm pretty happy with how things are organized, given that this thing has to work on multiple platforms that have little GUI structure in common. --ruaok Freezerburn! All else is only icing. -- Soul Coughing Robert Kaye -- [EMAIL PROTECTED] http://moon.eorbit.net/~robert
Re: theme.ui architecture
you get a pointer to the PlaylistManager in the FAContext that is passed to your UI when it is instantiated. Use this pointer to add items and access all other playlist functionality. you should also listen for the Playlist Events such as AddItem, UpdateItem, and MoveItem if you are implementing your own playlist manager... elrod Valters Vingolds wrote: Robert... I was toying with UI other day, wanted to implement drag'n'drop functionality. I quickly cut'n'pasted code from freeampUI to Theme's Win32Window.h/cpp, so the window started to accept WM_DROPFILES. But then I even quicker got frustrated to death, could not figure out how to get the filenames to PLM. Spent time looking at class hierarchy and could not see a way (well, I'm not speaking inherited virtual functions and other wacky C++ encapsulation/data hiding stuff very fluently). Can you think of something? Else, I think theme.ui is too damn complex. I think I'll want to draw a hierarchy diagram. -- Valters "WaTT" Vingolds
Re: theme.ui architecture
I must say I am a little lost. Where is that theme.ui everybody's talking about ? I took the latest freeamp from CVS but I can't find anything about a theme UI in it. Any idea ? Sylvain - Original Message - From: Mark B. Elrod [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, October 07, 1999 3:17 PM Subject: Re: theme.ui architecture you get a pointer to the PlaylistManager in the FAContext that is passed to your UI when it is instantiated. Use this pointer to add items and access all other playlist functionality. you should also listen for the Playlist Events such as AddItem, UpdateItem, and MoveItem if you are implementing your own playlist manager... elrod Valters Vingolds wrote: Robert... I was toying with UI other day, wanted to implement drag'n'drop functionality. I quickly cut'n'pasted code from freeampUI to Theme's Win32Window.h/cpp, so the window started to accept WM_DROPFILES. But then I even quicker got frustrated to death, could not figure out how to get the filenames to PLM. Spent time looking at class hierarchy and could not see a way (well, I'm not speaking inherited virtual functions and other wacky C++ encapsulation/data hiding stuff very fluently). Can you think of something? Else, I think theme.ui is too damn complex. I think I'll want to draw a hierarchy diagram. -- Valters "WaTT" Vingolds
Re: theme.ui architecture
I must say I am a little lost. Where is that theme.ui everybody's talking about ? I took the latest freeamp from CVS but I can't find anything about a theme UI in it. Any idea ? it's on the release-1-5 branch. And it and gcc-2.95.1 do not seem to want to play nicely. I'm working on it, though... stupid templates.
Re: theme.ui architecture
On 08-Oct-99 Tom Spindler wrote: it's on the release-1-5 branch. And it and gcc-2.95.1 do not seem to want to play nicely. I'm working on it, though... stupid templates. Compiles with 2 minor warnings in FreeAmpTheme.cpp with gcc-2.95.2pre2 here... Isaac
Re: theme.ui architecture
it's on the release-1-5 branch. And it and gcc-2.95.1 do not seem to want to play nicely. I'm working on it, though... stupid templates. Compiles with 2 minor warnings in FreeAmpTheme.cpp with gcc-2.95.2pre2 here... Oh, it _compiles_... it just fails when you try to run the sucker: ld.so.1: ./freeamp: fatal: relocation error: file ./plugins/theme.ui: symbol cop y__t18string_char_traits1ZcPcPCcUi: referenced symbol not found However, compiling with -fsquangle seems to get around this. It's definitely a bug in gcc 2.95.1, though. Incidentally, adding -fsquangle makes everything compile _and_ run, but it fails with "base/src/database.cpp:47: failed assertion `m_dbase'"
