Re: Bug or feature?

Miyako, On Thu, Feb 1, 2018 at 12:33 PM, Keisuke Miyako via 4D_Tech <4d _t...@lists.4d.com> wrote: > I don't think that actually proves that JSON Parse is throwing the > runtime error. > ​Agreed. But that is where it shows up so it's the place to start.​ rather than looking at the "line of

RE: Bug or feature?

I just today got the -20002 error in a compiled database. The issue is/was pointers. I was doing something "fancy", basically the pointer was not pointing to what I thought it was, it was actually pointing to a nonexistent variable - via Get Pointer. All of this code worked perfectly

RE: Bug or feature?

Arnaud, Thank you, this led me to reinspect my code and I found a couple issues with the original code. The issue I was seeing was actually multiple issues compounded together that led me to think it didn’t work. You are correct, using the current Method Name for an error handler does seem to

Re: Bug or feature?

> Le 2 févr. 2018 à 00:30, Timothy Penner a écrit : > > Arnaud, > >> Most of the time I do this at beginning: >> $cmn_t:=Current method name >> then I use $cmn_t. >> I don't remember of problems in compiled. > > But do you use the current method to handle errors? > Either: ON

Re: what version(s) work with which version(s)

> Le 1 févr. 2018 à 22:34, Chip Scheide via 4D_Tech <4d_tech@lists.4d.com> a > écrit : > > Given a component, compiled in v13, besides v13, which version(s) will > component work with? > Repeat for v14, v15 > > The component contains nothing but 4D code. I use a the same v12 component with

Re: what version(s) work with which version(s)

Thanks! On Thu, 1 Feb 2018 23:20:28 +, Keisuke Miyako via 4D_Tech wrote: > in principle (that is, if we just focus on the version number) > then a v13 compiled component will work in v14 all the way up to v16. > > but there are other factors to consider. > > if you intend to also compile

Re: Where is the client's preferences file

> Le 1 févr. 2018 à 22:23, Timothy Penner via 4D_Tech <4d_tech@lists.4d.com> a > écrit : > > Rather than guessing or trying to remember, I find it so much easier to just > use this set of commands: > > SHOW ON DISK(Get 4D folder(4D Client database folder);*) ... not in debugger ;-) --

Re: Bug or feature?

> Le 1 févr. 2018 à 22:14, Timothy Penner via 4D_Tech <4d_tech@lists.4d.com> a > écrit : > >> besides, you shouldn't have to look at the string in the first place if you >> use JSON Parse with error handling. > > So it seems that the problem here is that you cannot use the current method >

Re: what version(s) work with which version(s)

in principle (that is, if we just focus on the version number) then a v13 compiled component will work in v14 all the way up to v16. but there are other factors to consider. if you intend to also compile your host application, you need to be aware that non-unicode mode is not available in 64-bit

Re: "Goodbye 4D Write" email

On Feb 1, 2018, at 4:17 PM, Chip Scheide wrote: > In principle, it should be possible to create a text editor in 4D > itself. > > I believe that the 4D design interface is built in/with 4D. If this is > true, you should be able to build a tailorable text editor inside 4D. > The Method editor

what version(s) work with which version(s)

Given a component, compiled in v13, besides v13, which version(s) will component work with? Repeat for v14, v15 The component contains nothing but 4D code. Thanks --- Gas is for washing parts Alcohol is for drinkin' Nitromethane is for racing

RE: Where is the client's preferences file

Rather than guessing or trying to remember, I find it so much easier to just use this set of commands: SHOW ON DISK(Get 4D folder(4D Client database folder);*) This is actually much better because the actual path depends on the name of the database and the ip address (or dns name) of the

Where is the client's preferences file

My brain is not working this morning. Can’t remember where the preferences for a v16 client server client is located. Need to tell someone to throw it out to resolve their inability to log in to server because of inability to save the preference file. Thanks, John John Baughman Kailua,

RE: Bug or feature?

> besides, you shouldn't have to look at the string in the first place if you > use JSON Parse with error handling. Hmmm, this does seem to work in compiled mode: C_OBJECT($ob) C_TEXT($text) ON ERR CALL("handler") $text:="{\"OK\": True}" // The JSON is invalid because True should be written as

Re: Intermittent 4D Server / System crashes

> > I have been having intermittent system crashes. These happen every 2-5 > days.. Never when the system is in use. (8-21:00) Usually early in the > morning long after Retrospect has run. Retrospect Client takes about 15-30 > to back up to our main Server. > We had a similar issue but with

Re: ImageCaptureCore - to Variable?

the callback signature, as explained the sample DB, is $1 C_LONGINT: param_scan_type $2 C_TEXT: param_scan_path $3 C_BLOB: param_scan_data $4 C_TEXT: param_scan_context_info $4 contains parameters such as dataSize dataNumRows dataStartRow bytesPerRow numComponents bitsPerComponent

Re: Bug or feature?

I don't think that actually proves that JSON Parse is throwing the runtime error. rather than looking at the "line of code referenced in the error dialog" perhaps you could activate debug log recording in verbose mode (2) at the start of the offending method (and disable it a the end)

Re: "Goodbye 4D Write" email

In principle, it should be possible to create a text editor in 4D itself. I believe that the 4D design interface is built in/with 4D. If this is true, you should be able to build a tailorable text editor inside 4D. The Method editor while not perfect, is a usable text editor. IF that is true

Re: "Goodbye 4D Write" email

On Thu, Feb 1, 2018 at 3:53 PM, Herr Alexander Heintz via 4D_Tech < 4d_tech@lists.4d.com> wrote: > Come on you plugin developers, give us a real Word processing Plugin and > there will be a market for it. > Sadly this kind of development is out of my league, or i’d do it. > > > > Definitely, do

Re: "Goodbye 4D Write" email

Omnis is still around and very alive. Alan Chan 4D iNug Technical <4d_tech@lists.4d.com> writes: >How many of you >used to work using Foxbase, dBase, Omnis, to name a few. Just be greatful >that the company has been able to keep up with the times and is still a >viable product.

Re: Bug or feature?

There are no work-arounds for runtime errors. 4D throws up an error dialog and allows the end user to decide what to do, even if executing on 4D Server or in a web process. See feature request and discussion here: http://forums.4d.com/Post/EN/17994245/1/19128922 John DeSoi, Ph.D. > On Feb

Re: "Goodbye 4D Write" email

The more things change the more they stay the same. 4D like any company makes decision on how to spend money. There are probably not enough users of 4D write to warrant the cost associated with porting to 64 bit. While this hurts at one of my customers, think of it this way. How many of you used

Re: Bug or feature?

Hi Miyako, On Wed, Jan 31, 2018 at 9:55 PM, Keisuke Miyako via 4D_Tech < 4d_tech@lists.4d.com> wrote: > JSON Parse error can be handled with ON ERR CALL, because it is not a > runtime error. > > "Current method name" requires range checking (see docs), but that is > unrelated. > > you just have

Re: Intermittent 4D Server / System crashes

Thanks for the suggestions: 1) Upgrading to 16.3 HF1. I will do this but none of the reported bug fixes seems to address the problem. 2) This is a 32 bit application 2) Memory setting. Since this is 32 bit on OSX my understanding is that the memory allocation is fixed by the OS at around 2 GB.

Re: ImageCaptureCore - to Variable?

maybe another time, if I find where it starts. > On Jan 31, 2018, at 6:46 PM, Keisuke Miyako via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > but you receive binary RGB data in chunks, > and you have to build your own JPG, PNG, TIFF, whatever, by code. > > do you really want to go down that

Re: Styled text to clipboard - v16

Miyako, you are (as ever) a mine of valuable information. Thanks. Jeremy Jeremy Roussak j...@mac.com > On 1 Feb 2018, at 09:29, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > that would be INVOKE ACTION > >

Re: "Goodbye 4D Write" email

I have been using 4D Write Pro for quite some time now as an editor for E-Mails. Porting the functionality I had before using 4d Write (mostly dynamic access to data) was quite simple. Nevertheless, there is quite a lot missing for it to replace 4D Write for those who need a „real“ text editor.

Re: "Goodbye 4D Write" email

If 4D Write Pro doesn’t, and won’t, have all the features of 4D Write then 4D should give it a different name instead of pretending that it’s a replacement. I’ve been totally baffled by this seemingly endless piecemeal rollout of a “pro” product. I remember getting an email a couple years ago

Re: Styled text to clipboard - v16

that would be INVOKE ACTION http://doc.4d.com/4Dv16R4/4D/16-R4/INVOKE-ACTION.301-3316995.en.html see also: https://blog.4d.com/discover-and-use-standard-actions/ https://blog.4d.com/more-standard-actions-for-styled-text/ https://blog.4d.com/create-your-own-interface-for-4d-write-pro/

Re: Styled text to clipboard - v16

Pat, Thanks, but I tried that. I ended up pasting plain text with style tags in it. I’m obviously doing something wrong. Jeremy Jeremy Roussak j...@mac.com > On 1 Feb 2018, at 07:35, Pat Bensky via 4D_Tech <4d_tech@lists.4d.com> wrote: > > Jeremy, > Maybe *ST Get Text* does what you need?

Re: Styled text to clipboard - v16

Jeremy, Maybe *ST Get Text* does what you need? Pat On 1 February 2018 at 10:32, Jeremy Roussak via 4D_Tech < 4d_tech@lists.4d.com> wrote: > I want to put styled text (nothing complex: just some in italic and some > in bold) onto the clipboard so that I can paste it into Word or Mail or > some

Styled text to clipboard - v16

I want to put styled text (nothing complex: just some in italic and some in bold) onto the clipboard so that I can paste it into Word or Mail or some such. I used to do it by using Write: make an offscreen area, put the text in it, style it and then do WR EXECUTE COMMAND ($area;wr cmd copy)

Re: Re(2): "Goodbye 4D Write" email

> Le 1 févr. 2018 à 02:28, Don Lapin via 4D_Tech <4d_tech@lists.4d.com> a écrit > : > > Hi Brian, > > You did not answer the question regarding whether 4D will continue to work > with 4D Write (the regular version, not the Pro). That's my primary concern > at the moment. Hi Don, I heard

Re(2): "Goodbye 4D Write" email

Hi Alfonso, I agree with most of what you state here. My customers for this application are on Windows, so I'm not as concerned about the 64-bit thing. Apple's always dropping "last year's" technology, but Windows maintains good compatibility, even with their 64-bit systems. Because the Write

Re: "Goodbye 4D Write" email

Don Lapin: > You did not answer the question regarding whether 4D will continue to work > with 4D Write (the regular version, not the Pro). That's my primary concern > at the moment. From my understanding the "old" 4D Write will continue working in 32Bit versions of 4D. There will be no 64Bit

Re: "Goodbye 4D Write" email

Hi Don, I agree with you that 4D Write PRO can't replace today 4D Write. But, forget trying that 4D mantain 4D Write. Because MacOs High Sierra is the last Mac Os working compatible 32 bits. So, all applications must be 64 bits, in the future. 4D Write PRO borned 64 bits for that reason. We