Object position by size and location


Recommended Posts

Not really the same thing, at least in the simplest implementation of your recommendation. You'd still have to KNOW, and therefore think about, the values of the properties you don't want to change. My point in specifying those properties is that it seems to me they define the object along the axes you're most likely to want to change independently. Move it but keep the same size, leave the left or bottom anchored but change the size, etc. So your change becomes more "object oriented" in the sense that you don't have to calculate and offset the effect on other properties you don't care about.

Link to comment
Share on other sites

There is a MoveBy() function of the control, otherwise you could design your own function to work the way you want. There are two trains of thought here: there are languages that offer lots and lots of functions that largely do the same thing (php is kind of like this), or there are languages that offer all the basic functions, and advanced functions for things that would be hard to do yourself (or slow in many cases for DAQFactory, like the search() function). We went the second route because truthfully, if you have lots and lots of functions, you can never remember what they are, and they still never do exactly what you want.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.