- User Since
- Sep 27 2016, 1:59 PM (63 w, 5 h)
Tue, Nov 28
One thing that i have noticed from my project is that non kde people try to often help via the github fork . We should maybe find a way to work with PRs made via Github. Submiting a Pr then having it autoclose and told go make an account here and get anarchist and do your commit this way , then your github name (or email) is not ok because it usually just a nickname this now creates a git configuration burden to fix before contrubiting.
The only issue I could see with making this happen is Calamares is that not all distros are using it. Some distros (such as arch ) will never use it This creates inconsistancy for KDE users. That is the reasaon I suggest we do it on first login.
Mon, Nov 27
I think one way to add to the polish is to have new users do a wizard on their first login to a kde session. This wizard will invite the user to configure kde how they want it Look and Feel. KDE3 used todo this and I propose the new one follows the KDE3 method. First the user would be asked how they want the desktop to Feel some options could include default KDE, mac like , windows like , unity like, custom, etc. Provide some kind of prevew when selecting the options with descriptions here. This step would set up plasma and kwin, Then we move on to the 'Look' Part. Give the user options to customize the color scheme and widget set background, and other look options like icon theme . Then do the About me portion where you can set your user icon and fill out their Telepathy stuff. and then be sure to tell them more settings can be changed In system settings . Also provide a way to make it easy for users to make a Look and Feel theme from their settings so they are less afraid to try new things.
This removes the runtime problem referanced in the bug above.
Thu, Nov 23
- Update base
- Patrick suggestions
Yes and no M18 does disable the steppers on some firmwares. This will disable the power being sent to those motors after some delay . This is from the perspective the samething . The main differance being that M84 is supported by most all of the reprap firmwares.
- Adjust wording of doxygen comment for setIdleHold
- Added Line in gcodetests
- Fixed typo in atcore.h
- Removed auto added amp; in mainwindow.ui
Fri, Nov 17
I found the issue. QMultimedia has a problem with PRIME/BUMBLEBEE Laptops with the gstreamer-vaapi parts . So if you have one of these devices remove the vaapi package for gstreamer and it will work.
Wed, Nov 15
- Adjust indents for if blocks
Tue, Nov 14
Mon, Nov 13
- Use apt instead of apt-get
- Remove unNeeded -y
Nov 12 2017
Nov 10 2017
Nov 8 2017
Well you would need to create several instances of atcore and then you can just connect to the "current" one and maybe have some way to switch between them .. I think It would be just be easier to run a second (or third client)
Nothing shows up in the media widget other then a black frame.
Tested with mjpeg streamer (http stream) and the internal web cam of my laptop (v4l2:///dev/video0) both result in no frames being shown .The light on my camera turns on so the device does seam to get opened.
No errors are shown in the app output or in the application
Video options should be moved into a common settings dialog, most camera paths are not going to change. This will help also when / if we have support for multi preview streams
Not sure a pause/ play button is needed here. I don't forsee pausing the stream And we can use the finishedEditing () signal to do the connect / disconnect for the device.
Nov 7 2017
Nov 6 2017
- remove full path from macdeployqt
- remove == for = make sure space after all then
- fix = != ==
- fix typo
- Less if
Nov 5 2017
- Travis Autobuild working appimages
Nov 3 2017
- Update Version to 0.90.2
Nov 2 2017
- Update the icon
Nov 1 2017
This should be done with the connection dialog. Unasigning myself .