Happy New Year everyone! ![]()
I was working on MHWD and it’s almost ready (actually only some testing is needed) so I wanted you to present the design for KCM/Kirigami page.
I’m all ears to hear the ideas of what could be improved.
Happy New Year everyone! ![]()
I was working on MHWD and it’s almost ready (actually only some testing is needed) so I wanted you to present the design for KCM/Kirigami page.
I’m all ears to hear the ideas of what could be improved.
Happy new year! ![]()
Nice!
Feedback on the text:
The message that “no drivers available” could be perceived as a message that the hardware does not work correctly whereas it surely works as it is detected.
From what I recall when using windows, the first thing to do is go download a bunch of drivers when they are not there after installation and this seems to point to such a situation. So for the new user from the windows/apple world this might lead them in a wrong direction.
Rephrasing it to something like “Hardware detected and recognized” would be (in my mind) a better way to communicate the state of the hardware to the user.
When more modules/packages/drivers are available for detected hardware, does it show what is being used now?, so the user has a choice.
The interface looks good. Maybe you want to rename it to “hardware” or “driver” control panel. Cause this is the only function this has.
I wonder how a noob user (since the fancy gui is targeted at them, isn’t it) will be able to choose between 11 drivers. Especially since some of the options are going to cause a black screen on next reboot…and then…command line, manual chroot on the now default btrfs, nonworking mwhd and havind to sort it out with pacman. Which is a very non-noob procedure.
Maybe it is time to work on an automatic recovery procedure instead.
Looks good, very good.
My 2 cents, the label “No drivers available”, perhaps should be “No additional drivers available” since there must already be a kernel module running.
If the hardware is not supported, will it still show in the list?
The page is not for supported or unsupported hardware in my opinion (what does ‘unsupported’ mean?), but for the availability of installable drivers. But I agree it may be confusing, and should say when the hardware has already drivers from the kernel (that might be more difficult to do though).
//EDIT: tell us when a version is ready to be tested so we can compile it and check it out.
Build currently fails like by Omano. On XFCE.
[52/100] Scanning /home/teo/Downloads/manjaro-control-pane...ommon/src/TransactionAgentLauncher.cpp for CXX dependencies
FAILED: [code=1] mcp-qt/common/CMakeFiles/mcp-qt-common.dir/src/TransactionAgentLauncher.cpp.o.ddi
/usr/bin/c++ -DFMT_SHARED -DMCP_TRANSACTION_AGENT_PATH=\"/usr/bin/mcp-transaction-agent\" -DMCP_VERSION=\"0.1.0\" -DMCP_VERSION_MAJOR=0 -DMCP_VERSION_MINOR=1 -DMCP_VERSION_PATCH=0 -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_KEYWORDS -DQT_OPENGL_LIB -DQT_QMLINTEGRATION_LIB -DQT_QML_LIB -DQT_QUICKCONTROLS2_LIB -DQT_QUICKWIDGETS_LIB -DQT_QUICK_LIB -DQT_WIDGETS_LIB -Dmcp_qt_common_EXPORTS -I/home/teo/Downloads/manjaro-control-panel/packaging/src/build/mcp-qt/common -I/home/teo/Downloads/manjaro-control-panel/packaging/src/manjaro-control-panel/mcp-qt/common -I/home/teo/Downloads/manjaro-control-panel/packaging/src/manjaro-control-panel/mcp-qt/common/src -I/home/teo/Downloads/manjaro-control-panel/packaging/src/manjaro-control-panel/libmcp -I/home/teo/Downloads/manjaro-control-panel/packaging/src/build/_deps/libpamac-cpp-src/include -I/home/teo/Downloads/manjaro-control-panel/packaging/src/build/_deps/libpamac-build/src -isystem /home/teo/Downloads/manjaro-control-panel/packaging/src/build/mcp-qt/common/mcp-qt-common_autogen/include -isystem /usr/include/sigc++-3.0 -isystem /usr/lib/sigc++-3.0/include -isystem /usr/include/glib-2.0 -isystem /usr/lib/glib-2.0/include -isystem /usr/include/libmount -isystem /usr/include/blkid -isystem /usr/include/sysprof-6 -isystem /usr/include/libsoup-3.0 -isystem /usr/include/qt6/QtWidgets -isystem /usr/include/qt6 -isystem /usr/include/qt6/QtCore -isystem /usr/lib/qt6/mkspecs/linux-g++ -isystem /usr/include/qt6/QtGui -isystem /usr/include/qt6/QtQuick -isystem /usr/include/qt6/QtQml -isystem /usr/include/qt6/QtQmlIntegration -isystem /usr/include/qt6/QtNetwork -isystem /usr/include/qt6/QtOpenGL -isystem /usr/include/qt6/QtQuickWidgets -isystem /usr/include/qt6/QtQuickControls2 -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -Wp,-D_GLIBCXX_ASSERTIONS -flto=auto -O3 -DNDEBUG -std=c++23 -fPIC -Wall -Wextra -Wconversion -Woverloaded-virtual -pthread -D_FILE_OFFSET_BITS=64 -mno-direct-extern-access -E -x c++ /home/teo/Downloads/manjaro-control-panel/packaging/src/manjaro-control-panel/mcp-qt/common/src/TransactionAgentLauncher.cpp -MT mcp-qt/common/CMakeFiles/mcp-qt-common.dir/src/TransactionAgentLauncher.cpp.o.ddi -MD -MF mcp-qt/common/CMakeFiles/mcp-qt-common.dir/src/TransactionAgentLauncher.cpp.o.ddi.d -fmodules-ts -fdeps-file=mcp-qt/common/CMakeFiles/mcp-qt-common.dir/src/TransactionAgentLauncher.cpp.o.ddi -fdeps-target=mcp-qt/common/CMakeFiles/mcp-qt-common.dir/src/TransactionAgentLauncher.cpp.o -fdeps-format=p1689r5 -o mcp-qt/common/CMakeFiles/mcp-qt-common.dir/src/TransactionAgentLauncher.cpp.o.ddi.i
In file included from /home/teo/Downloads/manjaro-control-panel/packaging/src/manjaro-control-panel/libmcp/kernel/KernelTransactionBuilder.hpp:15,
from /home/teo/Downloads/manjaro-control-panel/packaging/src/manjaro-control-panel/mcp-qt/common/src/TransactionAgentLauncher.h:17,
from /home/teo/Downloads/manjaro-control-panel/packaging/src/manjaro-control-panel/mcp-qt/common/src/TransactionAgentLauncher.cpp:8:
/home/teo/Downloads/manjaro-control-panel/packaging/src/manjaro-control-panel/libmcp/kernel/KernelProvider.hpp:19:10: fatal error: coro/task.hpp: No such file or directory
19 | #include <coro/task.hpp>
| ^~~~~~~~~~~~~~~
compilation terminated.
[57/100] Linking CXX shared library libmcp/kernel/libmcp-kernel.so
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().
Aborting...