Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #5589 > unrolled thread

Values in the window-editor are different from those in the resource

Started byStefan Überbacher <info@sanosoft.com>
First post2013-07-26 07:52 -0700
Last post2013-07-31 06:48 -0700
Articles 3 — 2 participants

Back to article view | Back to comp.lang.clipper.visual-objects


Contents

  Values in the window-editor are different from those in the resource Stefan Überbacher <info@sanosoft.com> - 2013-07-26 07:52 -0700
    Re: Values in the window-editor are different from those in the resource "Wolfgang Riedmann" <wriedmann@gmail.com> - 2013-07-31 08:40 +0200
      Re: Values in the window-editor are different from those in the resource Stefan Überbacher <info@sanosoft.com> - 2013-07-31 06:48 -0700

#5589 — Values in the window-editor are different from those in the resource

FromStefan Überbacher <info@sanosoft.com>
Date2013-07-26 07:52 -0700
SubjectValues in the window-editor are different from those in the resource
Message-ID<9272615a-062c-4dca-b313-f48a869a7792@googlegroups.com>
Hi,

the size- and position-values in the resource-file are different from those in the window-editor. Does anyone of you know the relationship between those values?




[toc] | [next] | [standalone]


#5595

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2013-07-31 08:40 +0200
Message-ID<b5rppvFf0dvU1@mid.individual.net>
In reply to#5589
Hi Stefan,

> the size- and position-values in the resource-file are different from
> those in the window-editor. Does anyone of you know the relationship
> between those values?

you shold look in the SDK. AFAIK this has something to do with the
Pixel Positions parameter in the WED. If you set these to yes, your
window will not scale with large fonts, but the control positions will
be more accurate.
If you set this to no, your window will scale, but positions are no so
accurate.

The difference lies in the generated code. The resource is the same for
both settings:

CONTROL	"Nummer Angebot", _ANGEBOTSUBEDIT1_SC_ANGNR, "Static",
WS_CHILD, 4, 5, 81, 11

but the init() method of the window differs. With Pixel Positions = yes
this code will be generated:

oDCSC_AngNr :=
FixedText{SELF,ResourceID{_ANGEBOTSUBEDIT1_SC_ANGNR,_GetInst()},Point{7,
387},Dimension{122, 18}}

and with Pixel Positions to auto the following:

oDCSC_AngNr :=
FixedText{SELF,ResourceID{_ANGEBOTSUBEDIT1_SC_ANGNR,_GetInst()}}


I have spent a few minutes in the SDK searching for the difference, but
since this is not my problem, I cannot spend more than a few minutes on
it.

Wolfgang


-- 

[toc] | [prev] | [next] | [standalone]


#5599

FromStefan Überbacher <info@sanosoft.com>
Date2013-07-31 06:48 -0700
Message-ID<2dd5bd48-e005-4db8-8b2b-b6ca07bb4621@googlegroups.com>
In reply to#5595
Hi Wolfgang,

thank you for the tip.

Stefan

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.clipper.visual-objects


csiph-web