Kirogi issueshttps://invent.kde.org/utilities/kirogi/-/issues2022-03-01T21:13:16Zhttps://invent.kde.org/utilities/kirogi/-/issues/25QtGamepad blocks potential plans for a Qt 6 port2022-03-01T21:13:16ZAlbert Astals CidQtGamepad blocks potential plans for a Qt 6 portKirogi is the only KDE application that uses QtGamepad in KDE.
The Qt Company says that they are not interested in a release of the module as is.
They have [vague] plans to bring the functionality back as part of a module that would a...Kirogi is the only KDE application that uses QtGamepad in KDE.
The Qt Company says that they are not interested in a release of the module as is.
They have [vague] plans to bring the functionality back as part of a module that would also support VR controllers.
The code for qtgamepad is available on git and should be in a compilable state or very close to make it compile. Patches are welcome.
One suggestion from The Qt Company representatives would be to just copy the files over tp if Kirogi it is ported to Qt6 before the new Qt module is released.https://invent.kde.org/utilities/kirogi/-/issues/14Add build option to build without gstreamer support2020-07-09T10:15:35Zpatrick pereiraAdd build option to build without gstreamer supporthttps://invent.kde.org/utilities/kirogi/-/issues/17Add support for mavlink versions in findMAVLink.cmake2020-05-24T17:02:29Zpatrick pereiraAdd support for mavlink versions in findMAVLink.cmakeright now, there is mavlink 1.0 and mavlink 2.0, we should aim to use mavlink 2.0 since it's compatible with mavlink 1.0 and has more features.right now, there is mavlink 1.0 and mavlink 2.0, we should aim to use mavlink 2.0 since it's compatible with mavlink 1.0 and has more features.https://invent.kde.org/utilities/kirogi/-/issues/11Add video source settings2020-05-10T18:35:06Zpatrick pereiraAdd video source settingsRight now it's not possible to change how we are going to receive the videoRight now it's not possible to change how we are going to receive the videohttps://invent.kde.org/utilities/kirogi/-/issues/24Unable to click on any other buttons because of joysticks2020-03-10T13:31:36ZManav sethiUnable to click on any other buttons because of joysticks![kirogi2](/uploads/edfccc4a41b039b3a9459438adf5a235/kirogi2.gif) I am unable to click any other buttons the joysticks always interfere with them ![kirogi2](/uploads/edfccc4a41b039b3a9459438adf5a235/kirogi2.gif) I am unable to click any other buttons the joysticks always interfere with them https://invent.kde.org/utilities/kirogi/-/issues/23Icons not visible on non plasma desktop envs and window managers2020-03-09T12:47:43ZManav sethiIcons not visible on non plasma desktop envs and window managersNone of the icons load up in the i3 window manager since I don't have any icon pack installed . Add this to cmakelists so that the breeze icons become an optional dependency similar to what we do in AndroidNone of the icons load up in the i3 window manager since I don't have any icon pack installed . Add this to cmakelists so that the breeze icons become an optional dependency similar to what we do in Androidhttps://invent.kde.org/utilities/kirogi/-/issues/22Think about vehicle UI provider source2020-03-08T15:56:46Zpatrick pereiraThink about vehicle UI provider source1. Should we allow vehicle plugins to provide UI ?
2. Should kirogi provide the UI for the `AbstractVehicle` class ?
About 1., can result in a crappy UI with a windows 95 style where anyone can create the UI and resulting in a non unifo...1. Should we allow vehicle plugins to provide UI ?
2. Should kirogi provide the UI for the `AbstractVehicle` class ?
About 1., can result in a crappy UI with a windows 95 style where anyone can create the UI and resulting in a non uniform UI/UX problem, where each vehicle has it's own configuration and UI/UX.
About 2., we'll have an uniform UI/UX where kirogi code will try to deal with everything via information provided by each vehicle actions/capabilities.
This issue should be improved to seek 2. approach, showing how different and what kind of capabilities `AbstractVehicle` should deal with, if we fail to provide such thing, 1. could be a valid solution.patrick pereirapatrick pereirahttps://invent.kde.org/utilities/kirogi/-/issues/4Making video visible while in map view and making map visible while in camera...2020-03-03T12:51:56Zpatrick pereiraMaking video visible while in map view and making map visible while in camera viewThis allows the pilot to know where he's without changing to map viewThis allows the pilot to know where he's without changing to map viewhttps://invent.kde.org/utilities/kirogi/-/issues/19Add mavlink analyze tool to check for vehicle status and variables states2020-03-03T12:22:32Zpatrick pereiraAdd mavlink analyze tool to check for vehicle status and variables statesIt's important for the user to have access and see and real time the value of such variables in some mavlink messagesIt's important for the user to have access and see and real time the value of such variables in some mavlink messageshttps://invent.kde.org/utilities/kirogi/-/issues/6Send joystick button from frontend to backend2020-03-03T12:12:32Zpatrick pereiraSend joystick button from frontend to backendRight now we are only sending joystick position to the vehicle, we should also send the buttons state. Right now we are only sending joystick position to the vehicle, we should also send the buttons state. https://invent.kde.org/utilities/kirogi/-/issues/21UI: Fix the binding of virtual joysticks with each other2020-02-26T15:42:02ZSethuram SenthilkumarUI: Fix the binding of virtual joysticks with each otherThe joysticks gets bound with each other when 'left click' is held on one and 'right clicked' on the other.
![kirogi_joystick](/uploads/baa98b691a405cce1a99e12e4db75aa6/kirogi_joystick.mp4)The joysticks gets bound with each other when 'left click' is held on one and 'right clicked' on the other.
![kirogi_joystick](/uploads/baa98b691a405cce1a99e12e4db75aa6/kirogi_joystick.mp4)https://invent.kde.org/utilities/kirogi/-/issues/16Think about companion computer support2020-02-22T13:44:20Zpatrick pereiraThink about companion computer supportSome vehicles uses an embedded computer that provides a REST api and video camera services to configure and get system status.
It may be important to integrate such system with kirogiSome vehicles uses an embedded computer that provides a REST api and video camera services to configure and get system status.
It may be important to integrate such system with kirogihttps://invent.kde.org/utilities/kirogi/-/issues/9UI: Add parameters editor2020-02-21T09:18:24Zpatrick pereiraUI: Add parameters editorRight now I have two tips of mockups, the classic one used between different GCS:
![deepin-screen-recorder_qhot_20191226201310](/uploads/615b369d510fb92ea7f195952db240c1/deepin-screen-recorder_qhot_20191226201310.gif)
And a new one base...Right now I have two tips of mockups, the classic one used between different GCS:
![deepin-screen-recorder_qhot_20191226201310](/uploads/615b369d510fb92ea7f195952db240c1/deepin-screen-recorder_qhot_20191226201310.gif)
And a new one based in the new OS that need to aggregate settings:
gif: https://gfycat.com/joyfulscarceanglerfishhttps://invent.kde.org/utilities/kirogi/-/issues/12UI: Add parameters editor2019-12-27T00:10:51Zpatrick pereiraUI: Add parameters editorRight now I have two tips of mockups, the classic one used between different GCS:
- This uses the left part of the windows to list and filter the parameters
- The main space is used to show the controls and information about the selected...Right now I have two tips of mockups, the classic one used between different GCS:
- This uses the left part of the windows to list and filter the parameters
- The main space is used to show the controls and information about the selected parameter
![deepin-screen-recorder_qhot_20191226201310](/uploads/615b369d510fb92ea7f195952db240c1/deepin-screen-recorder_qhot_20191226201310.gif)
And a new one based in the new OS that need to aggregate settings:
- This uses the entire space space available to show all parameters
- The top part of the windows has a search input
- When selecting the parameter group, the window will display the parameters inside the group and the configuration
for the selected parameter
![deepin-screen-recorder_Select_area_20191226203954](/uploads/a775383a93b00d78af51e50bb50a5572/deepin-screen-recorder_Select_area_20191226203954.gif)https://invent.kde.org/utilities/kirogi/-/issues/10Add connection settings2019-12-26T23:36:35Zpatrick pereiraAdd connection settingsRight now it's not possible to change how you are going to connect with the vehicleRight now it's not possible to change how you are going to connect with the vehiclehttps://invent.kde.org/utilities/kirogi/-/issues/7Rework actual HUD2019-12-26T23:15:17Zpatrick pereiraRework actual HUD- [X] Redesign the interface to be closer to a airplane HUD
- [X] Include yaw indicator
- [ ] Add full roll rotation
- [X] Add pitch values
Example:![kirogi](/uploads/aca5fc48c9d4f534e15ece2fe111c785/kirogi.png)- [X] Redesign the interface to be closer to a airplane HUD
- [X] Include yaw indicator
- [ ] Add full roll rotation
- [X] Add pitch values
Example:![kirogi](/uploads/aca5fc48c9d4f534e15ece2fe111c785/kirogi.png)patrick pereirapatrick pereirahttps://invent.kde.org/utilities/kirogi/-/issues/8Add joystick settings2019-12-20T00:26:38Zpatrick pereiraAdd joystick settings- [ ] Exponential fitting
- [ ] Throttle centralization
- [ ] Add offsets
- [ ] Add deadzones
- [ ] Add sticks and buttons visual feedback
- [ ] Add calibration procedure- [ ] Exponential fitting
- [ ] Throttle centralization
- [ ] Add offsets
- [ ] Add deadzones
- [ ] Add sticks and buttons visual feedback
- [ ] Add calibration procedurehttps://invent.kde.org/utilities/kirogi/-/issues/2Protocol should not be part of the vehicle plugin but implemented in a differ...2019-12-15T15:28:28Zpatrick pereiraProtocol should not be part of the vehicle plugin but implemented in a different waySuch approach helps with two things:
- Remove protocol specific code from vehicle code
- Use only high abstraction level functions related to vehicle protocol
- Removing protocol related code from our actual plugins will not break compat...Such approach helps with two things:
- Remove protocol specific code from vehicle code
- Use only high abstraction level functions related to vehicle protocol
- Removing protocol related code from our actual plugins will not break compatibility with
future plugins that want to implement privated protocol communication layers.
Alternatives:
- My suggestion is to move the communication protocol from the vehicle plugin layer
to be part of kirogi main code.
- I was thinking initially to move the protocols to a plugin like architecture,
but the protocols can be really different from each one.https://invent.kde.org/utilities/kirogi/-/issues/3vehicle communication class should not create connection code from the ground up2019-12-15T15:26:07Zpatrick pereiravehicle communication class should not create connection code from the ground upWe should abstract the communication and connection layer to a simple IO abstract object.
Example:
- AbstractLink
- UdpLink
- TcpLink
- SerialLink
- FileLink
All classes share a simple logic:
- connect(QString): connect(...We should abstract the communication and connection layer to a simple IO abstract object.
Example:
- AbstractLink
- UdpLink
- TcpLink
- SerialLink
- FileLink
All classes share a simple logic:
- connect(QString): connect("udp:0.0.0.0:14550"/"serial:/dev/ttyUSB0:115200"/...)
- isOpen()
- newData(QByteArray)
- write(QByteArray)
Everything related to writeDatagrams, clients, serial timer latency and everything else
should be provided and done by the classes and not by vehicle side.https://invent.kde.org/utilities/kirogi/-/issues/5Vehicle icon in map does not point vehicle orientation2019-12-15T15:17:14Zpatrick pereiraVehicle icon in map does not point vehicle orientationIt's not possible to know vehicle orientation from map viewer
![image](/uploads/cd5bdce1af76e5bbdfa0e95facd7b5d6/image.png)It's not possible to know vehicle orientation from map viewer
![image](/uploads/cd5bdce1af76e5bbdfa0e95facd7b5d6/image.png)