1 Apr 2008 09:45
1 Apr 2008 19:46
Re: About tlayouter
Martin Schreiber wrote:
> wahono wrote:
>
> > How to make children of tlayouter resize the width when tlayouter.width
> > is resized (with anchor)? (margin for every children is fixed)
> >
> anchors:= [an_top,an_left,an_right] if there is one column only or with
> tsplitter with options spo_hprop set between the widgets.
>
> Martin
>
With one column, its ok to use anchor, but with many columns is too
difficult to apply with tsplitter. Than I try to modify tlayouter, maybe
you can improve it, at the moment my adding is ok for me.
I add plo_syncwidgetsize in placeoptionsty adn I modify
tlayouter.updatelayout procedure with this :
procedure tlayouter.updatelayout;
var
ar2: integerarty;
space,margin: integer;
procedure calcarray(const awidgets: widgetarty; const awidth: integer;
const amin,amax: integer);
var
int1,int2: integer;
rea1,rea2: real;
(Continue reading)
1 Apr 2008 19:58
Re: About tlayouter
I think again, how if widget is sized automatically (not sync) with
replace :
if plo_syncwidgetsize in fplace_options then begin
if lao_placex in foptionslayout then begin
rea1:= (innerclientsize.cx-space-(margin*2)) /
(high(awidgets)+1);
int2:= round(rea1);
for int1:= 0 to high(awidgets) do begin
awidgets[int1].width:= int2;
end;
end else
if lao_placey in foptionslayout then begin
rea1:= (innerclientsize.cy-space-(margin*2)) /
(high(awidgets)+1);
int2:= round(rea1);
for int1:= 0 to high(awidgets) do begin
awidgets[int1].height:= int2;
end;
end;
1 Apr 2008 11:47
Re: About tlayouter
Martin Schreiber wrote:
> The problem of the proportional widget sizes is how to store the reference
> values, tsplitter does it that's the reason why I suggested to use
> tsplitter. If you use splitters you probably don't need a tlayouter as
> container. Don't forget that you will get rounding errors with your method
> of using the same integer value for all widgets. It is planned to add a
> proportional size mode to tlayouter but the reference value problematic is
> difficult to solve.
>
> Martin
I think the real number is result an edge, this problem can be fixed
with resizing again one of widget size, and exactly just 1 pixel. This
is my solution.
if plo_syncwidgetsize in fplace_options then begin
if lao_placex in foptionslayout then begin
rea1:= (innerclientsize.cx-space-(margin*2)) /
(high(awidgets)+1);
int2:= round(rea1);
for int1:= 0 to high(awidgets) do begin
awidgets[int1].width:= int2;
end;
int1:=innerclientsize.cx-space-(margin*2)-childrenwidth;
if int1<>0 then awidgets[high(awidgets)].width:=
awidgets[high(awidgets)].width+int1;
end else
if lao_placey in foptionslayout then begin
rea1:= (innerclientsize.cy-space-(margin*2)) /
(Continue reading)
1 Apr 2008 11:53
1 Apr 2008 11:58
1 Apr 2008 08:46
Re: tmemoedit and trecordband
Attid wrote: > > i add tbandarea at report > set options to bo_once > move my_recodband at recordband (cut and paste) > > after it i see 1 page with 1 my_recordband =( > The single recordband is printed because you set bo_once, you normally don't set bo_once if you set empty to false in onbeforerender. Did you lose the value of onbeforerender with cut/paste? Martin
1 Apr 2008 09:16
Re: Which FP units does MSEgui use ?
IvankoB wrote: > both in the default and the max build configurations ... > > Needed to clarify the package deps. > Has FPC 2.2.0 the units already split into packages? For fixes_2_2: rtl/units/$fpctarget packages/libc/units/$fpctarget packages/x11/units/$fpctarget packages/fcl-image/units/$fpctarget packages/pasjpeg/units/$fpctarget packages/paszlib/units/$fpctarget packages/fcl-base/units/$fpctarget packages/hash/units/$fpctarget packages/fcl-db/units/$fpctarget packages/postgres/units/$fpctarget packages/iase/units/$fpctarget packages/mysql/units/$fpctarget packages/sqlite/units/$fpctarget packages/odbc/units/$fpctarget > Also a Q: > > why are some ( DB etc ) MSEgui units not smatlink ready (dont' have > lib*.a versions ) ? Works for me, there is a libpmsedb.a.(Continue reading)
1 Apr 2008 09:21
Re: tmemoedit and trecordband
Hello, Martin! You wrote on Tue, 01 Apr 2008 08:46:55 +0200: MS> Attid wrote: >> i add tbandarea at report set options to bo_once move my_recodband at >> recordband (cut and paste) >> after it i see 1 page with 1 my_recordband =( MS> The single recordband is printed because you set bo_once, you MS> normally don't set bo_once if you set empty to false in MS> onbeforerender. bo_once i set only on tbandarea on my_recodband i add only onbeforrender MS> Did you lose the value of onbeforerender with MS> cut/paste? no MS> Please send the testcase. i test it at linux at home, i have not ps_file_viewer at work under windows and i have fpc 2.0 and i fear update MSE to last svn version =)
RSS Feed