×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 02-Mar-2012 12:56 , CRPence wrote:
On 02-Mar-2012 11:38 , John McKee wrote:
<<SNIP>>
So, I converted 21 (assumed decimal, based on 32 being ASCII value
of 2 for manual input) to 15.
<<SNIP>>
SWAG... Consider that both the decimal difference 39-20=19 and the
decimal difference 21-2=19. Also that assuming either set of values
is hexadecimal instead, that does not allow a similar subtraction to
get an equivalent difference.
dec val <<SNIP>>
Please ignore my prior nonsensical reply [which was just a portion of
my attempts to understand the chosen value '15']; unintentionally sent,
as I shut down for the weekend. Seems I properly canceled the other
reply that I was composing. Anyhow, I will make a new and hopefully
comprehensible reply to the earlier quoted message, to describe why
neither the ASCII control character 0x15 [the <nak> control character]
nor the 0x3135 [string '15'] is desirable for the tray specification in
the DATA; i.e. instead, that the 21 should remain decimal versus
hexadecimal 15, but as the character string [decimal] value '21'.
Regards, Chuck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.