I'm confused about offsets.
If someone tells me to edit something at the offset "0x0805F4B0",
what would I type in my hex editor's "Jump To" function?
I would hope the editor would make clear what form of input it expects there. Ideally, 0x0805F4B0 would work. Failing that, I would try 0805F4B0 and 805F4B0. As a last resort, I'd try 134608048 (i.e. 0x0805F4B010).
Hmm... which question such answer... may be you must enter 0805F4B0 in 'jump to'? Or you can enter this number converted to decimal value? Any modern calculator can convert numbers between hex and dec
Related
I'm using List & Label to display results on a report (floats) and I don't want them to be displayed by large numbers of decimal places like:
0.00005850
but like:
5,85e-05
I would be glad if someone had a hint for me :-) I already tried out the number format settings but nothing suiting there. Excel does this automatically, but is there a way in List&Label at all?
For me, the scientific exponential format works nicely - have you tried this setting?
I am trying to create a regular expression for a dollar amount that accepts values between 5.00 and 1000.00.
Here is what I have so far:
^([5-9](\d){0,4}([.](\d){1,2})?|1000([.](0){1,2})?)?$
I have already tried the range validator and it isn't working this field.
Any help is much appreciated.
This is what I came up with, which could likely be improved. It seems to work for my limited testing. You may want to tag your question with "regex" to get some expert advice!
^(?:[5-9](?:\.\d{0,2})?|\d{2,3}(?:\.\d{0,2})?|1000(?:\.0{0,2})?)$
I have a double variable assigned to a boundfield in a gridview. There will only ever be a max of 5 decimal places.
The boundfield is formatting the display to a scientific value. I'm assuming because it would default to a general format which gives the most compact of either fixed-point or scientific notation (https://msdn.microsoft.com/en-us/library/system.web.ui.webcontrols.boundfield.dataformatstring%28v=vs.110%29.aspx)
How can i format the number to show only as many decimal places as needed, up to 5. And do not show scientfic notation?
i.e.
0.00002 is currently showing as 2E-05, but I would like it to show as 0.00002.
0.002 should show as that, and not 0.00200.
1 should show that, and not 1.00000. etc.
So a format such as {0:N5} would not work. {0:N} defaults to 2 decimal places, and so would not work either.
Thanks for any help.
Thanks for the advice #David W
I ended up working it out anyhow.
Although I couldn't find any documentation on it, you can give it proper custom formats.
Therefore, the following solved my issue;
<asp:BoundField DataField="theField" DataFormatString="{0:0.#####}" />
I thought to ask this as an update to my previous similar question but it became too long.
I was trying to understand a regex given in w3.org that matches css comments and got this doubt
Why do they use
\/\*[^*]*\*+([^/*][^*]*\*+)*\/
----------------^
instead of just
\/\*[^*]*\*+([^/][^*]*\*+)*\/
?
Both are working similarly. Why do they have an extra star there?
Let's look at this part:
\*+([^/*][^*]*\*+)*
-A- --B-- -C-
Regex engine will parse the A part and match all the stars until there is NO MORE stars or there is a line break. So once A is done, the next character must be a line break or anything else that's not a star. Then why instead of using [^/] they used [^/*]?
Also look at the repeating capturing group.
([any one char that's not / or *][zero or more chars that's not *][one or more stars])
It captures groups of characters ending with atleast one or more stars. So C will take all the stars leaving B with no stars to match in the next round.
So the B part won't get a chance to meet any stars at all. That is why I think there's no need to put a star there.
But that regex is in w3.org so I guess my understanding may be wrong. Please explain what I'm missing.
This has already been corrected in the CSS3 Syntax module:
\/\*[^*]*\*+([^/][^*]*\*+)*\/ /* ignore comments */
Notice that the extraneous asterisk is gone, making this expression identical to what you have.
So it would seem that it was simply a mistake on their part while writing the grammar for CSS2. I'm digging the mailing list archives to see if there's any discussion there that could be relevant.
I am working on a project that involves converting data into dos date and time. using a hex editor (Hex Workshop) i have looked through the file manually and and found the values I am looking for, however I am unsure how they are calculated. I am told that the int16 value 15430 corresponds to the date 06/02/2010 but i can see no correlation, also the value 15430 corresponds to the time 07:34:12 but i am lost in how it is calculated. any help with these calculations would be very welcomed
You need to look at the bits in those numbers.
See here for details:
http://www.vsft.com/hal/dostime.htm
I know this post is very old but I think the time 07:34:12 corresponds to 15436 (not 15430).