Re: Subform 64-bit problem

2018-05-12 Thread Jim Crate via 4D_Tech 
On May 12, 2018, at 5:18 PM, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> 
wrote:

> was it ever documented that "SET ENTERABLE(False)" should also render the 
> object invisible?
> 
> 64-bit version of 4D on Mac is Cocoa, as opposed to 32-bit which is Carbon.
> The UI was recreated from the ground up, based on what the specification 
> (=documentation) dictates.
> Any undocumented or serendipitous, consequential behaviour would have been 
> eliminated in the process.
> (reason why one should not take too much advantage of undocumented behaviour)


This isn’t about undocumented behavior. In 32-bit mode SET ENTERABLE and OBJECT 
SET ENTERABLE only set the enterable flag, not the visibility flag. 

In 64-bit, OBJECT SET ENTERABLE and OBJECT SET VISIBLE work as expected for 
objects on a form. The problem is the behavior specific to 64-bit mode in a 
list subform when setting object enterability during On Display Detail. In 
these specific conditions, OBJECT SET ENTERABLE(field;false) makes some objects 
invisible and enterable.

> Also, 4D no longer draws pixels to create a bitmap of a list form, but rather,
> requests Cocoa to update sub views of the window view hierarchy,
> and lets the framework do its own optimisation to create the final result.

I guess this is why OBJECT SET ENTERABLE now behaves erratically in a list 
subform.  This is the only place in this structure where this functionality was 
used, so I guess it will be out with the subform and in with a listbox.

Jim Crate


> 
>> 2018/05/12 15:11、Jim Crate via 4D_Tech <4d_tech@lists.4d.com> のメール：
>> 
>> I have a form with a list-only subform, with enterable in list checked, and 
>> no detail subform. Based on values in the records displayed in this subform, 
>> certain fields are set to be enterable or not by calling OBJECT SET 
>> ENTERABLE during On Display Detail. This works fine in 32-bit mode.
>> 
>> In 64-bit mode, fields set with OBJECT SET ENTERABLE(field;false), they 
>> become invisible, but if you click on them, the line switches to editing 
>> mode, the text becomes visible and the field is actually enterable.  Fields 
>> set with OBJECT SET ENTERABLE(field;true) display normally.
>> 
>> This happens with 4D 16.3 HF2 and HF3 on macOS. Has anyone run into this 
>> before and found a workaround other than using a listbox instead? I’ve tried 
>> using OBJECT SET ENTERABLE during On Display Detail both in a subform field 
>> object method and the subform’s form method.
> 
> 
> 
> 
> **
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> 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)
FAQ:  http://lists.4d.com/faqnug.html
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: Subform 64-bit problem

2018-05-12 Thread Keisuke Miyako via 4D_Tech 
was it ever documented that "SET ENTERABLE(False)" should also render the 
object invisible?

64-bit version of 4D on Mac is Cocoa, as opposed to 32-bit which is Carbon.
The UI was recreated from the ground up, based on what the specification 
(=documentation) dictates.
Any undocumented or serendipitous, consequential behaviour would have been 
eliminated in the process.
(reason why one should not take too much advantage of undocumented behaviour)

Also, 4D no longer draws pixels to create a bitmap of a list form, but rather,
requests Cocoa to update sub views of the window view hierarchy,
and lets the framework do its own optimisation to create the final result.

> 2018/05/12 15:11、Jim Crate via 4D_Tech <4d_tech@lists.4d.com> のメール：
>
> I have a form with a list-only subform, with enterable in list checked, and 
> no detail subform. Based on values in the records displayed in this subform, 
> certain fields are set to be enterable or not by calling OBJECT SET ENTERABLE 
> during On Display Detail. This works fine in 32-bit mode.
>
> In 64-bit mode, fields set with OBJECT SET ENTERABLE(field;false), they 
> become invisible, but if you click on them, the line switches to editing 
> mode, the text becomes visible and the field is actually enterable.  Fields 
> set with OBJECT SET ENTERABLE(field;true) display normally.
>
> This happens with 4D 16.3 HF2 and HF3 on macOS. Has anyone run into this 
> before and found a workaround other than using a listbox instead? I’ve tried 
> using OBJECT SET ENTERABLE during On Display Detail both in a subform field 
> object method and the subform’s form method.




**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
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: Web Service Call in 4Dv15

2018-05-12 Thread Ronnie Teo via 4D_Tech 
Hi Tim,

Thanks for your heads up. 

FWIW, I have also tested the Web Service Call command at any another site (call 
this SiteB) using the same version 4Dv15.5 running on Windows 2012r2.

The test at Site B was successful and the only difference appears to be that 
the soapURL for Site B is a non-secured HTTP connection.
For the site that I am having issues with, the soapURL is a secured HTTPS 
connection.

In your opinion, would that have any effect on the success/failure of the Web 
Service Call command?

> Is it possible that the SOAP Server you are connecting to is older, and does 
> not understand current TLS versions above TLS 1.0?
> v11 supported SSLv2/SSLv3 while v15 does not.

How may I verify if the SOAP server we are connecting to support TLS versions 
above TLS 1.0?

Regards,
Ronnie
Tarawerkz




> On 12 May 2018, at 1:32 am, Timothy Penner  wrote:
> 
> Is it possible that the SOAP Server you are connecting to is older, and does 
> not understand current TLS versions above TLS 1.0?
> 
> v11 supported SSLv2/SSLv3 while v15 does not.
> 
> Reminders,
> SSLv3 and SSLv2 is disabled at the network layer in 4D as of v13 & v14
> http://forums.4d.com/Post/EN/15389376/1/15389377#15389377
> http://forums.4d.com/Post/FR/15389373/1/15389374#15389374
> 
> I think that TLS 1.0 is disabled at the network layer in 4D as of v15 leaving 
> only TLS 1.1 and 1.2 as an option in v15, but I am have not found a public 
> reference for this yet.
> 
> TLS 1.2 is set as the minimum TLS version at the network layer in 4D as of 
> v16R5
> https://blog.4d.com/more-security-for-your-4d-server/
> http://kb.4d.com/assetid=77901
> 
> -Tim
> 
> 
> Timothy Penner
> Senior Technical Services Engineer
> 
> 4D Inc
> 95 S. Market Street, Suite #240
> CA 95113 San Jose
> United States

**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
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: Paste (ctrl-v) in textfield doesn't work with focusable listbox

2018-05-12 Thread Piotr Chabot Stadhouders via 4D_Tech 
Hi,

Ok, thanks, i Will try to reproduce the problem in a sample database

"
I created a simple form with an array based listbox and a text field and it 
seems like I have no trouble pasting into the text field, but perhaps I am 
doing something different than you are doing.



Also, I don't see any bugs related to your described behavior, but if you can 
reproduce the issue I would suggest you create a simple sample database, raise 
a Tech Support (TAOW) case, and attach it to the case along with the steps to 
reproduce the issue. That way our tech support team can take a look."

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

Subform 64-bit problem

2018-05-12 Thread Jim Crate via 4D_Tech 
I have a form with a list-only subform, with enterable in list checked, and no 
detail subform. Based on values in the records displayed in this subform, 
certain fields are set to be enterable or not by calling OBJECT SET ENTERABLE 
during On Display Detail. This works fine in 32-bit mode. 

In 64-bit mode, fields set with OBJECT SET ENTERABLE(field;false), they become 
invisible, but if you click on them, the line switches to editing mode, the 
text becomes visible and the field is actually enterable.  Fields set with 
OBJECT SET ENTERABLE(field;true) display normally. 

This happens with 4D 16.3 HF2 and HF3 on macOS. Has anyone run into this before 
and found a workaround other than using a listbox instead? I’ve tried using 
OBJECT SET ENTERABLE during On Display Detail both in a subform field object 
method and the subform’s form method.

Jim Crate

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