No, but you can change what the save shortcut does. Normally you never have to save in idea, so it would be crazy for it to rebuild whenever it saves. For that reason, you kind of just have to hit rebuild (Ctrl+F9) instead of saving.

ok, ty

Just committed: ComboBox.validator moved to ComboBoxBase.validator to support ColorPicker and DatePicker as well

Also added

ComboBoxBase.required()

validator

I think

InstanceScoped

was a bad idea, it actually makes it hard to instantiate a Wizard and at the same time put data into it's scope. I'm thinking about simply removing it.

It should also be possible to make the Wizard part of the existing scope if one so chooses.

@edvin how is your shoulder today?

@ron It's much better, thank you 🙂 I didn't take any pills today, but I think I might have to soon. I have more mobility than yesterday, so I'm very optimistic.

@edvin I am glad you are feeling better already... but you should still take it easy eventhough I know that that is hard for you😉 Regarding the

InstancedScoped

I need to read more about scopes yet...so I can't say anything about that...you probably know best so go ahead and do what you think needs to be done 😀 (hoping to know more about the internals soon🙈 😀 )

@nimakro Thanks 🙂 Not used to doing nothing, but luckily it looks like I won't have to. Will try to stay away from the computer as much as possible this week though. I will experiment a little more with the instance scope, but pretty sure I made a mistake there. Nobody will probably even notice if I remove it now, might be harder down the line.

SmartResize.POLICY can now be installed by calling

smartResize()

on any

TableView

oh that is a nice one

that always felt a bit cluncky

Yeah, I hated it. Wondered about going overboard and adding

smartResize = true

as a parameter to the tableview builders, but that might be too much.

Just committed: SmartResize will automatically resize if the itemsProperty of the TableView changes value

is there a case where you don't want tableviews to smart resize?

@mikehearn I'm not sure, it seems to be the better choice for many situations. It might not be completely mature yet, but the API is probably all there. Do you think it makes sense to add it as an option in the builder, and maybe even consider making it default to true?

It would be a behavioral change for anybody that didn't configure a resize policy, don't know if that's smart.

I've started making some global default configuration options lately, so if we have a global

FX.defaultSmartResize = false

defined, the builder could be defined as

tableview(smartResize: Boolean = FX.defaultSmartResize)

for example.

This has turned out to be very useful for

defaultClosable

,

defaultSavable

and friends.

(Those other defaults are in the companion object for Workspace, this one could be inside the SmartResize companion object for example).

SmartResize.makeDefault = true

or something.

@mikehearn maybe if you have a composite view and don't want the TableView to affect other components?

Has anyone else noticed that the first event after start up seems to be a no-op, and then after that it seems like each event has the intended effect of the previous one (I'm talking specifically about mouse events on controls)

here's a demo https://vimeo.com/216006187

it probably makes sense to be the default, i'd imagine

@kastork That's because you're using the

menuitem

builder wrong 🙂 The op block for menuitem is the actual action.

@kastork Either remove the

action

wrapper inside it, or change

menuitem

to

item

, which behaves like you expect.

@kastork The initial

menuitem

builder was made this way because it was assumed that you normally never wanted to further configure the menu item, just supply the action. That assumption was probably not good, and it also breaks with how the other builders works. Therefore, the

item

builder was introduced. It might be time to deprecate the

menuitem

builder, because it causes confusion. If you just want to configure an action, you'd just do

item("My item").action { myAction() }

anyways.

@thomasnield I know you like the

menuitem

builder, but you see it keeps coming back to bite us in the ass 😢

I wonder if we can deprecate it and make sure IDEA helps you change from

menuitem(title) {}

to

item(title).action {}

.