Full Version: Turkey Layout

From: Carl (CSEWELL) [#12]
 22 Oct 2006
To: Harvey only (HARVEY-ONLY) [#11] 22 Oct 2006

Harvey,

I understand HEX, but I don't understand the point you are trying to make. Yes, the character that follows the CRD is hexadecimal notation. Is that the point you were trying to make?

From: BrianC (INKSQUIRTER) [#13]
 22 Oct 2006
To: Carl (CSEWELL) [#7] 22 Oct 2006

Carl,

I chose the ver 9 to save as....so I thought at least.

I just tried it again, maybe it will work for others now.


From: Carl (CSEWELL) [#14]
 22 Oct 2006
To: BrianC (INKSQUIRTER) [#13] 22 Oct 2006

Yep, that worked!

That's one of the reasons why I created a macro to do that for me. It's real easy to forget to check the box when doing a Save As. Or, if you save it once as version 9, the next time you save it will default to the current version. Version 12, however, does warn you before it saves it.

From: BWC (SPY007) [#15]
 22 Oct 2006
To: BrianC (INKSQUIRTER) [#13] 22 Oct 2006

Worked for me as well.

Thanks


From: BrianC (INKSQUIRTER) [#16]
 22 Oct 2006
To: BWC (SPY007) [#15] 22 Oct 2006

good!

From: Dave Jones (DAVERJ) [#17]
 22 Oct 2006
To: Carl (CSEWELL) [#12] 22 Oct 2006

Carl, Harvey was pointing out future versions. He's saying that when they get to CD version 15 they will use "F" and when they get to version 16 they will be using hex "10" as the version number in the place you are talking about.

From: UncleSteve [#18]
 22 Oct 2006
To: Dave Jones (DAVERJ) [#17] 22 Oct 2006

And don't be one bit surprised if it comes out as 14 or X4 to maintain continuity...

From: Carl (CSEWELL) [#19]
 22 Oct 2006
To: Dave Jones (DAVERJ) [#17] 22 Oct 2006

Dave;

That was an assumption he made that I didn't understand. I don't think that they'll stick to a true hexadecimal number to represent the version number in the CDR file based only on the assumption that it appear to be a one byte field. If it were truly a hexadecimal numbering scheme, it wouldn't display as an ASCII representation of that value (ie an "A" would actually have a hexadecimal value of 65, decimal, not "10", decimal, as Harvey suggested).

Going to "10h" (2-digits) for sixteen would require two bytes. I doubt they will change (assuming it is currently a single byte field) the file format to accommodate a hexadecimal (2 digit) number scheme. After all, a "G" (ie for version 16) or sequential ASCII decimal number is just as easy to deal with in a programming environment.

From: Derek (JUSTWELDIT41) [#20]
 22 Oct 2006
To: Carl (CSEWELL) [#19] 22 Oct 2006

Worked for me thanks and looks great.

Derek


From: Harvey only (HARVEY-ONLY) [#21]
 22 Oct 2006
To: Carl (CSEWELL) [#19] 22 Oct 2006

Only way to know is to wait a few years.

Lots of programs put out the ASCII letters for the hex number. Look at the registration numbers on the programs, lots of ASCII hex there.

At least the old HPGL put out full float decimal values, a horrid waste of space and computing power though.


From: basehorawards [#22]
 23 Oct 2006
To: Carl (CSEWELL) [#9] 23 Oct 2006

1 2 3 4 5 6 7 8 9 A B C D E F 10
11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20


From: Nick (NICKIONPOE) [#23]
 24 Oct 2006
To: BrianC (INKSQUIRTER) [#1] 24 Oct 2006

Thank you for sharing.... I think I will do the same and send them in to my son's kindergarten glass.

Thanks for sharing!!!

Nicole


Show messages:  1-11  12-23

Back to thread list | Login

© 2025 Project Beehive Forum