Related
Hi @ll
i have an idea when vieuwing websites, that portrait mode gives the mobile view, but if i rotate my hero to landscape i can switch to the full version of the website.
would this be possible at all ?
grtz
I hope it won't be just 90 degrees counterclockwise.
I'm still puzzled by this limit.
(double entry)
do not want
Why? As a left-handed I find the "normal" landscape orientation quite uncomfortable!
in most cases, it would involve reloading the site, which would suck if im on a gprs conxn.
@warsng
If you don't need to reload for a 90 degrees counterclockwise, you won't for 90 degrees clockwise!
And, if your abjection is general, keep in mind that most of the time the two things are just a change of CSSes away, which is not a site reload, just a new presentation.
You objection makes sense, though.
Hi
I love my desire. The HTC calculator is nice with the finger friendly buttons with haptic feedback, and I love the fact it's respecting the operator priorities. But what's wrong with the calculator?
100 - 99,9 = 0,09999999999999999
100 - 99,8 = 0,2
100 - 99,7 = 0,2999999999
100 -99,6 = 0,4
100 - 99,5 = 0,5
100 - 99,4 = 0,599999999
100 - 99,3 = 0,7
100 - 99,2= 0,7999999999
100 - 99,1 = 0,9
is this a known issue?
Do you know another calculator where you can review all the line you typed and correct it if needed, that has big buttons, has parenthesis, and that give accurate results? I used to use HiCalc on WinMo, but I can't seem to find a good substitute on android.
Turn the phone to landscape and more functions are available like parentheses. Not sure about your other points!
funny - i needed this calculator for my school time
100 - 99,2= 0,7999999999
i have same result
br stupsi
stupsi99 said:
100 - 99,2= 0,7999999999
Click to expand...
Click to collapse
Google floating point precision
nparley said:
Google floating point precision
Click to expand...
Click to collapse
Most likely this.
And I use RealCalc which seems to correct for it.
This is mad.
My calculated is screwed too. Lol
Sent from my HTC Desire using XDA App
Why are you putting commas in not decimal points? 99.7 not 99,7
^^^^ Other people in the world write things differently to us
ok...this is new...lol
do you guys think a solution is possible? or should we all get another calculator?lol
You need to get another calculator.
Seems that HTC's calculator is using floating point rather than fixed point or decimal floating point.
Regards,
Dave
it is also a problem on the Vanilla calculator.
I'm using OpenDesire and it also has this problem.
bedeabc said:
^^^^ Other people in the world write things differently to us
Click to expand...
Click to collapse
they might, but if the calculator is configured to work with points not commas I'm not surprised it fails
Edit
Wrong! Is the same with points as commas. My bad
When we use the calculator we press the . button, as there is no comma.
FYI when in the UK you write 1,002.50 the rest of the world writes 1 000,50.
HTC answered me to find another calculator on the maket, cause the HTC calculator is a basic one. LMAO I know it won't solve complex equations, but 100 - 99.9 should be solved by any basic calculator, even by a 7 year old pupil...so I guess it should be solved by a calculator that displays basic trigonometry buttons, shouldn't it?
It fails with points as well.
100-99.9=0.0999999999
So it's not a localisation thing, it's just a rubbish calculator.
This happens to any substraction having the following pattern:
n-((n-1)+p), where p = {0.9, 0.7, 0.4, 0.2}
And it doesn't matter whether the Calculator uses '.' or ',' for digits.
Very strange...
Benj555 said:
FYI when in the UK you write 1,002.50 the rest of the world writes 1 000,50.
Click to expand...
Click to collapse
That depends on your definition of the rest of the world.
The two most populous nations on the planet, namely China and India, use the point as the decimal separator, as does the US, Japan, and most of the ex-British empire.
For the most part, the "Decimal Comma" is in use in mainland Europe and most of South America.
Regards,
Dave
Benj555 said:
When we use the calculator we press the . button, as there is no comma.
FYI when in the UK you write 1,002.50 the rest of the world writes 1 000,50.
Click to expand...
Click to collapse
The 'rest of the world' write: 1.000,50 (they use the '.' to group thousands - e.g. 154.234.345,243)
nparley said:
Google floating point precision
Click to expand...
Click to collapse
Don't see why floating point should have anything to do with this. Floating point is relevant where there is a greater number of digits required to do the calculation than would normally be displayed. This is a simple subtraction of a number with one decimal place. This is just plain wrong!
norm2002 said:
Don't see why floating point should have anything to do with this. Floating point is relevant where there is a greater number of digits required to do the calculation than would normally be displayed. This is a simple subtraction of a number with one decimal place. This is just plain wrong!
Click to expand...
Click to collapse
nparley is correct.
Whomever wrote the HTC calc app used binary floating point data types. The subtraction is being performed "correctly" within the limitations imposed by the use of that data type. 0.1 cannot be exactly represented by that data type, which is why this issue shows up.
Regards,
Dave
No, in the UK we would use . to indicate decimal and , to indicate thousands. Which I think is standard?
The calculator calculates wrongly
Try the following:
5+1*5+1
You would think that this equals 11 but not in WP7 land
You could argue that its not a failure and its supposed to work in that way, but then at least the way the calculation is displayed is incorrect.
And even more ridiculous is the whole thing when you turn your phone sideways - then it works like expected
So to sum it up (haha!):
Microsoft seems not to be able to program a simple calculator - a firm with 1000s and 1000s of engineers ;D
Most phone calculators would make it 31, not 11. In landscape, it goes into an engineering mode so begins to work properly.
vangrieg said:
In landscape, it goes into an engineering mode so begins to work properly.
Click to expand...
Click to collapse
Ah! I didn't know that. Nice
Never mind , I get 11
Sent from my GT-I9000 using Tapatalk
the caluclators with no "memorydisplay" would make it 31, but when there is a display at least I had thought that it would calculate like the line in the top of the screen... maybe its me.
vetvito said:
Never mind , I get 11
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
So do I whether in portrait (simple view) or landscape (scientific view)
The android calc shows me also 11
its not only a WP7 bug
Hassan99 said:
The android calc shows me also 11
its not only a WP7 bug
Click to expand...
Click to collapse
How's that a bug, it is supposed to be 11
It was the same in WM. On my HD2 it would act like a "dumb" calculator in portrait and yield 31, and get "smarter" in landscape. So it's hardly a bug.
Maybe its not a bug (thats why I made the " in the topicname), but it is:
1. false (at least in the line on the top)
2. inconsistent and not intuitive (why behaves the calculator different in each view)
001mic said:
Maybe its not a bug (thats why I made the " in the topicname), but it is:
1. false (at least in the line on the top)
2. inconsistent and not intuitive (why behaves the calculator different in each view)
Click to expand...
Click to collapse
It looks like a "feature" that was brought over from WinMo.
I was quoting a person that made it look like other platforms were affected by the same "feature".
001mic said:
Maybe its not a bug (thats why I made the " in the topicname), but it is:
1. false (at least in the line on the top)
2. inconsistent and not intuitive (why behaves the calculator different in each view)
Click to expand...
Click to collapse
Because in portrait mode it's a simple desk-calculator like thousands of people use everyday. They are working like this, one calculation after the other. It would confuse people to see it work "correctly", because they won't understand what's going on.
For people that are used to it, we simply use the engineering mode in landscape and it's working as expected by them.
Portrait mode doesn't even have Pi =)
FWIW, the HTC Calculator for WP7 correctly returns 11 in both portrait and landscape modes.
Tried it on a Trophy. Portrait = 31, landscape = 11.
Was about to ask why it is 11, but then worked it out. No wonder most people are afraid of mathematics.
heh. order of operations..
in portrait, the calculator does the calculations in the order they are entered.
in landscape, it follows the order of operations.
Calculator in windows will behave the same way if you enable scientific mode.
lqaddict said:
I was quoting a person that made it look like other platforms were affected by the same "feature".
Click to expand...
Click to collapse
I think I said "most phones". Every dumbphone I had did the same thing. I remember I had to store intermediate results in memory to get the calculations right.
001mic said:
Maybe its not a bug (thats why I made the " in the topicname), but it is:
1. false (at least in the line on the top)
2. inconsistent and not intuitive (why behaves the calculator different in each view)
Click to expand...
Click to collapse
I don't see any usefulness in this "feature" either. On the other hand, it does seem to be the standard Windows behavior, and since I haven't heard lots of complaints about it, maybe that's what "most" people expect. Who knows.
It does look silly and useless, I agree.
Seems like the expected results to me. If it was like a TI-83 where you could type it on one line and then hit Equals, I would be concerned. It's interesting to know when it's in scientific mode it functions like that.
But since it's just a simple one in portrait mode, it will do 5+1, multiple by 5, plus 1.
" 5 + 1 X 5 + 1"
Normal: 5+1 = 6 > 6 x 5 = 30 > 30 + 1 = 31
Scientific: 5 + (1 x 5 ) + 1 = 5 + 5 + 1 = 11
That's normal, multiplication in first, and after addition.
(Sorry for my English :s )
It doesn't matter how you try to justify it, its still wrong.
I bet every calculator with the result of 31 does not have a line where the calculation shows up - that's where the failure lies in the wp7 calculator.
It shows you, that you have calculated 3+3*4 so far, but in reality he calculated (3+3)*4.
So either they:
-don't show this misleading line
-show it differently (e.g. 3; +3; *4; ...)
-calculate "correct"
What I think imho is that they can not show it in the exact same way in portrait and landscape mode but calculate differently.
Okay I also just noticed that you can "take" the wrong calculation with you to the landscape mode (start making a calculation and then turn it sideways)
Then you have the wrong result to the calculation even in the scientific mode.
This is not excusable in my opinion. Is there any reason that it not should adjust the calculation, either in the result, or in the calculation line? I think not.
I think its a bug
I am trying to figure out how to calculate dewpoint from temperature and humidity. The formula is ridiculously long, but there is a simple formula that gives an approximation, which is good enough for my purposes.
Td = T - ((100 - RH)/5).
Td = Dewpoint in degrees Celcius
T = Temperature in degrees Celcius
RH = Humidity
Since my phone is in degrees F. I had to convert to degrees C. This is what I did, but it doesn't work, I think because of the % symbol attached to the humidity variable: $int((#WCTEMP#-32)*5/9))-(100-#WCHUM#)/5)$. The problem is, it just displays exactly what I typed, it doesn't do the math. Can anyone point a noob in the right direction? It is probably obvious, but I am still trying to figure out zooper.
I have seen other requests for a dewpoint variable on the forums, so there is a demand out there. Any help would be appreciated, thanks!
Do you own Tasker?
You could do an https get on yahoo weather api and get all the info from there.
Its not to terribly difficult. Probably on the intermediate level.
Sent from my Nexus 5 using Tapatalk
I was just considering purchasing that tonight. I will give that a shot! Thanks Mr Biggzz
MrBiggzz said:
Do you own Tasker?
You could do an https get on yahoo weather api and get all the info from there.
Its not to terribly difficult. Probably on the intermediate level.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Its a great app!
Sent from my Nexus 5 using Tapatalk
@robgross how are you making out?
MrBiggzz said:
@robgross how are you making out?
Click to expand...
Click to collapse
I downloaded Tasker but haven't had time to learn it yet...but I will! I do know that ZW sees #WCHUM# as text, so it will not formulate it. I tried using #WCHUMN# to see if it would dispay the value as a number, as #WCTEMPN# does...but that didnt work. Thanks for following up!
Christmas in May!
Dave Handler shares a file with you, please click the link to download: http://dl.dropboxusercontent.com/1/view/qqiv1skjchq7ifu/Tasker Projects/Yahoo_Weather.prj.xml
In it are two tasks Input Zip code which uses a scene to well, get the zip!
The other task is Get Yahoo Weather. That uses a variable that gets set when you set the zip code.
Set your zip and the run the weather task and then check the variables tabs. You'll see every thing that is supplied including the five day forecast.
You'll have to figure what you want and pass it on to Zooper. Every variable for weather is global!
Enjoy!
p.s. everything is in standard units. Fahrenheit, mph and inches. This only thing I didn't do is give you an indicator if the barometric pressure is falling, stable or rising. If you need it I can put it in there!
Sent from my Nexus 5 using Tapatalk
Mr. Biggs, thanks for this, but I can't seem to open this link, it says it's not valid both in Tasker and a browser.
MrBiggzz said:
@robgross how are you making out?
Click to expand...
Click to collapse
MrBiggzz, I figured out how to use Tasker! It's a lot easier to use than I thought, and the possibilities are endless. Thanks for the tip!
I know its an old thread and i was seaching in this thread too; and now i solved by myself. I post here the solution for tasker if someone needs it:
You need to set up or read out from web 2 variables (%temp = temperature and %hum = humidity), once you have set the 2 variables you need to add a code java scriplet to the task to calculate dewpoint and absolute humidity:
function taupunkt() {
if ( (temp == null || temp == 0) ||
(hum == null || hum == 0) ) {
return;
}
var a1=7.45;
var b1=235;
tp=temp;
fw=hum;
tp=tp*1;
fw=fw*1;
x1=(a1*tp)/(b1+tp);
e1=6.1*Math.exp(x1*2.3025851);
e2=e1*fw/100;
x2=e2/6.1;
x3=0.434292289*Math.log(x2);
taux=(235*x3)/(7.45-x3)*100;
taux=Math.floor(taux)/100;
feux=(216.7*e2)/(273.15+tp)*100;
feux=Math.round(feux)/100;
var TAUX = taux;
setGlobal("TAUX", TAUX );
var FEUX = feux;
setGlobal("FEUX", FEUX );
exit ();
}
taupunkt()
The java scriplet calculate the dewpoint and the absolute humdity and stores it in the variable %TAUX (dewpoint) and %FEUX (absolute humidity). Now you can make a popup alert or whatever you want and display the dewpoint calling %TAUX and the absolute humidity %FEUX
I own an A52s 5G and have a problem where all the apps based on compass that I use don't show the same values. Samsung's own panel overlay, Stellarium, ISS Detector and Google Maps all disagree on where north is, some more than 20 degress while others 1 or 2 to either west or east. I don't own a real compass so I cannot measure with accuracy where north is and say which app is more accurate, but I am sure that they shouldn't be showing different values. Of these apps I mentioned ISS Detector is the only one with a compass offset correction option, which doesn't solve much. I've already tried the 8 drawing calibration method and rotating on the axis one on each app, but have not got any different results. I would be grateful if anyone could help me fix this problem, or at least give some hints of what might be causing it.