Thank you very much Zumi for your help:
I make you mods and now i can resize all my windows, the only i cant is GPSDRIVE, strange under matchbox i've no problem....
I can't try that now. I will compile a new cvs version from gpsdrive in the near future and I will try this out with that.
1.Can you tell me when fvwm starts problem will be fixed on SL6000?
Here's a 0.3.1-pre1 version. I will write changelog, futher plans and updated readme for the 0.3.1, but this is without "support".
http://web.interware.hu/radon/pda/fvwm-pda...e1_armv5tel.ipk2.Is it possible having in the bar the controllers for SD/CF an WIFI MEMORY/CPU as in matchbox ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88541\"][{POST_SNAPBACK}][/a][/div]
It will be supported, later, when I will concentrate on writing that FLTK ztaskbar applet.
If somebody has an idea, how to use matchbox applets under fvwm, that will come handy until there's proper support for everything in ztaskbar.
The reason why I really want to write every applet in one application is this:
Memory usage according to "ps x" command output):
ztaskbar: 2000KB
---
mp-applet-clock: 1968KB
mb-applet-battery: 1388KB
mb-applet-menu-launcher (this is the menu button): 2232KB
mb-applet-launcher (this launches an aterm): 1372KB
(others are like these)
So, every little knob on matchbox taskbar use a little less or as much memory as ztaskbar itself.
I don't expect that when there will be all the other applets integrated in ztaskbar (volume control, cpu/mem monitor, cf/sd monitor, wireless monitor, power saving options), its memory usage will go wild, so about 10-15MB... I think it won't be more than 5MB, in the worst case. So I vote for improving ztaskbar.
Zumi