RE: JHora is not validating the Wrong Date as Birth Date

[Guest guest]

Dear friends,

 

This can actually be a useful “feature”.

When looking for muhutas etc around the end of a month (say around May 30th),

it is useful to be able to increment the date to May 31st, 32nd

etc without having to think about the number of days in the month. The

underlying swiss ephemeris library has no problem with this input, so it does

work correctly. This is also useful for rectification. In JHora, for the birth

date as well as birth time, you can even enter –ve numbers ! Since the

output is “correct”, I vote for leaving this as is.

 

Thanks,

 

ajit

 

 

 

 

 

Rao Nemani

[raon1008]

Thursday, June 24, 2004

12:14 PM

jhora

JHora is not

validating the Wrong Date as Birth Date

 

 

 

 

 

Hare Rama Krishna

 

Namaste Narasimha Ji,

 

After used for an Year your Commercial Version,

today, I have

found that, the Jhora is not validating for the

birth date.

 

Today I have accidently entered the following

date and surprised

to see it did not complained about the wrong

date of birth.

 

Year : 2004

Month : June

Date : 2004 ( actually I wanted to enter 24, but

accidently

entered 2004 which is the year)

 

Can you please see whether I am making any

mistake of may be

you can fix this before you release the next

version soon.

 

Regards

Raghunadha Rao

 

 

 

 

 

 

[Guest guest]

Namaste all,

 

I have decided the Guru Pournima day next Thursday as the release day. I am frantically working on making the daylight savings time calculations correct for USA, Australia etc. This will be the last thing to get in.

 

However, I did think about this a while ago. I do capture bad years (e.g. enter 24000 in the year field and see). Regarding dates, the valid range varies from month to month. Based on the month and year, the valid range can be 1 to 28 or 1 to 29 or 1 to 30 or 1 to 31. Basically, it is more involved than the year. It is not a matter of simply calling DDV_MinMaxInt() function of MFC with some hard numbers, like I do for years. Computing it correctly and setting the limits is possible, but I thought it was an unnecessary effort. I was actually thinking in the same lines as Ajit and thought it could be beneficial to allow the date to go over 31 for muhurtas etc.

 

I can revisit this later, for the next year's release.

 

Best regards,

Narasimha

 

-

Ajit Krishnan

jhora

Thursday, June 24, 2004 8:11 PM

RE: JHora is not validating the Wrong Date as Birth Date

 

 

Dear friends,

 

This can actually be a useful “feature”. When looking for muhutas etc around the end of a month (say around May 30th), it is useful to be able to increment the date to May 31st, 32nd etc without having to think about the number of days in the month. The underlying swiss ephemeris library has no problem with this input, so it does work correctly. This is also useful for rectification. In JHora, for the birth date as well as birth time, you can even enter –ve numbers ! Since the output is “correct”, I vote for leaving this as is.

 

Thanks,

 

ajit

 

 

 

 

 

Rao Nemani [raon1008] Thursday, June 24, 2004 12:14 PMjhora Subject: JHora is not validating the Wrong Date as Birth Date

 

 

 

 

 

Hare Rama KrishnaNamaste Narasimha Ji,After used for an Year your Commercial Version, today, I have found that, the Jhora is not validating for the birth date.Today I have accidently entered the following date and surprised to see it did not complained about the wrong date of birth.Year : 2004Month : JuneDate : 2004 ( actually I wanted to enter 24, but accidently entered 2004 which is the year)Can you please see whether I am making any mistake of may be you can fix this before you release the next version soon.RegardsRaghunadha Rao

 

[Guest guest]

Dear Friends,

Yes, Even I think that to be feature. And would vote to remain as is.

 

But I do have other sugestions,

 

1. Sarvotabadra Chakra to have East at top.

As all charts like south indian format have East at top (Ar-Ta)

It would be great to continue the traditional way.

 

2. The Swaruda option has redundant options like

Quadrants from Graha Arudha and Bhava Arudha.

It's redundant because the Graha Arudha always falls

in quadrants to its Bhava arudha. So if a graha is

in quadrant to one Graha arudha then it will be quad to

the Bhava arudha.

 

3. To have the Start or End times of all the 15 day and 15 night

muhurthas in Panchanga section.

And also name of current Muhurtha in Key Info Section.

 

Hope this are good suggestions

 

Thank you

Sanjay P

 

 

 

jhora , " Ajit Krishnan " <ajit@m...> wrote:

> Dear friends,

>

>

>

> This can actually be a useful " feature " . When looking for muhutas

etc around

> the end of a month (say around May 30th), it is useful to be able to

> increment the date to May 31st, 32nd etc without having to think

about the

> number of days in the month. The underlying swiss ephemeris library

has no

> problem with this input, so it does work correctly. This is also

useful for

> rectification. In JHora, for the birth date as well as birth time,

you can

> even enter -ve numbers ! Since the output is " correct " , I vote for

leaving

> this as is.

>

>

>

> Thanks,

>

>

>

> ajit

>

>

>

> _____

>

> Rao Nemani [raon1008]

> Thursday, June 24, 2004 12:14 PM

> jhora

> JHora is not validating the Wrong Date as Birth Date

>

>

>

>

> Hare Rama Krishna

>

> Namaste Narasimha Ji,

>

> After used for an Year your Commercial Version, today, I have

> found that, the Jhora is not validating for the birth date.

>

> Today I have accidently entered the following date and surprised

> to see it did not complained about the wrong date of birth.

>

> Year : 2004

> Month : June

> Date : 2004 ( actually I wanted to enter 24, but accidently

> entered 2004 which is the year)

>

> Can you please see whether I am making any mistake of may be

> you can fix this before you release the next version soon.

>

> Regards

> Raghunadha Rao

>

>

>

<http://us.adserver./l?M=295196.4901138.6071305.3001176/D=groups/S=

> :HM/A=2128215/rand=747556688>