Actually adding OBJECT GET COORDINATES can make it a relative coordinate
situation, an offset from the original position, easy!
Alan
On Thu, Mar 14, 2019 at 10:55 AM Alan Tilson wrote:
> This process works and is not as clunky as I'd imagined. Would be great if
> there was an offset option in
This process works and is not as clunky as I'd imagined. Would be great if
there was an offset option in the print object command but I can now print
what I want to print!
Thanks,
Alan
On Wed, Mar 13, 2019 at 2:51 PM Alan Tilson wrote:
> Miyako,
> It looks like you just step through all the
Miyako,
It looks like you just step through all the objects and offset and print
them, so I'm trying that...
Alan
On Wed, Mar 13, 2019 at 1:16 PM Alan Tilson wrote:
> Hello Miyako,
> Ok, I'm back to this project.
> Thanks for the info and I'm working with the Print Object command, trying
> to
> Le 7 mars 2019 à 15:48, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> a
> écrit :
>
> [...]
> it was useful, because the old label editor could only position objects in
> mac points (1/72 of an inch)
>
> but I see that the doc says C_LONGINT.
>
>
that has been my experience,
in particular when I wrote my own label editor.
https://github.com/miyako/4d-component-label-editor
it was useful, because the old label editor could only position objects in mac
points (1/72 of an inch)
but I see that the doc says C_LONGINT.
Can we use real values for positioning and width/height with the "Print object"
command?
> On Mar 6, 2019, at 7:41 PM, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> have you looked into the "Print object" command?
>
> you can print … at any position (decimal, not integer
have you looked into the "Print object" command?
you don't need to duplicate an object,
you can print the same object as many times as you like,
at any position (decimal, not integer positioning)
with 17R you can define an object (JSON) representation of a form from scratch,
or take an existing
7 matches
Mail list logo
