Re: Write Hex Bytes

> 2019/02/22 9:45、Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com>のメール: > the task was to process a single value 78,487,500 or 0xCC9FAD04; correction: decimal 78,487,500 is 0x04AD9FCC > If I have a number 78487500, this translates to CC 9F AD 04. but PC byte ordering will give you CC 9F AD

Re: Write Hex Bytes

you're right, I re-read the OP, the task was to process a single value 78,487,500 or 0xCC9FAD04; not 4 separate decimal values 78, 48, 75 and 00 > 2019/02/22 9:43、Justin Carr via 4D_Tech <4d_tech@lists.4d.com>のメール: > > C_BLOB($vX_Data) > C_LONGINT($vL_Offset) > > $vL_Offset:=0 > LONGINT TO

Re: Write Hex Bytes

On 22 Feb 2019, at 10:30 am, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> wrote: > > it sounds like you are over-thinking :) > > you could just do > > SET BLOB SIZE($bytes;4) > > $bytes{0}:=78 > $bytes{1}:=48 > $bytes{2}:=75 > $bytes{3}:=00 > > then BLOB TO DOCUMENT. > > not need to go

Re: Write Hex Bytes

it sounds like you are over-thinking :) you could just do SET BLOB SIZE($bytes;4) $bytes{0}:=78 $bytes{1}:=48 $bytes{2}:=75 $bytes{3}:=00 then BLOB TO DOCUMENT. not need to go through hex. 2019/02/22 9:27、Peter Mew via 4D_Tech <4d_tech@lists.4d.com>のメール: If I

Re: Write Hex Bytes

Hi Actually, I dont think this quite what I want, Unless Im Misunderstanding whats going on. If I have a number 78487500, this traslates to CC 9F AD 04. If I carry out your method, I get 8 bytes added to the initial string. However,If I read the hex number from a file on disc, it only takes up 4

Re: Write Hex Bytes

Hi Yes, Thats it almost exactly, I just need to convert to little endian, I think I can manage that! Thanks -pm On Thu, Feb 21, 2019 at 10:45 PM Arnaud de Montard via 4D_Tech < 4d_tech@lists.4d.com> wrote: > > > Le 21 févr. 2019 à 22:09, Peter Mew via 4D_Tech <4d_tech@lists.4d.com> > a écrit : >

Re: Write Hex Bytes

> Le 21 févr. 2019 à 22:09, Peter Mew via 4D_Tech <4d_tech@lists.4d.com> a > écrit : > > Hi > This is driving me mad, so I hope someone will point me in the right > direction. > I have a string of text. > I can find its length in Hex. now I want to write this length as 4 hex > bytes, into the

Re: Object notation bug?

Drew, On Thu, Feb 21, 2019 at 10:27 AM Drew Waddell via 4D_Tech < 4d_tech@lists.4d.com> wrote: > I am unable to do $oChildObject:=null in my actual situation because I am > passing that object into a Dialog You run into this when passing the object to a new form using DIALOG. I use two

Re: Write Hex Bytes

**IF** I understand what you are trying to do you are halfway there in both cases, and is fairly easy. I think what you want is: String+Hex[[1]]+Hex[[2]]+...+Hex[[n]] Example: "This is my string of which I want the length" (decimal) 44 characters 44 (dec) = 2C (hex) final value: "This is my

RE: Object notation bug?

Just FYI for those following along, I tried the following in my test method even though I wouldn't be able to in my Form object scenario: $oChildObject:=Null // $oParentObject.ChildInformation = {FirstName:John,LastName:Smith} Drew -Original Message- From: 4D_Tech

RE: Object notation bug?

I am unable to do $oChildObject:=null in my actual situation because I am passing that object into a Dialog so in my situation $oParentObject is actually the Form object, I don't have the local variable for $oChildObject on the form. So is there another command to clear both references without

Re: Object notation bug?

Hi, That’s not a bug. That’s normal. $oChildObject:=New object create a reference to a object store in $oChildObject OB SET($oParentObject;"ChildInformation";New object) push another reference into the $oParentObject but the old reference still exist because $oChildObject isn’t cleared. you

Object notation bug?

I am trying to figure out if this is a bug or not. This is a watered down version of something I am trying to do: C_OBJECT($oParentObject;$oChildObject) $oChildObject:=New object $oParentObject:=New object

Re: interesting find

Tim the problem is the compiler did not choke on the code and it seemed to worked compiled but did not work in source while testing Regards Chuck Sent from my iPhone > On Feb 21, 2019, at 10:45 AM, Randy Engle via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > I seem to recall that in v1.x of

RE: interesting find

I seem to recall that in v1.x of 4D (or v2 when the compiler first showed up), you could practically write in Swahili, and 4D would not complain.  Every version since then, 4D has become less "forgiving" (or as Tim Says: "smarter") Randy Engle -Original Message- From: 4D_Tech

Re: Menubar 1

do you do: Set Menubar(1) at the end of your startup? Chip On Wed, 20 Feb 2019 23:35:40 -0600, David Ringsmuth via 4D_Tech wrote: > 4D v17R4 2323298 64bit Remote > OSX 10.16+ > > At the end of my startup method Menubar 1 is displayed. > > On some client machines the menu items are not