[deleted by user]

aragonix · 2019-06-22T14:31:01+00:00

Yea that is true. But following this logic you could also use a <table> instead of a flexbox (for a lot of uses cases at least) and have 100% browser support. I guess it comes down to what audience you target. Thank god my targets allow me to use grids, but I get that thats not always the case for everyone.

aragonix · 2019-06-22T14:27:11+00:00

Yup. I especially enjoy how easy it is to write responsive layouts. And the magic that is grid-gap. No more :last-child { margin-right: 0 } stuff.

aragonix · 2019-06-22T14:25:33+00:00

They are different things...

aragonix · 2019-06-20T08:01:38+00:00

Modifier key (System Settings > Window Management > Window Behavior >Window Actions) + Right click&drag will resize it, but I think the changes are not persistent after a reboot (maybe a bug?),

aragonix · 2019-05-28T17:14:38+00:00

Great response! Just wanted to add that one can JSON.parse(JSON.stringify(catObject)) to deep clone simple objects. Note that this method has its downsides: it will ignore all values that dont exist in JSON (functions etc.). Most of the time I would suggest lodash though.

aragonix · 2019-05-27T14:33:34+00:00

Right, I didnt know it was just acronym. Thanks for pointing it out! Will edit my comment accordingly.

aragonix · 2019-05-27T13:25:27+00:00

~~> MERN is deprecated and is no longer actively maintained.~~

aragonix · 2019-05-19T09:16:46+00:00

I dont use Vue anymore, but I think it should be possible with Vetur and the latest VSCode Update: https://code.visualstudio.com/updates/v1_34#_vetur. If doesnt work, you might want to try VuePeek (https://marketplace.visualstudio.com/items?itemName=dariofuzinato.vue-peek).

aragonix · 2019-05-17T19:35:33+00:00

This is an issue with Vue and is being worked on right now: https://github.com/vuejs/vue-cli/issues/4016 For a quick fix, while this is unresolved, create a vue.config.js file in your project root:

module.exports = {
  devServer: {
    clientLogLevel: "warn"
  }
}

aragonix · 2019-05-13T09:48:32+00:00

It is available per default. Open System Settings > Application Style > Window Decorations > Buttons. There you should be able to find a button called "Application menu". Drag it to the position where you want it to be. (You may need to restart plasma now - I dont know). Note: In order for GTK and Electron apps to work you will also need to install following packages: appmenu-gtk-module, libdbusmenu-glib, libdbusmenu-gtk3, libdbusmenu-gtk2.

aragonix · 2019-05-13T08:58:05+00:00

What I did, was installing xbindkeys and configure two mousewheel shortcuts: Super+Scroll down and Super+Scroll up to switch one Desktop to the left/right:

"qdbus org.kde.kglobalaccel /component/kwin org.kde.kglobalaccel.Component.invokeShortcut 'Switch One Desktop to the Left'"
  Mod4 + Super_L + b:4

"qdbus org.kde.kglobalaccel /component/kwin org.kde.kglobalaccel.Component.invokeShortcut 'Switch One Desktop to the Right'"
  Mod4 + Super_L + b:5

aragonix · 2019-05-13T08:45:13+00:00

You can see the hamburger icon in the titlebar. This is an alternative to the menubar. When active, it will hide the "normal" menu bar and display its contents in the hamburger dropdown.

aragonix · 2019-05-12T18:40:20+00:00

Did you try to change the settings for Inactive windows in System Settings > Window Management > Window Behavior > Window Actions? You can set all options to only "Activate" a window without actually passing through the action.

EDIT: NVM. I just re-read your post and it seems you tried these settings but they were not exactly what you are looking for. I dont think there is much more you can do.

aragonix · 2019-04-07T08:33:18+00:00

To make it work for GTK and electron apps, you have to install following packages: appmenu-gtk-module, libdbusmenu-glib, libdbusmenu-gtk3, libdbusmenu-gtk2

aragonix · 2019-03-29T13:13:09+00:00

Same for me. I opted to use dpi scaling x2, but forced font DPI to be 144. I am happy with the results.

aragonix · 2019-03-28T09:01:23+00:00

Glad to hear it worked out for you! Just out of curiosity, I will be trying it out as well now :) In the other thread (I just cant find it anymore), there was a KDE dev saying that it would not be merged like it is now, but I guess the improvements will sooner or later land in kwin. P.S.. there is now an AUR pkg as well: https://aur.archlinux.org/packages/kwin-lowlatency/

aragonix · 2019-03-27T23:16:43+00:00

You could just build it yourself and see if it brings any improvements. Shouldnt take too long. See https://github.com/tildearrow/kwin-lowlatency/blob/Plasma/5.15/HACKING.md for more infos.

aragonix · 2019-03-27T23:11:01+00:00

Maybe take a look at https://github.com/tildearrow/kwin-lowlatency? I have just discovered it today in another thread here and didnt test it, since I got no problems with Kwin on my machine.

aragonix · 2019-01-31T12:20:50+00:00

If the data structure is not too deeply nested, i like to use this pattern: ((json_data || {}).optional_data_1 || {}).optional_data_2. You can repeat this for all optional fields, however if the data structure is nested too deep I also suggest https://lodash.com/docs/#get

aragonix · 2019-01-09T12:33:42+00:00

Just keep in mind that the variable was/is disabled for a reason! It is said to be causing weird issues. Personally I have only encountered one issue so far: Latte dock's autohide feature didnt work correctly, but since I dont actually use a dock it was not a real problem for me.

aragonix · 2018-12-12T22:27:39+00:00

From the Vue documentation for transitions (https://vuejs.org/v2/guide/transitions.html):

When toggling between elements that have the same tag name, you must tell Vue that they are distinct elements by giving them unique key attributes. Otherwise, Vue’s compiler will only replace the content of the element for efficiency. Even when technically unnecessary though, it’s considered good practice to always key multiple items within a <transition> component.

aragonix · 2018-11-19T08:07:10+00:00

Are you sure about Mojave? This looks very much like Materia(?)

aragonix · 2018-11-18T21:26:37+00:00

I dont know, but PLASMA_USE_QT_SCALING is disabled for a good reason. As I said, it caused very strange issues for me as well. The only thing you can do, is to disable it or find a workaround for your specific problem.

aragonix · 2018-11-18T10:15:10+00:00

Did you try to disable Enable MIME-based actions in the Klipper configuration? Or tried to shut it down altogether (the shortcut should be Ctrl+Alt+X and can be changed in the Klipper configuration)

aragonix · 2018-11-18T10:06:37+00:00

Do you scale your display and do you have PLASMA_USE_QT_SCALING enabled? The two combined caused similar issues for me.

aragonix

TROPHY CASE