|
Mike Buess
USA
3037 Posts |
 Posted - 06/08/2006 : 2:33:09 PM
|
I can reproduce that in Origin 7.5 but have no idea why it happens. A workaround that I've found is to combine your condition with another. For example, Data2!wks.ncols>=0 && exist(Data2)==2 (in that order) satisfies Origin at startup and works as intended. Note that Data2!wks.ncols>=0 works on its own but that condition is also met by a matrix window named Data2.
...Turns out that Origin will also fail to start when the colnum() function is used as the sole button condition. There may well be other functions that offend Origin on startup. An easy general solution seems to be to combine such conditions with @V>0 where @V is the Origin version number which is alway greater than zero. @V>0 && exist(Data2)==2 works fine but switching the order of the conditions or using exist(Data2)==2 alone will prevent Origin from starting.
Mike Buess
Origin WebRing Member
Edited by - Mike Buess on 06/08/2006 2:40:30 PM
Edited by - Mike Buess on 06/08/2006 3:36:09 PM |
 |
|
User defined buttons. activation by exist(win)==2
