Prev: Windows version
Next: ChildAppWindow in WED
From: Alessandro Antonangeli on 10 Feb 2010 12:38 Il Wed, 10 Feb 2010 18:36:07 +0100, Harry B. ha scritto: > Wolverine, > > can you explain more detailed how you found the Hex-Values, please? > > TIA, > Harry B. Just look in the help for OwnerAlignment -- Ciao, Alessandro
From: Harry B. on 10 Feb 2010 13:02 Alessandro, I've read the online help already, but I don't understand it! I use such an owner aligenment form, but I found the values by try and error only. Here an example from the online help: "MLE5 will adjust its size with 1/4 and 1/3 and its position with 1/2 of the height and 2/3 of the width" MLE5 is one MLE on the right side and the second from the bottom. And if I take the mentioned values the dialog looks fine. But why should I use 1/4, 1/3m 1/2 and 2/3? Lets take 1/4. 1 is called factor and 4 is called divisor. So 1/4 from what? Why exactly these value? (How) can I calculate such a value? Harry B.
From: Alessandro Antonangeli on 10 Feb 2010 16:09 Il Wed, 10 Feb 2010 19:02:44 +0100, Harry B. ha scritto: > Alessandro, > > I've read the online help already, but I don't understand it! I use such > an owner aligenment form, but I found the values by try and error only. > > Here an example from the online help: > > "MLE5 will adjust its size with 1/4 and 1/3 and its position with 1/2 of > the height and 2/3 of the width" > > MLE5 is one MLE on the right side and the second from the bottom. And if > I take the mentioned values the dialog looks fine. But why should I use > 1/4, 1/3m 1/2 and 2/3? > > Lets take 1/4. 1 is called factor and 4 is called divisor. So 1/4 from > what? Why exactly these value? (How) can I calculate such a value? > > Harry B. I'm not expert, I just tryed for curiosity of Sebastián example Best way is to make a win and put some controls on it (like the one of Phil) and try. There are 4 couple of byte: the first couple is the Height, the second is the width of the control, the third is the Y position and the last is the X position. If all are 0 no movement or resize. Otherwise it means that the control is resized or moved of n/m the owner window size/position If for example u put 1/2 for size (0x12120000), the control will be resized the half of the resize of the window, so if the window is increased of 50 points, the control is increased of 25. So, for the example of Phil, 1/2 is the right value because in vertical and orizzontal there are 2 groups of control, and each group must be resized of half the resize of the window. If for example you had 3 control in orizzontal, all to resize, 1/3 would be the right value. For the moving a bit more attention is needed: the first control (the one on the left) is not to be moved, the second is to be noved of 1/3 of the resize and the 3rd control is to be moved of 2/3 of the resize. The rule is (ControlPosition-1)/NumberOfControl: that is 0/3, 1/3 and 2/3 the value are (not dealing with vertical size): 0x00130003 0x00130013 0x00130023 Hard to explain, and in english also worst! HTH -- Ciao, Alessandro
From: Geoff Schaller on 10 Feb 2010 16:22 Show us the line of code please. This should be trivial (Or you have dll hell) "Philippe Mermod" <pmermod(a)REMOVEpkl.ch> wrote in message news:7tfrjmF7esU1(a)mid.individual.net: > Hi Alessandro, > > I have the following error when executing your sample under VO > 2822 (With Vista Sp2 - x86) : > > http://www.pkl.ch/dev/screenshots/alessandro.png > > Somebody has seen this before ? > > -- > Phil Mermod > Crystal Reports Library for Visual Objects > http://www.pkl.ch/dev/ > > > Alessandro Antonangeli wrote: > > > > Il Wed, 10 Feb 2010 13:09:19 +0000, Philippe Mermod ha scritto: > > > > > > Hi Alessandro, > > > > > > Can you send me your sample by email ? > > > > > > Thanks, > > > > > I sent > > > > Anyway nothing different from what Sebasti�n posted. > > > > The sample is with 5 groups of element (3 upper and 2 lower), > > I was just plaiyng to see how it works.
From: Geoff Schaller on 10 Feb 2010 16:26
Harry, Please, such basic questions. LOOK AT THE SDK. The entire source to this process is there. Everything - how it is derived, all the constants, everything. Look at the method oWindow:__AlignControls() You could easily add specific alignment options with minimal fuss. (This goes for Philippe too who has been around a lot longer...) Geoff "Harry B." <bongoplayer(a)gmail.com> wrote in message news:hkusc4$m93$1(a)news01.versatel.de: > Alessandro, > > I've read the online help already, but I don't understand it! I use such > an owner aligenment form, but I found the values by try and error only. > > Here an example from the online help: > > "MLE5 will adjust its size with 1/4 and 1/3 and its position with 1/2 of > the height and 2/3 of the width" > > MLE5 is one MLE on the right side and the second from the bottom. And if > I take the mentioned values the dialog looks fine. But why should I use > 1/4, 1/3m 1/2 and 2/3? > > Lets take 1/4. 1 is called factor and 4 is called divisor. So 1/4 from > what? Why exactly these value? (How) can I calculate such a value? > > Harry B. |