Skip to main content
12 events
when toggle format what by license comment
May 7, 2015 at 11:08 comment added jkuczm @Kuba I agree, but I was bitten by it one time. I was aggregating options like this newOpts = {opt -> val, oldOpts}. I thought f[newOpts] would work the same as SetOptions[f, newOpts];f[] (except obvious fact that the latter sets options permanently), but it doesn't.
May 6, 2015 at 23:11 comment added Kuba @jkuczm I wouldn't say those are options for SetOptions, rather arguments. But good point.
May 6, 2015 at 16:35 comment added jkuczm @J. M., @Mr.Wizard Options[f] = {a -> x}; SetOptions[f, a -> y, a -> z] uses the rightmost option.
May 6, 2015 at 9:44 history edited Mr.Wizard CC BY-SA 3.0
added 860 characters in body
May 6, 2015 at 9:36 history edited Mr.Wizard CC BY-SA 3.0
added 860 characters in body
May 6, 2015 at 9:25 comment added J. M.'s missing motivation Wizard, sadly my memory fails me here. :( But at least for all the usual system functions, the "often" is in fact "always".
May 6, 2015 at 9:22 comment added Mr.Wizard @J. M. Can you give me an example of the "not" case?
May 6, 2015 at 9:21 comment added J. M.'s missing motivation More often than not, when two or more option settings are given to a function, the leftmost one is the one applied, and the rest are ignored.
May 5, 2015 at 8:18 comment added Mr.Wizard @Kuba I don't recall ever seeing that syntax produce an error, and in fact I have found internal implementations that result in duplicate rules so it seems to be accepted practice at WRI; however I added a GatherBy filter for this case in my own code here: (46925)
May 5, 2015 at 8:15 comment added Kuba Should I live with Button[...., ImageSize->200, ImageSize->333]?, it is ugly but works, could it be a problem anywhere?
May 5, 2015 at 8:09 history edited Mr.Wizard CC BY-SA 3.0
added 52 characters in body
May 5, 2015 at 7:55 history answered Mr.Wizard CC BY-SA 3.0