Hello, Mel Thank you for pointing out this mistake in the title. It's already corrected. Best Regards, Kostadin Dimitrov
I don't feel to bad about myself now for not seeing that the correct property name is "ButtonsPosition" and not "ButtonPosition". It would be more obvious to call it "ButtonPosition" rather than "ButtonsPosition": I'll bet that half of you still don't even notice the difference even though I've pointed it out. The plural of the word "Button" in the name "ButtonsPosition" because out brains tend to form preconceived ideas of how things should be due to exposure to them over a period of time and use. Hence one does not even see the extra "s" in the property name. You might say that this is not a great problem except that the error messages generated are not precise enough to tell us that the property does not exist: we get a generic error message, or none at all because in http markup errors are ignored and only visual discrepencies are generated. Anyway, this little out of normal spelling cost me a great deal of time trying to find the problem because of the bug associated with it at the same time. I would go out on a limb and say that the bug is that some one used ButtonPosition in stead of ButtonsPosition in the routine to move the button. Thanks, Mel