@jmg1340 said in Popup edit: save & cancel:

On the other hand, in the CANCELED HANDLER, how do I set the original value (initialValue). That is to say: Do I Have to put a command like this: props.row.name = initialValue ?

you don’t need to. like i said, the value will revert back to initialValue when cancel event is emitted. if you want to do other operations after any event is emitted on the component then you pass a method like in my example above, otherwise just leave it be.

can’t reproduce that one in your image, maybe add a class gutter-sm on the div containing your 2 q-input’s. https://codepen.io/anon/pen/yQMOOL

<q-select :value="model" @change="val => { onValueChange() }" :options="options" /> https://quasar-framework.org/components/select.html#Vue-Events

q-popup-edit will emit save event on pressing enter key, clicking away from the component or if you press save/set button (if you enabled Buttons) if the initialValue has changed, cancel event will be emitted if you press escape key or if you press cancel button (buttons enabled) any edit will revert to its initialValue.

if you want to check the values emitted from those event you pass a method like so @save="saved" and @cancel="canceled".

...
methods: {
  saved (val, initialValue) {
    console.log(`original value = ${initialValue}, new value = ${val}`)
  },
  canceled (val, initialValue) {
    console.log(`retain original value = ${initialValue}, canceled value = ${val}`)  
  }
}
...

@stuartcusack said in How to define electron only packages?:

I’m trying to fix the spacing in my code above but “content flagged as spam by Askimet??”

just wait few mins and submit your edit again.

the error message is correct, since you put it in the wrong plugins section, in your case not the one under quasar, so it does look into the said “src/plugins/” directory.

iirc, someone made it to work as a plugin, i don’t know about vidyo. maybe try search function in here or at the quasar github page about it.

yep, that’s what i’ve been struggling to find too avoiding two way binding to get proper handle on the value. i’m always reluctant to use refs or any dom way coz it seems hacky, but gotta do most of the time specially on edge cases shrugs.

You’ll still need to build two separate build for different themes, then probably in your landing page you’ll have to detect what platform the user is currently on and redirect them to the appropriate themed servers. What’s stopping you from building two themes tho? since you can do just quasar build -m pwa -t ios for IOS themed build or quasar build -m pwa for the material one and still maintain one codebase.

@toymachiner62
use :width="392" or width=392.