Beautiful simulation of particle added with gravity inside canvas with help of javascript. link to demo page[^] link to blog explaining it.[^]

Sorry unable to delete. :(

As you wish. Will remove it in next 5 min.

Why do users click randomly and rapidly when an application hangs? This is an interesting question WHY do user click knowing that it is hanged. :wtf: i found it while just randomly clicking on the link. One more thing even if you are too lazy to click on the link and read the whole post just check this image it is really funny. Image Link

Motion JPEG Streaming Server May this is what you are looking for.

I thought that it was to save Dark enrgy used in between the two calculation steps. :laugh: Just Joking. :-\

:thumbsup:

From you article Adding Post-commit Hook to SVN Source Control It seems like you are much better than other. :laugh:

It is just pointless to add one more calculation step without any reason. :)

Link to the article For More detail explanation(PDF) Counting arrays from 0 simplifies the computation of the memory address of each element. If an array is stored at a given position in memory (it’s called the address) the position of each element can be computed as

element(n) = address + n * size_of_the_element
//If you consider the first element the first, the computation becomes

element(n) = address + (n-1) * size_of_the_element
//Not a huge difference but it adds an unnecessary subtraction for each access.

It very often that while reading an article i found some more article on other topics which i would like to read but currently its not possible.So i used to bookmarks article for later reading but after a while my bookmarks became over crowded and difficult to find what i read, what want to read and what are article i really want to bookmark. So i would really appreciate if you add a button "Read it Later" on the article page like YouTube "Watch it Later". One more thing i would like to be added: Shot by Bookmarked date in "Bookmarks" because it very hard to find what i bookmarked last time.Every time i have to scroll till the end to find the one.

Jasmine2501 wrote:

official licensed version of your application is easier to get than the cracked version.

you are right.why don't i thought like that. :doh:

Thanks But little bit scared because Obfuscator only change the names of methods,class,var to some random name.Means still can be decompiled and a very curious person can understand it. And one more thing

Dim password as String ="sometxt"

sometxt can still be seen in memory dump of process is there any way to hide.

Eddy Vluggen wrote: You're building a new house, because you did not like the way the old one is painted? Actually, the house has wrong things in wrong places which could not be done by just shifting the rooms. :( Eddy Vluggen wrote: "NotInheritable" is meant as a code-construction that helps during development, not as a means to stop hackers. Open up ILSpy, load your assembly, copy and paste I have put a method

verify(apikey,secret)

with which you can activate every class and without it nothing will work. It may be seen as constructor method. Eddy Vluggen wrote: Dunno, how many have you got? How many would your users want?   If the app is becoming too complex for the average user, then hide some of the features under an "Advanced" tab or button. Hmm, that is good point :thumbsup:

I have created a application in .Net for remote desktop connection and it is working fast and secure also, but for some reason i am not satisfied with the User Interface so just decided to rewrite the code again from the beginning. ;) But the problem came with the security from the hacker,cracker. yeah i know that .Net app can be easily de compiled so obstruced the code and declared all the class as not inheritable so that they can't import the app and create a object for the some important class and understand the algorithm or working behind it. Is there any other thing i am missing :doh: Can give any suggestion for the UI or features. One More Question: Should i kill features for the shake of UI.(i think i should kill features).