From: Anjo K. <kr...@lo...> - 2004-12-07 14:25:40
|
Hi Timo, Am 07.12.2004 um 14:53 schrieb Timo Hoepfner: >> Set a rule where batchNavigationComponentName is D2WEmtpy (or=20 >> whatever the names are, I don't have the stuff handy here). > It's so easy if you know how... ? How about: (pageConfiguration =3D "Foo") =3D> batchNavigationBarComponentName =3D=20= ERXEmptyComponent [100] >> Add a rule with a higher prio and leave the RHS emtpy. But this may=20= >> not work because empty values might be "" not null. I don't know if=20= >> RuleEditor is fixed in that regard. > I have tried almost everything with RuleEditor, "" and "null" were=20 > certainly in it. Maybe some NullAssignment would be more elegant than=20= > my approach (or fixing RuleEditor...). So this isn't fixed... =A7$%&. You could actually edit the rule file=20 itself and remove the "value" from the "rhs" of the respective rule.=20 This change sticks as long as you don=B4t edit the rule again. And file = a=20 bug report against WO, of course. I really wish I had the time to=20 actually finish one of my many attempts to write a better RuleEditor:( >> Brr... at the very least you are creating one page and throw it=20 >> away... > So what to do then? Just copy *.wo and *.api every time? And hope you=20= > never forget to update the component if the "super" component is=20 > updated? Well... normally you will add functionality anyway, so you might as=20 well make a copy. But other than that, I don't have a good idea. Cheers, Anjo |