Hi all,
I am just working on my first Quasar project ( and its turning out nicely ). I thought I’d share this incase it is useful to anyone. I have been using tachyons for most of the styling:
and I have found it to be quite nice for layout in most cases. I notice Quasar has a few css items that would be duplication such as some colors, etc. I thought I’d share it incase it might be useful as an addition to the framework or to others for their layout.
Looks like its super awesome. Thank you!!
I’m seeing an odd behavior with a side bar. I have the left sidebar and I have some q-side-link’s in it and they work fine, but I have an icon bar that opens the sidebar. Some of the icons open it and some change the route using the this.$router.push({name: ‘blah’}) method. If I open the sidebar and then change the route using one of the icons outside the sidebar, when I go to close the sidebar either with the close button I have or clicking the layouts overlay, the route goes back to where I had it when the sidebar opens, then if I click again it closes the sidebar. Anyone else run into this?
Thanks Nicholas for your confirmation.
I just noticed the other post mentioned the extras: http://forum.quasar-framework.org/topic/507/v0-14-beta-important-notice
And I see I have “quasar-extras”: “0.0.7” after installing it.
I ended up using window.scrollTo(0, 0) in the router afterEach for cordova, So far so good.
Enjoy the well deserved vacation!!
@ssuess I was able to get it to build if I open the workspace and change it to use legacy build mode from the workspace settings. Nice to see androidVersionCode added! I suppose that means the other version prop will be used for ios.
YES! - Auto-inject Quasar stylus variables to any .styl file
Maybe helpful, maybe not 
but I was facing a drawer with a q-scroll-area that was working and then it stopped working when I converted some content inside to use v-for, I was about to either just go with a div with overflow auto or look at calculating as mentioned above and then I added another div and it started working again. So I have a q-drawer with div.column, a couple div.col, then a div.col with the q-scroll-area using class=“fit” inside and at this point it was not working, then I added one more div (I used div-auto because of the design) and the scroll bar started working again.
I did also just notice that if I check safari I had native scroll bars appearing on one of the parent divs ( I have not looked into which) so out of curiosity I changed the drawer to behavior=“mobile” and the q-scroll-area stopped working again. Sig, so I suppose its back to calculating and a bit of extra height somewhere must be what made it work again.
I want to click the no down with ie11 choice, but I’m still supporting it currently.
I just did this upgrade: @quasar/extras: 1.3.3 → 1.4.0
quasar: 1.5.11 → 1.7.1
@quasar/app: 1.4.3 → 1.5.0
Not sure which version the change happened, but it looks like .q-btn picked up align-self: center was that intentional? I noticed because after upgrading I have a div.column with a few QButton’s in it and they are now centered when they previously were not.
Interesting, will have to check this out
@jaysaurus Everything had been working fine until I build and run the actual electron build. I’m only using createSharedMutations to share data between 2 electron browser windows. If I use the createSharedMutations plugin and I do the required step of importing the store into electron-main.js, when I build & run it I immediately get an error notice that it cannot find the module ‘vue’. It works fine when I run quasar dev -m electron
@s-molinari @metalsadman any thoughts on why this might be happening?
Seems to work if I go back to electron-main with my value first with ipcRenderer then from there dispatch is used. Curious if you found a better way.
@jaysaurus Were you able to get this working. I’m hoping to be able to call an action from one BrowserWindow and have another one pick up the change. Its for an array of objects.