Re: Rotating Pictures

I should mention that the pictures are JPEGs, if it matters. -- Cannon.Smith Synergy Farm Solutions Inc. Hill Spring, AB Canada 403-626-3236 > On Aug 8, 2017, at 5:01 PM, Cannon Smith via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > I was surprised that the

RE: Rotating Pictures

Hi Cannon, > Does anyone have any ideas about how to do this? I think you could use SVG_SET_TRANSFORM_ROTATE: http://livedoc.4d.com/4Dv15/help/Command/en/page65945.html The idea would be to create a new SVG canvas and embed the picture on it, then rotate the SVG, then export the SVG back to an

Re: JSON Tools Was: Re: C-objects and memory use

it seems this view just keeps coming up... I think it is important to understand that 4D didn't look at JSON and implement it as Object and Array Object, doing a really bad job at it, as it were, no, it happened the other way round... Object and Array Object were implemented first, and then

Rotating Pictures

I was surprised that the TRANSFORM PICTURE doesn’t have the ability to rotate a picture. I have the need to programmatically rotate a picture before displaying it on a form based on the EXIF rotation data. I’d like to do this natively, if possible, and it needs to work on both Mac and Windows.

Re: Relative path in SVG DOM

is your SVG image itself a file inside the Resources folder? > 2017/08/09 2:45、Two Way Communications via 4D_Tech <4d_tech@lists.4d.com> > のメール： > However, if I put this inside the xlink:href attribute of the image, it does > not show up in the SVG.

Re: JSON Tools Was: Re: C-objects and memory use

On Tue, Aug 8, 2017 at 5:14 PM, Keisuke Miyako via 4D_Tech < 4d_tech@lists.4d.com> wrote: > it seems this view just keeps coming up... > > I am sorry if the documentation or marketing material or presentation or > some other form of communication gave the wrong impression, but Object and >

Re: ​Re: UUID vs Longint primary key

David, how do you tell these two issues apart: Customer name : John Smith Customer Name : John Smyth is this a typo (one should be Smyth and is not, or one should be Smith and is not)? is it real (2 John Smiths with different spellings) I see this problem with a 'free form' entry inventory

Re: Preventing Duplicate Data WAS UUID vs Longint primary key

Jody, what are your normal duplicate reducing/removal technic(s)? On Mon, 7 Aug 2017 12:28:21 -0600, Jody Bevan via 4D_Tech wrote: > John: > > Thanks for sharing this. I had not thought of this way after all > these years. I will take the idea and apply where appropriate, in > addition to my

Re: ​Re: UUID vs Longint primary key

ok - I'm confused. what is the difference between a display only field showing an internal ID number, and a duplicate, display only ID number showing on the entry form? On Tue, 8 Aug 2017 08:07:00 -0600, npdennis wrote: >> I find that by placing the internal linking value (non-editable) on an

​Re: Preventing Duplicate Data REAL WORLD

I thought I would share this real world experience in regard to data, as it is somewhat humorous, but not for the people in the back seat. Long long ago, in another country, I was a police member patrolling the downtown streets of a city in economic boom circumstances. There were lots and lots

Re: ​Re: UUID vs Longint primary key

yes, BUT - I find that by placing the internal linking value (non-editable) on an entry form GREATLY enhances the ability/simplicity of tracking down data issues. ex (without viewable internal key): user: "... customer John Smith does not show the correct invoice(s) Dev/Sys admim: John Smith..

Re: ​Re: UUID vs Longint primary key

> I find that by placing the internal linking value (non-editable) on an > entry form > GREATLY enhances the ability/simplicity of tracking down data issues. This same thing can also be done by adding the same field to the same table but not linking off of it internally :) -- Neil Dennis 4D

Re: ​Re: UUID vs Longint primary key

> This all started with David making a broad blanket statement about "data > integrity" and "row duplication" and how using "synthetic" record ID keys > ruined the ability to automatically​ ​filter out "dupes". (I _think_ that > was your point David. Please correct me if not.) And in that strict

Relative path in SVG DOM

I am trying to use a relative path to a picture file that is stored locally, in the database folder. According to the documentation: A relative URL ("../picture.png"). This is particularly useful in client/server mode, when files are stored in the "Resources" folder. Relatives URLs can begin

Re: JSON Tools Was: Re: C-objects and memory use

It’s been a long time since I’ve used 4D and JSON but as I recall one problem was the inability to parse JSON where the top level is an array instead of an object. IOW, if your JSON looked like this: [ 1, 2, 3 ] 4D couldn’t parse it. A pretty big deviation from the standard. On the other

Re: JSON Tools Was: Re: C-objects and memory use

Rick, You have to use the JSON PARSE ARRAY command. http://doc.4d.com/4Dv15/4D/15.4/JSON-PARSE-ARRAY.301-3274446.en.html I wrote a wrapper for JSON strings to look at the first char and then use the appropriate method. This is one place where NTK is more convenient since it makes that

Re: Preventing Duplicate Data WAS UUID vs Longint primary key

Chip: I have always tried doing at the point of data entry. Obviously no code is perfect, and either is the object between the keyboard and the chair. My experience is that few Administrators would take the time to filter through duplicates. Getting them to do system maintenance was almost

Re: Re(4): 4D db -> SAAS

Unless I misunderstood the requirement, if it's a single user application and the Data is particular to each customer but not the schema/structure than why not use 4D Volume Desktop? Cheers Jim Labos - infobase - Jim Labos - infobase -- View this message in context:

​Re: UUID vs Longint primary key

On Tue, Aug 8, 2017 at 11:00 AM, ​ Chip Scheide <4d_o...@pghrepository.org> wrote: > > Worse, I've found that the same product, from the same vendor in > differing purchase amounts (1 vs case) is the same part number, but > different pricing! So.. even a check on part numbers is insufficient to >