WPF touch program development (4) -- salvation of MultiTouchVista _-_ second_release _-_ refresh_2, releasetorefresh

WPF touch program development (4) -- salvation of MultiTouchVista _-_ second_release _-_ refresh_2, releasetorefresh

Multitouch is an open-source software that can be used to simulate touch screens in Win7 (about its usage). The last update was made in February 11, and I started to use it at the beginning, at that time, I developed a photo display and touch program similar to the IPhone album, which is a very useful simulator. Recently, I read several blogs I wrote and asked for code. I turned out the code and planned to upload it. I was afraid of any bugs and I wanted to run debugging again, the result is confusing to me. The Multitouch becomes invalid and red, but the dot screen does not respond anywhere. The key is that once the mouse is taken over, it becomes invalid, the average person cannot return to the normal desktop. Open the drawing and find that no matter how the red dot is painted, it will only be painted in a fixed area. At this time, I am still very calm. I have to unload the driver and try again. It still does not work if I unload the driver and reinstall it, there are quite a few materials searched on the Internet, and none of them can solve the problem. So I started a wonderful experience...

I like problem analysis very much. It was good 10 months ago. What did happen in the past 10 months to invalidate it? I think that hardware is incompatible, software conflicts, viruses, security guards, and system configuration is changed... Not long ago, the system was reinstalled once. At that time, to upgrade SP1 to install VS2013, the original system was reinstalled without being upgraded. Because the original driver was not found, I found some drivers installed on the Internet. As a result, the system was still stable. In addition to a horn, the system went on strike intermittently. I wonder if the driver is not compatible, so I am in trouble. I don't know which driver is incompatible. Why re-install it? That's not a joke. The developer's computer, you know, is just a slap in the eye, and I have no idea if I can solve the problem after I reinstall it, but I only have this method. It was just a weekend, and I had a rest at home. I got up early in the morning and didn't wash my face. My wife was playing with her own computer. She had a computer, installed Win8.1, and searched the internet, this software does not seem to support 8.1. I want to try using her to reinstall Win7, so I want to persuade her to reinstall the system. The result is not worth talking about. Think about whether to waste time, reinstall it.

It took me a morning to export the file. I started to reload it around two o'clock P.M. and found the built-in drive disk. After some twists and turns around for about, I finally installed all the drivers, the first thing I did was try to use it. I still remember the eyes I was waiting for when I opened the palm of my hand and the results were usable. At that time, I decided that it was the driver. Okay, the reason is found. I can close the work perfectly. I have installed all the installed patches and installed them at pm. Everything is done well, install 360 patches and install more than 100 patches. If you don't have them, go to bed. The next day, I woke up and rushed to work. I turned on my computer and checked the patches. All the patches should have been completed. (I started the automatic shutdown mode before going to bed. In the morning, my computer was shut down, I didn't see any new screen after I started the system). I tried Multitouch again and I was relieved to go to work. Later, I wanted to find a file in my company. On my home computer, I remotely went to my home computer. In 360, I reminded me that there were another 25 patches to be updated, after hitting the computer, I tried again. If Multitouch is okay, I shut down the computer.

When I got home from work, I turned on my computer and started the computer to display system updates. I thought it would be normal, because I installed patches remotely at the company during the day and entered the system. A miracle occurred, and the Multitouch failed again! The result seems to have taken the lead for me and I have been beaten. Yesterday I made a day and got it. I wonder if the service is disabled after the update, so it becomes invalid. But which service is used? If you don't know which service is used, I only need to activate all the services! I bet there won't be many people in the world who open all services for a piece of software. At that time, I was almost crazy. I got more than 10 o'clock in the evening, and all the services that can be opened were turned on, but they still didn't work. I think, I don't want to. Isn't it because VS2012 already supports touch program development? I have installed 13 and searched online, you cannot find any information about the touch program that VS2013 can develop. The time passed midnight without knowing it. At that time, the whole person was very tired, unwilling, helpless, and very hot. People could do a lot of things in their minds, so I re-installed the system again, because I can basically conclude that the patch caused the failure, and it was one or some of the latest 25 patches. Unfortunately, I didn't have it at the time, I will find you! It's impossible for me to forget it. I must drag you out!

After the system was reinstalled, it was already two o'clock in the morning. I wanted to continue working on it. I thought I 'd have to rest my body and wake my mind up. Because of my sleep, I had not fallen asleep until half past four, my mind is sorting out the countermeasures for this problem. It does not have more than 100 patches. I will attach them to you one by one to see which ones have caused your failure. Some patches have to be restarted to take effect, it is too slow to come one by one. If there are 10, you can analyze them up to 10 times. Then, if a batch of 10 installs cause failure, how can we determine which one of the 10 is? Right, get a one-click Restore, and restore it after the failure, saving the trouble of reinstalling the system, the patch size can be sorted in the descending order, the installation time of small patches is short, the number of one batch can be set to 20, the installation of large patches is slow, and the number of one batch can be set to 5... when I was so hungry, I began to get up and chew a loaf of bread, so I went to bed.

When I came back from work the next day, I started to look for the patches that caused the failure according to my plan. I first found a software with one click and backed up the system. I want to test the effect after one-click restoration, this guy backed up for 40 minutes. After the backup, I accidentally found that 360 of the patches can be uninstalled. I seem to find a shortcut. Since the patches can be uninstalled, I have the opportunity to roll back to a certain time point, unloading is always faster than loading. Unfortunately, the list in patch management cannot be exported, So I sorted the patch numbers in the lower order from small to small, and saved the images on every 11 screens. I restarted my computer every 11 downloads, check whether Multitouch has taken effect. At first, I was full of confidence. The more I felt guilty, the less luck I had to unload my work for nine times. Although I have always been angry with myself, I have to be confident. Until the last time, I broke down completely. The last batch was finally unloaded and my computer was not restarted. I thought, I may not be able to solve this problem. Even if the patch is removed, the system configuration may not be able to be rolled back. In this case, we can only use the countermeasures we came up with last night.

At that time, it was not too late to restart the computer. As a result, the miracle happened again and Multitouch took effect! This should be the process of returning to life. This was a huge shock, and I could not give up until the last moment! Afterwards, I thought that I should sort the numbers in descending order, so that I could find them soon. In a short time, I found the patch named KB2993651. If the SP1 system does not have any patches, this patch will invalidate the Multitouch and take effect after it is uninstalled, so I have a good reason to believe that this patch is the cause.

Afterwards, my wife asked me how I felt after such a long time. I said, "I don't even think of anyone who developed this stuff. I was killed by Microsoft's patch ." As a result, her words made me smile on the spot. She said, "My mom secretly discussed with me and asked me to buy a new computer for you ." (My mother-in-law has brought a daughter in my house over the past few days. It is estimated that I am suffering from such a late sleep every day)

Today, I tried it on the computer of the organization after the organization. After I uninstalled the patch, it still didn't take effect. I also needed to uninstall a patch named KB2973201 (how can I find it? You can join the group ~), After these two patches are uninstalled, Multitouch can be used. 360 the pop-up window notification is set to close during vulnerability fix, so no prompt will be prompted after startup.

These two patches:

You can use 360 to unload it. So far, this is the perfect end. Let's sum up my feelings: I will sort out some interesting code and place it in group sharing. If you are interested, you can share it with me.

 

MultiTouchVista _-_ second_release _-_ refresh_2 this is a simulated multi-touch program. I want to know how to uninstall it. It's urgent.

As if not, you can disable the touchpad and choose start, control panel, and mouse. In the hardware selection bar, click the touchpad, click "properties", and then select "do not use this device (disable)" In device usage )", however, to resume use, you need to open "Mouse properties" and click the touchpad, and then click "use this device (enable.




I used AS30 to develop multi-touch FLASH and WPF to develop multi-touch. Which one is better? In terms of the development process and user experience?

Of course it's FLASH. I 've been doing this for a long time.