Recently active topics in Wuala tagged with icon

sometimes wuala is missing its tray icon (win32). sometimes when auto-logon to windows xp (for example autologin with tools like powertoys/tweakui) is activated, the wuala trayicon cant be created/registered as the traybar (explorer.exe components or such) havent been started yet.

im not into win32 api details, but i think i remember that with at least winxp and later windows builds new methods and calls have been implemented into windows to recreated/redraw/register the tray icons and tray-related stuff in case explorer.exe / desktop crashes or restarts and things like that.

please make wuala work properly with the windows tray area or at least add a real quit/shutdown icon on the wuala logon window, as wuala can only be exited properly with rightclick on the traybaricon and "exit" there for example when wuala is logged out. when the traybar icon is missing, there is only the really unclean and hardcore killing way of the wuala.exe process left for quitting wuala, which isnt really nice i suppose.

also, wuala doesnt react properly to wm_quit message that i tried to send with process.exe tool from beyondlogic guys.

C:\>process -q wuala.exe

Command Line Process Viewer/Killer/Suspender for Windows NT/2000/XP V2.03
Copyright(C) 2002-2003 Craig Peacock beyondlogic org
Sending PID 832 'wuala.exe' WM_CLOSE Message. Timeout is 60 seconds.
wuala.exe (PID 832) failed to respond to WM_CLOSE. Terminating Now.
Sending PID 832 'wuala.exe' WM_CLOSE Message. Timeout is 60 seconds.
wuala.exe (PID 832) has been closed successfully.

so maybe you guys can add proper wm_close message handling of the wuala main app, or fix the traybar/trayicon handling or add a real shutdown/exit function also to the logon-window or the main wuala window too.

would be great thanks.

hi there,

a main problem with the wuala project as whole is, that there is far too little information on technical details, far too little documentation and real information given by the developers.

people often wonder why the wuala software behaves this or the other way, search for solutions that are sometimes no real problems if the behaviour would be properly documented.

i started up some older build (winxp) wuala client after a while of downtime and it upgraded itself.
after logging in to the wuala network (username) the wuala client now works heavily on the wuala database files in probably reoganisation tasks (fragmentsxx.db and COMP-fragmentsxx.db files being messed with the whole time)

anyways so it literally took ages for this client to finish, and the connection status icon was yellow all the time. only after a long while, and when finally the insane diskactivity has finished, the connection status icon went green again.

ctrl+alt+d _shownetworkstats displayed that it wasnt connected to any supernodes during this period, hence the yellow icon i presume.

what makes me wonder if this is a neccessary behviour, that the client cant properly connect to the network until its finished with its database overhaul. maybe some multithreading designs could help, or maybe its just really the need to bring the database into a consistant and up-to-date state again before being able to add and fetch chunks of data again to and from it.

it would really be great if the wuala team could document its piece of software much more in detail.