Way cool Timon!

13bpower said:
Maybe this should be the default behavior for any folder in the dock?

I would like that too!

spacebetween said:
I can't get the video to play correctly. :-

You must be on windows ;)

It was encoded with ffmpeg as mpeg4, and windows doesn't support that out of the box. Something about the header that ffmpeg uses, FMP4. I was having the same problem with my movies that's why I know now ;) You have to go here and download ffdshow for windows play back.

http://sourceforge.net/projects/ffdshow

groo028 said:
patch: **** malformed patch at line 2569: Index: applets/stack/stack.desktop

I can confirm that too.

Timon said:
It's goal is to have a folder as backend to store files in. You can drag'n'drop files into the stack (which will be copied to the backend folder). From the stack you can launch files or drag'n'drop them to some application.

One question Timon.... ?

I would prefer to have another "default" container folder then
/tmp/12123 ( I know I can change it)

Perhaps I missed something how this works... ? ;-)

DBO said:
erm I get a white bar with it, how did you fix it groo028?

I also got a white bar, just restart session, or the whole system. It might work.

Check you got the updated patch.

groo028 said:
cool..it works...but how do i get an item out of the stack?

You can add/delete things from the backend folder. These changes are seen in the applet. Removing things directly from the stack is in my TODO list.

DBO said:
erm I get a white bar with it, how did you fix it groo028?

A white line is caused by first startup (gconf schemes are installed), inaccessible backend folder (default folder is /tmp/[some number], default icon cannot be found/loaded (uses "folder-drag-accept"-icon) or low cpu resources (cannot create icon fast enough).

markitoxs said:
Just noticed that the "popup does not close when I click on an image or item of the list, is this correct?

The popup should disappear when it looses focus.

plunn said:
Yes, Ive seen that but I thinking about users which never goes under the hood and looks... The Gnome Way... "Failsafe" :-)

It's the AWN way to store/use settings via gconf. In the end it should be alterable via a GUI, for now this fits.

DBO said:
and ruin my uptime? Really though there has to be a more logical reason behind it... If restarting fixes it Im guessing something in /tmp has to be cleared out

I'm not running it, so this is just a guess, but restarting usually means gconf schema was added or changed. You can simply restart your gconf deamon by executing this command as your normal user:

killall -HUP gconfd-2

Give it a try