Well, I’m about to start project to replace an old Adobe Flex application, and I’m leaning towards Quasar+Electron… yours is practically the first result I Googled and it’s very instructive (although recreating the file explorer isn’t the most useful application for me lol)

So, thank you.

10 hours ago? Fantastic timing, Hawkeye!!

@Martin Of course, I’ve just realised the weight of a .png is negligible

Nonetheless, I’ve printed it and pinned it on the wall above my monitor for easy reference as I’m about to dive into Vuex and AXIOS (god help me)

@mariaczi said in How to add quaternary color ?:

I did try to just add $quaternary= #E28413 to app.variables.styl

That is correct.

It’s possible your project is configured to use the default Quasar stylesheet, rather than your custom theme…

Have a look in the App.vue file for something like the code below…

// === DEFAULT / CUSTOM STYLE ===
// WARNING! always comment out ONE of the two require() calls below.
// 1. use next line to activate CUSTOM STYLE (./src/themes)
require('./themes/app.' + __THEME + '.styl')
// 2. or, use next line to activate DEFAULT QUASAR STYLE
// require('quasar/dist/quasar.' + __THEME + '.css')
// ==============================

Notice I’ve commented out option #2 (default quasar style) and enabled option #1 (custom theme styles)

TBH I didn’t pay attention to the path, just the ${} syntax. My bad, sorry.

Is this in a plain HTML template, or are you using some custom templating engine instead?

If the former, then I don’t think ${foo} does what you think it does. Try this instead…

<img :src="'/assets/' + account.avatar" />

The first pic in particular is worth its weight in gold.

@eliashdezr

Try adding the command “debugger” in your source code where you’d like a break point to occur. That oughta stop it in its tracks! (A kludge, but maybe better than nothing.)

Like you, I’m also having major problems debugging in Chrome (and FireFox) since moving to Vue 2/Quasar 0.8+/Webpack 2 (<— One of those is the culprit!)

Under V1, I used to be able to click on the error message in console and link straight to the mapped (i.e. readable) source-code, and step through it. Now, unless the error occurs during the build or I manually insert “debugger” into the source code, I’m usually taken to the Vue internal function that “rehtydrates” the component into JS. Have tinkered & looked for a solution for ever with no luck, so if you find it please let us know!!

Also, I had some partial success by selecting “Break on uncaught expection” from Chrome debugger, although it only seems to work sporadically. sigh