Description: This Project is a control center module, giving the administrator a YAST-like, but configurable administration module.
The aim of the project is not to rewrite all administration/config tools, but giving the user a program for starting your config tools without to remember all the program names.
You can open all website-based configuration pages (e.g.:webadmin, cups,...) and applications.
The double click problem is solved in the version 0.1a on Debian. The default DOUBLECLICK_VALUE in the src/koast.h file is optimal.
I forgot to tell you about an other problem:
The koast configuration file is missing after installation. It must be copied manually. It is not a problem for me, because I create deb packages, but the others...
You are right.
I used the mouse-double-clicks.
Their is no other control-center-module using the double-click-event. I think, the Control Center can not handle this at all, or the second click is not taken into consideration by KDE Control Center. Is it possible to clear the second click after opening an application? There must be a solution for the problem.
sorry, that i didn't wrote back earlier,i was realy busy ;-)
i updated the apptlication to handle/skip the doubleclick event, the way you want...
if you still got some problems with the double click, try to play a little bit with the value DOUBLECLICK_VALUE in the top of the src/koast.h file.
just install the new one, the module will overwrite the old one, the configfile will not be touched....don't wory about the smaller size, every thing is still there (i just remove some tempfiles)
It can be compiled for Debian Sid/Kanotix, but every application run again after closing them. E.g. closing Synaptic Synaptic run again. It must be closed one more time.
Are you using the mouse-double-clicks? Thanks for the bug-report.
I noticed that the applications opens twice using the double-click-event. I was listening to the wrong event.
But after changing this, it still didn't work as i supposed.
So i was googling around and found
that the controll center is not handling the double-click-event. Unfortunately their is no other
control-center-module using the double-click-event for checking this problem.
So i guess this problem is one of the control-center and you are forced to use single-clicks.
Please let me know, when this wasn't your problem.
sorry..i see the idea..and the program is easy to understand..
but when i've created a menu..exemple:Administrator..and an application as submenu..example /usr/bin/konqueror..
The result is that i can see my conf(i had to create /usr/share/apps/koast with mkdir..) but when i click on the application..nothin happens..
:(
what do you mean, you had to create the folder /usr/share/apps/koast - did the install script not work?
is it possible that the application will open in the background (hidden by some other applications) or even opens on another desktop? that happens sometimes on my
"ubuntu amd64", but everything works fine on my "kanotix 32bit".
When nothing happens at all, do you see some error messages, starting the module from a terminal (kcmshell koast)?
sorry about that,
add the following line to the src/listloader.h
"#include <stdint.h>" (right to the other includes) and try again.
i'm interested in your results.
Ratings & Comments
10 Comments
The double click problem is solved in the version 0.1a on Debian. The default DOUBLECLICK_VALUE in the src/koast.h file is optimal. I forgot to tell you about an other problem: The koast configuration file is missing after installation. It must be copied manually. It is not a problem for me, because I create deb packages, but the others...
You are right. I used the mouse-double-clicks. Their is no other control-center-module using the double-click-event. I think, the Control Center can not handle this at all, or the second click is not taken into consideration by KDE Control Center. Is it possible to clear the second click after opening an application? There must be a solution for the problem.
sorry, that i didn't wrote back earlier,i was realy busy ;-) i updated the apptlication to handle/skip the doubleclick event, the way you want... if you still got some problems with the double click, try to play a little bit with the value DOUBLECLICK_VALUE in the top of the src/koast.h file. just install the new one, the module will overwrite the old one, the configfile will not be touched....don't wory about the smaller size, every thing is still there (i just remove some tempfiles)
It can be compiled for Debian Sid/Kanotix, but every application run again after closing them. E.g. closing Synaptic Synaptic run again. It must be closed one more time.
Are you using the mouse-double-clicks? Thanks for the bug-report. I noticed that the applications opens twice using the double-click-event. I was listening to the wrong event. But after changing this, it still didn't work as i supposed. So i was googling around and found that the controll center is not handling the double-click-event. Unfortunately their is no other control-center-module using the double-click-event for checking this problem. So i guess this problem is one of the control-center and you are forced to use single-clicks. Please let me know, when this wasn't your problem.
sorry..i see the idea..and the program is easy to understand.. but when i've created a menu..exemple:Administrator..and an application as submenu..example /usr/bin/konqueror.. The result is that i can see my conf(i had to create /usr/share/apps/koast with mkdir..) but when i click on the application..nothin happens.. :(
what do you mean, you had to create the folder /usr/share/apps/koast - did the install script not work?
is it possible that the application will open in the background (hidden by some other applications) or even opens on another desktop? that happens sometimes on my "ubuntu amd64", but everything works fine on my "kanotix 32bit".
When nothing happens at all, do you see some error messages, starting the module from a terminal (kcmshell koast)?ok form me in compilation.. Now i'm try to configure my own control center..if i understand.. gcc 3.4.6 on zenwalk
Compilation Problem on my Slackware 10.2 make[1]: Entering directory `/tmp/koast-0.1/src' if /bin/sh ../libtool --silent --tag=CXX --mode=compile i486-slackware-linux-g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/opt/kde/include -I/usr/lib/qt/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT -D_REENTRANT -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall -W -Wpointer-arith -Wwrite-strings -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -DNDEBUG -DNO_DEBUG -O2 -O2 -march=i486 -mcpu=i686 -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -MT koast.lo -MD -MP -MF ".deps/koast.Tpo" -c -o koast.lo koast.cpp; \ then mv -f ".deps/koast.Tpo" ".deps/koast.Plo"; else rm -f ".deps/koast.Tpo"; exit 1; fi In file included from koast.cpp:41: listloader.h:71: error: 'uintptr_t' is used as a type, but is not defined as a type. koast.cpp: In member function `void Koast::slot_listViewChanged(bool)': koast.cpp:205: warning: unused parameter `bool state' koast.cpp: In member function `void Koast::m_loadFile(const char*)': koast.cpp:288: warning: unused variable `STObject*pObj' make[1]: *** [koast.lo] Error 1 make[1]: Leaving directory `/tmp/koast-0.1/src' make: *** [install-recursive] Error 1
sorry about that, add the following line to the src/listloader.h "#include <stdint.h>" (right to the other includes) and try again. i'm interested in your results.