Re: v16 Time picker - bound variable changed

Keisuke Miyako: As usual, fantastic clear response. That explains it very well. Thanks Jody > On Jun 18, 2018, at 12:19 AM, Keisuke Miyako via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > Hello, > >> how to tell when a non-R version will have the features of an R-version. > > short answer i

Re: v16 Time picker - bound variable changed

n > x obviously... > n > R ** 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-un

Re: v16 Time picker - bound variable changed

Hello, > how to tell when a non-R version will have the features of an R-version. short answer is, when the version number changes and the "R" goes way. 16Rn and 16.x are different numbering systems, so it doesn't matter if n > R. 16.3 has the exact same features as 16.0 - nothing will be added

Re: v16 Time picker - bound variable changed

Thank you Miyako. That was it. David Samson > it is a bug that was fixed in 16.3 Hotfix 1 (latest is Hotfix 4) > > ACI0097700 > > 2018/06/12 0:40、David Samson via 4D_Tech <4d_tech@lists.4d.com 4d_tech@lists.4d.com>> のメール： > Should I be defaulting the time on the on-load of the holding form now?

Re: v16 Time picker - bound variable changed

Thanks Keisuke. That explains it. I still have not wrapped my head around how to tell when a non-R version will have the features of an R-version. I have read the BLOG on it, and it does not go into that detail. How can we know what are ‘feature’ equivalent? I spent time yesterday reading on:

Re: v16 Time picker - bound variable changed

LISTBOX SET PROPERTY was created in 16R2, it's normal that it won't compile on 16.3 (if that is what you mean) http://doc.4d.com/4Dv16R6/4D/16-R6/LISTBOX-SET-PROPERTY.301-3547819.en.html 2018/06/12 6:09、Jody Bevan via 4D_Tech <4d_tech@lists.4d.com> のメール： I submitted

Re: v16 Time picker - bound variable changed

I submitted a bug on Sunday in regard to 16.3 Hotfix 4 where the command Listbox Set Property and all the lk_ constants are not dereferenced (thus cannot compile). In the Method editor one ends up with just a numerical reference. Jody > On Jun 11, 2018, at 2:40 PM, Keisuke Miyako via 4D_Tech

Re: v16 Time picker - bound variable changed

it is a bug that was fixed in 16.3 Hotfix 1 (latest is Hotfix 4) ACI0097700 2018/06/12 0:40、David Samson via 4D_Tech <4d_tech@lists.4d.com> のメール： Should I be defaulting the time on the on-load of the holding form now? Or is it something else? **

v16 Time picker - bound variable changed

Whilst doing some initial tests on converting a large DB from v14 to v16 (Windows) I came across a strange error. A dialog form has a time picker on it. This worked fine in v14.3 but in v16.3 I get an alert "Bound variable changed" as the form is opened. I do default the time on loading the sub fo