Re: [v16.3 64 IC on El Capitan] Receive file

[Jörg Knebel via 4D_Tech]

> On 5 Sep 2018, at 10:40 AEST, Keisuke Miyako via 4D_Tech 
> <4d_tech@lists.4d.com> wrote:
> 
> of course. that is not a good enough excuse,
> but I wanted to mention it as a weak explanation.

Thanks Keisuke.

That means I’ll use your cURL only.

**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: table/field token

[Keisuke Miyako via 4D_Tech]

it could be that the token syntax for tables and fields has been missed by 
engineering when the interpreter was rewritten for object notation.

in fairness, though, I don't think it was ever documented that the table or 
field name could be omitted in token syntax.
I know it worked, and sometimes it is better to not have any labels than have a 
misleading one,

e.g. [contacts:2] but maybe [contacts] is NOT table #2

but unlike :k, :C or :P

http://doc.4d.com/4Dv16/4D/16.3/Using-tokens-in-formulas.300-3651182.en.html

I think tables and field tokens can be confusing without labels because of the 
ambiguity of the [] brackets.

2018/09/06 3:20、Arnaud de Montard via 4D_Tech 
<4d_tech@lists.4d.com>のメール:
Surely something to do with dot notation, but I wonder if it's a bug or 
something I miss?



**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: [v16.3 64 IC on El Capitan] Receive file

[Keisuke Miyako via 4D_Tech]

I don't mean that it is obsolete or deprecated.

I mean that the basic design and feature set is pretty much the same as v6.8 
(1999)
because the focus has been placed on keeping it alive, not to give it a new 
life.

true, there have been efforts over the years to support Unicode, UDP, TLS email 
and 64-bits,
but the main driver for such updates was to prevent it from becoming a 
liability to 4D, not to make it better.

as a consequence, the plugin is a strange compromise of outdated design and a 
series of patches that sometimes contradict each other.

it is the classic new wine old skin bottle situation.

2018/09/06 5:14、Richard Wright via 4D_Tech 
<4d_tech@lists.4d.com>のメール:
Can you clarify "in fairness, it is legacy software, free to use and not part 
of the main product line.”
There is a 64 bit version 4D Internet Commands which tells me it’s being 
updated and I see nothing to indicate that it is considered legacy.


**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

RE: table/field token

[Timothy Penner via 4D_Tech]

Hi Richard,

> > * Starting with 4D v16 R4, "." and "[]" characters are no longer allowed in 
> > names of tokenized objects.
> I take that to mean they are no loner allowed in “new” names of tokenized 
> objects.

I take it to mean they are no longer allowed in tokenized objects, **existing 
or new**.  To be pedantic, I am interpreting the 'no longer' part of the 
sentence to apply to *existing* tokenized objects and then the overall sentence 
I am interpreting would also apply to *new* tokenized objects as well. I don't 
think it would make sense for this to apply to one and not the other.

I am not sure what would have been found by the MSC in your specific situation, 
but I am very curious...

Quote:
{
A specific MSC feature helps you detect names which are incompatible with 
object notation. Using this feature is highly recommended before enabling the 
option (see the Verify page section of the "MSC" chapter). As usual, it is 
recommended to work on a copy of the structure file.
}

Did you try running it through the MSC prior to enabling the feature?

-Tim



**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

RE: v13 - screen redraw

[Chip Scheide via 4D_Tech]

Thanks Stephen, 

I got it!

On Wed, 5 Sep 2018 14:43:13 -0500, Stephen J. Orth via 4D_Tech wrote:
> Chip,
> 
> Another option is to use CALL PROCESS (-1) and see if that works...
> 
> 
> Steve
> 
> -Original Message-
> From: 4D_Tech [mailto:4d_tech-boun...@lists.4d.com] On Behalf Of Chip 
> Scheide via 4D_Tech
> Sent: Wednesday, September 05, 2018 2:37 PM
> To: 4D iNug Technical <4d_tech@lists.4d.com>
> Cc: Chip Scheide <4d_o...@pghrepository.org>
> Subject: v13 - screen redraw
> 
> I have a small form I am trying to get working
> - it has a fixed text object on it.
> - the object is set 'indivisible by default'
> - The on load event sets up an outside call back to the process in 
> which the form is opened.
> - Outside call event sets the title of the object, and sets the text 
> object visible.
> 
> I can not get the screen to redraw and display the newly assigned text, 
> without opening another window over it; like an alert.
> 
> 
> I have tried:
> 1 hiding and showing the process the form is in
> using REDRAW WINDOW.
> 
> I changed from  fixed txt to a variable and assigned a value
> this too fails to redraw properly
> 
> can someone see what I am missing?
>   
>   
> Thanks 
> Chip
> ---
> Gas is for washing parts
> Alcohol is for drinkin'
> Nitromethane is for racing 
> 
> 
> **
> 4D Internet Users Group (4D iNUG)
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> **
> 
> **
> 4D Internet Users Group (4D iNUG)
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> **
---
Gas is for washing parts
Alcohol is for drinkin'
Nitromethane is for racing 
**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: table/field token

[Richard Wright via 4D_Tech]

> * Starting with 4D v16 R4, "." and "[]" characters are no longer allowed in 
> names of tokenized objects.

I take that to mean they are no loner allowed in “new” names of tokenized 
objects.


> Date: Wed, 5 Sep 2018 18:50:28 +
> From: Timothy Penner 
> 
>> Surely something to do with dot notation, but I wonder if it's a bug or 
>> something I miss?
> 
> There is a section of the docs that talks about this:
> http://doc.4d.com/4Dv16R4/4D/16-R4/Using-object-notation-preview.300-3303773.en.html#3304590
> 
> {
> Activating the object notation
> Over any versions, 4D has always accepted dots (.) and square brackets ([ and 
> ]) in tokenized database object names (tables, fields, variables, and 
> methods).
> 
> However, these characters are used to identify language tokens in standard 
> object notation. Thus, databases using names containing dots or square 
> brackets are not compatible with the standard object notation since 
> misinterpretations could break existing code. For example, if the following 
> code is written:
> 
> a.b
> a.b:=c[1]
> 
> ...4D could not know if a.b and c[1] represent standard variable names or if 
> b is a property of the a object and c the second element of a c collection.
> 
> Consequently:
> 
> * In converted databases, you have to select a specific option stating that 
> you want to use the object notation. By selecting this option, you declare 
> that your code is "object notation ready", that is, it does not use any names 
> containing "." or "[]" characters.
> * A specific MSC feature helps you detect names which are incompatible with 
> object notation. Using this feature is highly recommended before enabling the 
> option (see the Verify page section of the "MSC" chapter). As usual, it is 
> recommended to work on a copy of the structure file.
> * Enabling the object notation is a no-return option since it requires a 
> retokenization of the code. Once enabled, it cannot be removed and the 
> database cannot be reopened with a previous version.
> * Starting with 4D v16 R4, "." and "[]" characters are no longer allowed in 
> names of tokenized objects.
> }

**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: [v16.3 64 IC on El Capitan] Receive file

[Richard Wright via 4D_Tech]

Can you clarify "in fairness, it is legacy software, free to use and not part 
of the main product line.”

There is a 64 bit version 4D Internet Commands which tells me it’s being 
updated and I see nothing to indicate that it is considered legacy. 


Richard Wright
DataDomain
rwri...@datadomainsoftware.com



> Date: Wed, 5 Sep 2018 00:40:30 +
> From: Keisuke Miyako 
> 
> 
> I think you are referring to ACI0096897 which is described as standard 
> behaviour, that is,
> expected result according to design.
> 
> FTP_GetDirList uses the 'LIST' request.
> When optionnal output parameter if provided to get timestamps, it sends an 
> 'MTDM' request for each file of the directory.
> (and not the 'MLSD' request of RFC 3659)
> 
> the result is that FTP_receive returns error 10048 on certain servers, since 
> 15.4 (was ok until 15.3)
> the workaround is to
> a: not provide last optional array for timestamps in FTP_GetDirList,
> or
> b: call  FTP_Login again after FTP_GetDirList
> 
> the fact that the bug is considered standard behaviour,
> speaks for itself about the level of enthusiasm to maintain the product.
> 
> in fairness, it is legacy software, free to use and not part of the main 
> product line.
> 
> of course. that is not a good enough excuse,
> but I wanted to mention it as a weak explanation.



**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

list box entry issue

[Chuck Miller via 4D_Tech]

Hi All,

Environment 4D v15.6 client server


I have an array based list box where there are 3 arrays. Only array 3 can be 
entered

Under the list box object I have the following code

Case of 
: (Form event=On Load)
  //EDIT ITEM(DefaultValue_ar;1)
: (Form event=On Double Clicked)
C_LONGINT($ColumnNumber_l;$row_l)
LISTBOX GET CELL POSITION(*;"SelectListBox";$ColumnNumber_l;$row_l)
If ($row_l>0) & ($row_l<=Size of array(DefaultValue_ar))
EDIT ITEM(DefaultValue_ar;$row_l)
End if 
End case 


Under the thirst column, I have the following code

C_LONGINT($Column_l;$Row_l)
LISTBOX GET CELL POSITION(SelectListBox;$Column_l;$Row_l)
MM_ValidateAmount is a method that checks to see if amounts are in the 
appropriate range
Case of 


: (Form event=On Data Change)// I have tried on losing focus as well

If (DefaultValue_ar{$Row_l}>0)
If (MM_ValidateAmount 
(vd_metalDate;->DefaultValue_ar{$Row_l};Metal_atxt{$Row_l};MarketName_atxt{$Row_l}))
If ($Row_lmailto:cjmillerinformed-solutions.com 
 Brookline, MA 02446 USA Registered 4D Developer
   Providers of 4D and Sybase connectivity
  http://www.informed-solutions.com  

This message and any attached documents contain information which may be 
confidential, subject to privilege or exempt from disclosure under applicable 
law.  These materials are intended only for the use of the intended recipient. 
If you are not the intended recipient of this transmission, you are hereby 
notified that any distribution, disclosure, printing, copying, storage, 
modification or the taking of any action in reliance upon this transmission is 
strictly prohibited.  Delivery of this message to any person other than the 
intended recipient shall not compromise or waive such confidentiality, 
privilege or exemption from disclosure as to this communication. 

**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

RE: v13 - screen redraw

[Stephen J. Orth via 4D_Tech]

Chip,

Another option is to use CALL PROCESS (-1) and see if that works...


Steve

-Original Message-
From: 4D_Tech [mailto:4d_tech-boun...@lists.4d.com] On Behalf Of Chip Scheide 
via 4D_Tech
Sent: Wednesday, September 05, 2018 2:37 PM
To: 4D iNug Technical <4d_tech@lists.4d.com>
Cc: Chip Scheide <4d_o...@pghrepository.org>
Subject: v13 - screen redraw

I have a small form I am trying to get working
- it has a fixed text object on it.
- the object is set 'indivisible by default'
- The on load event sets up an outside call back to the process in 
which the form is opened.
- Outside call event sets the title of the object, and sets the text 
object visible.

I can not get the screen to redraw and display the newly assigned text, 
without opening another window over it; like an alert.


I have tried:
1 hiding and showing the process the form is in
using REDRAW WINDOW.

I changed from  fixed txt to a variable and assigned a value
this too fails to redraw properly

can someone see what I am missing?


Thanks 
Chip
---
Gas is for washing parts
Alcohol is for drinkin'
Nitromethane is for racing 


**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

RE: v13 - screen redraw

[Stephen J. Orth via 4D_Tech]

Chip,

Have you tried procedurally changing the size of the window (i.e. 1 pixel 
wider, then smaller)?


Steve

-Original Message-
From: 4D_Tech [mailto:4d_tech-boun...@lists.4d.com] On Behalf Of Chip Scheide 
via 4D_Tech
Sent: Wednesday, September 05, 2018 2:37 PM
To: 4D iNug Technical <4d_tech@lists.4d.com>
Cc: Chip Scheide <4d_o...@pghrepository.org>
Subject: v13 - screen redraw

I have a small form I am trying to get working
- it has a fixed text object on it.
- the object is set 'indivisible by default'
- The on load event sets up an outside call back to the process in 
which the form is opened.
- Outside call event sets the title of the object, and sets the text 
object visible.

I can not get the screen to redraw and display the newly assigned text, 
without opening another window over it; like an alert.


I have tried:
1 hiding and showing the process the form is in
using REDRAW WINDOW.

I changed from  fixed txt to a variable and assigned a value
this too fails to redraw properly

can someone see what I am missing?


Thanks 
Chip
---
Gas is for washing parts
Alcohol is for drinkin'
Nitromethane is for racing 


**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

RE: table/field token

[Timothy Penner via 4D_Tech]

> Surely something to do with dot notation, but I wonder if it's a bug or 
> something I miss?

There is a section of the docs that talks about this:
http://doc.4d.com/4Dv16R4/4D/16-R4/Using-object-notation-preview.300-3303773.en.html#3304590

{
Activating the object notation
Over any versions, 4D has always accepted dots (.) and square brackets ([ and 
]) in tokenized database object names (tables, fields, variables, and methods).

However, these characters are used to identify language tokens in standard 
object notation. Thus, databases using names containing dots or square brackets 
are not compatible with the standard object notation since misinterpretations 
could break existing code. For example, if the following code is written:

a.b
a.b:=c[1]

...4D could not know if a.b and c[1] represent standard variable names or if b 
is a property of the a object and c the second element of a c collection.

Consequently:

* In converted databases, you have to select a specific option stating that you 
want to use the object notation. By selecting this option, you declare that 
your code is "object notation ready", that is, it does not use any names 
containing "." or "[]" characters.
* A specific MSC feature helps you detect names which are incompatible with 
object notation. Using this feature is highly recommended before enabling the 
option (see the Verify page section of the "MSC" chapter). As usual, it is 
recommended to work on a copy of the structure file.
* Enabling the object notation is a no-return option since it requires a 
retokenization of the code. Once enabled, it cannot be removed and the database 
cannot be reopened with a previous version.
* Starting with 4D v16 R4, "." and "[]" characters are no longer allowed in 
names of tokenized objects.
}

Hope that helps,

-Tim



**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

table/field token

[Arnaud de Montard via 4D_Tech]

Migrating from v14r5 to v16r6, dot notation on. 

In fomulas referencing fields, I have things like this:
  TimeStampToText([:2]:3)

In v16r6, such token is no longer recognised ; I've found 2 turnarounds :
1/ add the table/field names before the token:
  TimeStampToText ([aTable:2]aField:3)
2/ use wildcard:
  TimeStampToText ([@:2]@:3)

Surely something to do with dot notation, but I wonder if it's a bug or 
something I miss? 

-- 
Arnaud de Montard 



**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**