|
Type thanglish in keyboard when display tamil letters in textbox
|
|
|
|
|
So what is your question here?
modified 20-Sep-20 21:01pm.
|
|
|
|
|
You need to use a translation service, which would read the Tamil words and then generate English, or Thanglish for them. No framework, — ASP.NET, PHP, Node.js even Java EE — is capable of doing this all by themselves.
You can use services by either Google, or Microsoft and then write your own service that converts the words. Which is beyond the scope of these discussions. Both of these giants provide some good APIs that you can subscribe to,
Cloud Translation API - Dynamic Translation | Google Cloud Platform
Translator API - Microsoft Translator
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
Hi,
I want to get the current week of the month in string, like for example I want to check if this current week is the first week of the month, second week of the month like this is it last week of the month. Usually I am not having problem in finding if this week is first, second, third or even 4th but the problem is in finding which is the last week.
Any help is going to be greatly helpful - thanks in advance.
Thanks,
Abdul Aleem
"There is already enough hatred in the world lets spread love, compassion and affection."
|
|
|
|
|
So, which is the last week? Since you are able to calculate the week, what prevents you from finding out whether this is the last, or which is the last week of the month?
Quote: like this is it last week of the month
How? Isn't there going to be another week, or my April 21st, Friday calendar date is wrong? — there is another working week coming up, or maybe I'm a bit more sleepy and should take a nap. 
Perhaps, the question itself is a bit unclear. As a suggestion, please review the following thread, datetime - Calculate week of month in .NET - Stack Overflow
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
Presumably, the last week in the month is the one containing the last day. So if you have any date you should be able to find out which week it is part of.
|
|
|
|
|
Here it is.
public static bool RunForTheDay(bool IsTheJobWeekly, bool IsTheJobMonthly, bool IsTheJobYearly,
int WhatDayOfMonthJobRuns, int WhatWeekOfMonthJobRuns, int WhatMonthOfYearJobRuns,
int WhatDayOfYearJobRuns, bool RunForTheDay, string strDayOfTheWeek)
{
bool retRunForTheDay = false;
//string strDayOfTheWeek = DateTime.Now.ToString("dddd");
if (IsTheJobYearly)
{
if (WhatDayOfYearJobRuns > 0)
{
if (WhatDayOfYearJobRuns == DateTime.Now.DayOfYear)
retRunForTheDay = true;
}
else if ((WhatMonthOfYearJobRuns > 0) && (WhatMonthOfYearJobRuns == DateTime.Now.Month))
{
if ((WhatDayOfMonthJobRuns > 0) && (WhatDayOfMonthJobRuns == DateTime.Now.Day))
{
retRunForTheDay = true;
}
else if (WhatWeekOfMonthJobRuns > 0)
{
int tempWeekOfTheMonth = GetWeekOfMonth(DateTime.Now);
if ((tempWeekOfTheMonth == WhatWeekOfMonthJobRuns) && RunForTheDay)
retRunForTheDay = true;
}
}
}
else if (IsTheJobMonthly)
{
if ((WhatDayOfMonthJobRuns > 0) && (WhatDayOfMonthJobRuns == DateTime.Now.Day))
{
retRunForTheDay = true;
}
else if (WhatWeekOfMonthJobRuns > 0)
{
int tempWeekOfTheMonth = GetWeekOfMonth(DateTime.Now);
if ((tempWeekOfTheMonth == WhatWeekOfMonthJobRuns) && RunForTheDay)
retRunForTheDay = true;
}
}
else
{
retRunForTheDay = RunForTheDay;
}
return retRunForTheDay;
}
public static int GetWeekOfMonth(DateTime date)
{
DateTime beginningOfMonth = new DateTime(date.Year, date.Month, 1);
while (date.Date.AddDays(1).DayOfWeek != CultureInfo.CurrentCulture.DateTimeFormat.FirstDayOfWeek)
date = date.AddDays(1);
return (int)Math.Truncate((double)date.Subtract(beginningOfMonth).TotalDays / 7f) + 1;
}
Thanks,
Abdul Aleem
"There is already enough hatred in the world lets spread love, compassion and affection."
|
|
|
|
|
I have a fairly simple VB.Net application which I wrote a few years ago to chart weather observations. It uses two DateTimePicker controls to specify the date/time range of the data to be charted and had been working fine, once I got a few initial minor bugs sorted out. I don't use it that often (perhaps once every 3-6 months), so I don't know when the behavior I am about to describe started. A couple of days ago, I ran the application, and, instead of defaulting to displaying the beginning and end of the most recent 24 hours for which data was available (e.g. 04/18/2017 12:23), both controls displayed only the delimiter characters (// : ). The values of the fields were apparently correct - choosing a data set and pressing the 'plot' button produced the expected plot of 24 hours' data - but the datetimepicker controls didn't 'work'.
Debugging with Visual Studio confirmed that the contents of all the variables were as expected, but the controls still looked (differently!) weird in the running program, although they looked as they should in design view. Running under Visual Studio, the controls sort of worked, but with an enormous amount of horizontal space (and no delimiters) between each subfield (month, day, year, minutes, seconds), so that only one or at most two subfields were in view at a time.
Has anyone seen anything like this and/or does anyone know what may be going on.
|
|
|
|
|
There was a similar question posted yesterday, but I cannot recall where it was (can't find it in the obvious places). Someone suggested checking the code to see if some control information is being garbage collected early.
[edit]
Found it in the C++ forum: CDateTimeCtrl in Windows 10 - C / C++ / MFC Discussion Boards[^], but not sure if that helps.
[/edit]
|
|
|
|
|
Thanks for the pointer. As you imply, though, other than reassuring me that 'I am not alone', the C++ thread doesn't seem to help. The OP in that thread seems to have seen the problem just after applying the Win 10 Creators Update, which is when I, too, saw it, but I can't imagine why a change in garbage collection could be relevant in my case. I will look again at the code with that potential issue in mind, but I doubt if I will find anything.
[edit]
I have looked at the code. It is a single Form Application and there is nothing even remotely related to the problematic DateTimePickers that should be going out of scope unless/until the Form is closed.
[/edit]
modified 19-Apr-17 11:01am.
|
|
|
|
|
Unfortunately I cannot get the latest Windows update on my system, so cannot test the issue.
|
|
|
|
|
A "few years ago" I was running XP ... .NET something ... and probably a VGA monitor.
Now I run .NET 4.6.1; HDMI monitors; Windows 8.1 / 10; no XP "themes"; new default "font families"; etc.
Most certainly I had to "tweak" my UI's moving forward.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
And your point is?!
If you had read the second paragraph in my original post, let alone the thread that Richard pointed to, you would have seen that almost the first thing I (and the OP in the other thread) did was to go back and rebuild the application, which (at least in my case) only uses standard, current, controls, and determine that the controls in the rebuilt application also showed the strange behavior.
This is not a "the application I created in 2005 doesn't run unchanged under Windows 10" issue.
|
|
|
|
|
You seem mystified by behaviour that I have found typical moving from one "configuration" to another.
You seem to imply you have lived with the same hardware and software all this time and "somehow" have now suddenly gone "nuts".
While pointing me to a C++ forum while your app is VB.NET.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
Our experiences apparently differ. In general, I have found that .Net applications, and particularly their standard controls, almost always continue to work as expected through hardware and software upgrades, so long as the Framework version that they require is still present on the new system. On the very rare occasions when I have seen a problem with an old compiled application on a new system, this has always been corrected by rebuilding the application on/for the new system.
The C++ thread is at least arguably relevant because the apparently very similar problems that both threads describe is in a standard control which is part of the Framework, rather than in user code, strengthening (IMHO) the concern that the problem is one recently introduced into the Framework rather than 'user error'.
|
|
|
|
|
The (Windows Forms) Date Time Picker has been around since 1.1; initially, as a Windows "common dialog" control; so, no, it was not always "standard".
(You were not clear on what version of .NET you first developed on; or even what OS).
And any number of properties are "obsoleted" from one version to the next; and new ones introduced. I'm not convinced there may not be "some" impact somewhere.
It's those "cosmetic" changes (by the vendor) that bite you.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
As per the other discussion looks like Windows has made a structural change which is perfectly normal.
You should be able to go around the problem by just using Windows API. The other guy with the problem said he was losing the last word but I am pretty sure that is because he didn't have enough room in the box for the wording because the font was obviously slightly different spacing. I told him about using the negative height which forces absolute height selection of font and gives windows no latitude to play with it. I don't know what parameters the original MFC code used in selecting a suitable font but you just need to work it out.
WM_SETFONT should and must work because it is an API message if it doesn't work correctly it would be given a high priority to fix from Microsoft because it could effect any and every program.
This should not be a big issue to fix. Using frameworks makes things easier the penalty is sometimes things can change in the Windows API that break the frameworks. The alternatively would be Microsoft not ever be allowed to change anything which as one of your comments already says this stuff has changed multiple times over the years already.
In vino veritas
|
|
|
|
|
Hi,
Got a scenario: we have ASMX web services and we auto-test the service with the help of Soap UI Tool (by SmartBear) every night after launching a new build which also happens every night after merging all the latest changes in the TFS source codes. In the process of test step’s execution, some test step gets failed due to mismatch in test parameter values; this mismatch might be due to change in the values in the source code and check-in by the developer. Some test step gets failed due to null reference and some due to mismatch in testing value stored in sqlserver database. When we try to find the reason of failed test step, it’s a time consuming task every day to find the change-set which caused the failure. Therefore, we want to automate the process to get the change-set for the failed test steps. Here, looking for your expert suggestion for developing a solution for the same.
Please let me know in case you need further clarification.
Thank you
Thank you
JP
|
|
|
|
|
A time consuming process? What, you mean debugging the code? Yeah, you're not going to automate that process.
|
|
|
|
|
Hi Dave,
Soap UI tool generates log file after each execution. To know the reason for the failure, we go through log file. Log file does not have a proper stack trace with filename, methodname, line number etc for the failed test rather the generic reason for the failure of the test step. So, we have to debug the application for the failed method and this process takes a good amount of time to debug and find the bug. Hope it clarifies the question.
Thanks
|
|
|
|
|
In this case, I agree with Pete. You're not going to be able to write code to automatically find which check in caused the problem. You could even have multiple problems.
You have two possible paths here. The first is to debug the code and do what you've been doing. This is, obviously, time consuming and reactionary.
The other is to implement a check in process where the code is tested before you allow it to be checked in. It sounds like you've got people "breaking the build" on just about every check in. That's not tolerable and must be prevented. Yeah, it sounds like it's more time to do this. It is but instead of spending that time on finding and fixing the bug you're spending it on preventing the bugs and improving the quality of the code.
|
|
|
|
|
Thank you, Dave.
Yes, I too thinking about implementing Unit Test part for resolving such problem.
|
|
|
|
|
Member 1263842 wrote: find the change-set which caused the failure.
Since you check in code every day and run this every night then the change-set that caused the error is one of the ones from that day. I guess I don't quite follow what you are asking.
There are two kinds of people in the world: those who can extrapolate from incomplete data.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
If I were in your team, I would suggest that you would be better off with a comprehensive CI process with decent unit tests and pre-flight check ins to ensure that you don't regularly commit broken code.It's better to prevent problems than look to apportion blame.
This space for rent
|
|
|
|
|
Thank you, Pete for your suggestion.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
