RE: PICTs

Thanks! one more question... how do I find the 'static PICTs' referenced in the 64 bit report? I have looked at, and know what is on all of my forms - I do not have any static PICTS that I can see/find. Thanks again Chip >> In v13, or v15 is there a way to tell is a picture in the library is

Re: PICTs

Yes you can usehm free from https://www.hmplugins.com/ Regards Chuck Chuck Miller Voice: (617) 739-0306 Informed Solutions, Inc. Fax: (617) 232-1064

RE: PICTs

> In v13, or v15 is there a way to tell is a picture in the library is in PICT, > or other format? The 4D Pack plugin command 'AP Is Picture Deprecated' returns 1 if the picture is in PICT format. See this tech tip written for v13: https://kb.4d.com/assetid=76775 -Tim

Re: PICTs

Not that I know of however since v16 there has been the GET PICTURE FORMATS command: https://doc.4d.com/4Dv17/4D/17.2/GET-PICTURE-FORMATS.301-4387029.en.html but that doesn't directly help you for v13 or v15. So, I thought about it some more and _maybe_ could use PICTURE CODEC LIST and CONVERT

PICTs

In v13, or v15 is there a way to tell is a picture in the library is in PICT, or other format? Thanks Chip --- Gas is for washing parts Alcohol is for drinkin' Nitromethane is for racing ** 4D Internet Users Group

Re: _ as first character in Method Name [was 64 bit...]

4D already uses some private property names, e.g. __LockerID __NEW __KEY https://doc.4d.com/4Dv17R5/4D/17-R5/dataClassfromCollection.305-4128671.en.html https://doc.4d.com/4Dv17R5/4D/17-R5/Shared-objects-and-shared-collections.300-4128430.en.html so beware. > 2019/08/20 2:12、Chip Scheide via

Re: _ as first character in Method Name [was 64 bit...]

On Mon, 19 Aug 2019 09:31:09 -0700, Tom Benedict wrote: > How about two underscores instead of a space? DUH of course that will work! Chip > > Tom > >> On Aug 19, 2019, at 08:38, Chip Scheide via 4D_Tech >> <4d_tech@lists.4d.com> wrote: >> >> related... >> >> I name project methods in

Re: _ as first character in Method Name [was 64 bit...]

On Mon, 19 Aug 2019 17:37:19 +0100, Narinder Chandi via 4D_Tech wrote: > > Personally, I've never used spaces (or all uppercase for that matter) > when naming any 4D object but spaces are allowable and actually > encouraged according to that above?! I only use a space in the specific instance

Re: _ as first character in Method Name [was 64 bit...]

>> and 4D then processes to list all method names, and forms (1) with a space >> in their names ...and actually, by chance I was reading the v17.2 docs at the weekend which explicitly states: "Tip: It is a good programming technique to adopt the same naming convention as the one used by 4D

Re: _ as first character in Method Name [was 64 bit...]

How about two underscores instead of a space? Tom > On Aug 19, 2019, at 08:38, Chip Scheide via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > related... > > I name project methods in 'modules', that is the first 3 - 7 characters > are the same. > i.e. animal_ > I also have a 'header method',

Re: _ as first character in Method Name [was 64 bit...]

from my 64 Bit compatibility report: "Naming Conventions If Object Notation is enabled, naming conventions of items must not conflict with the object notation format. Even if Object Notation is not enabled, an MSC verify will complain. " and 4D then processes to list all method names, and forms

Re: _ as first character in Method Name [was 64 bit...]

I agree. I haven't found anything indicating a leading underscore is not allowed. Miyako said it's discouraged to avoid unintended consequences. That's a lot different than not allowed. I'm using, and compiling, leading underscore methods in 17r6 without issues. On Mon, Aug 19, 2019 at 9:13 AM

Re: _ as first character in Method Name [was 64 bit...]

Why is 64 bit 4D not going to like it? Spaces are still allowed in method names. You could also use animal__Module_Info (2 underscores) to keep it at the top. John DeSoi, Ph.D. > On Aug 19, 2019, at 10:38 AM, Chip Scheide via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > This causes the

Re: _ as first character in Method Name [was 64 bit...]

related... I name project methods in 'modules', that is the first 3 - 7 characters are the same. i.e. animal_ I also have a 'header method', which is all comments and has a summary of the function of the module. I currently name these 'module headers' with the module name + space +

Re: _ as first character in Method Name [was 64 bit...]

We have used digits for years, e.g. 00MyMethod, 000MyMethod2, etc. I haven't checked yet if digit prefixes for methods are still valid in v17 though! Regards, Narinder Chandi, ToolBox Systems Ltd. -- -Original Message- From: 4D_Tech <4d_tech-boun...@lists.4d.com> on behalf of 4D

Re: _ as first character in Method Name [was 64 bit...]

Hi Chip, Yes, we've been doing that for years also ... and sometimes a dot, which also is not allowed any more. We've changed them all to "aa..." Pat On Mon, 19 Aug 2019 at 16:24, Chip Scheide via 4D_Tech <4d_tech@lists.4d.com> wrote: > I use an underscore to start the name of methods which I

_ as first character in Method Name [was 64 bit...]

I use an underscore to start the name of methods which I want to 'float' to the top of the method list. I.E. _Conventions What allowed character(s) can I use instead? Thanks Chip On Sat, 17 Aug 2019 06:03:27 +, Keisuke Miyako via 4D_Tech wrote: > underscore prefixes are reserved for

Re: 64 bit readiness report - some questions

for those who are using v17, can someone test something for me, please, you need to be running on Mac, as Windows will not allow this. Filename: My_most_recent_File. What do you get for the extension property of the object returned from: Path to Object Thanks Chip On Sat, 17 Aug 2019

Re: 64 bit readiness report - some questions

in pre-17 versions (or when ever Is MacOS starts to exist) you can also use the konstant: Folder separator if all you need is to determine the current platform. ex: IF (Folder separator = ":") Do mac related stuff else Do Windows related stuff end if On Sat, 17 Aug 2019 05:57:41 +,