I was implementing some Drag'N'Drop algoritms using JQuery .draggable & .droppable plugins, when in IE got "unspecified error". Thanks to Microsoft, they finaly got released so called "Development Tools". Debugging my page using that, gave me exception inside jQuery's code. It was the line saying "d=b.getboundingclientrect()".
It got me a while to understand why that happens, and the answer is:
jQuery's event handles/listerners are not unbinded automatically from the elements you remove from the DOM... they keep firing. So every time you use something like $('...').droppable(...
you should also do $('...').droppable('destroy'), if you remove that $('...') from the DOM. I did.
Conclusion: $('...').droppable('destroy');
Monday, June 21, 2010
Friday, June 18, 2010
VMware Workstation cannot connect to the virtual machine.
My VM was up for ~2 last weeks and it seemt to get tired, so it hung up today. Tried to restart VM, close VM, none worked.
- Closing VMWare workstation gave me error that VM is busy, so please wait for it to finish and then close ...
- Restarting VM was disabled, due to tireness I guess
- Windows's 7 resource manager said vmware.exe makes 0b/s writes and 0b/s reads to/from hard-drive
So it was obvious to me that the only solution is to find vmware.exe in processes list and kill it.
Runing it again and trying to play virtual machine gave me another riddle to solve:
"VMware Workstation cannot connect to the virtual machine. Make sure you have rights to run the program and to access all directories it uses and rights to access all directories for temporary files."
I'll skip all the sarcasm on the usefullness of this advise and come right to the solution:
"Restart the Host computer" and it works nice.
Strange , cuz I remember the other time, that vmware.exe was restarted same gentle way, there were no problems appeared.
It's also fair to mention that before restarting the host computer I tried google... found a lot of hints how to fix that problem... Good for me I did not start trying any of them.
Conclusion: killing vm from the processes list is not always good idea
Santé!
- Closing VMWare workstation gave me error that VM is busy, so please wait for it to finish and then close ...
- Restarting VM was disabled, due to tireness I guess
- Windows's 7 resource manager said vmware.exe makes 0b/s writes and 0b/s reads to/from hard-drive
So it was obvious to me that the only solution is to find vmware.exe in processes list and kill it.
Runing it again and trying to play virtual machine gave me another riddle to solve:
"VMware Workstation cannot connect to the virtual machine. Make sure you have rights to run the program and to access all directories it uses and rights to access all directories for temporary files."
I'll skip all the sarcasm on the usefullness of this advise and come right to the solution:
"Restart the Host computer" and it works nice.
Strange , cuz I remember the other time, that vmware.exe was restarted same gentle way, there were no problems appeared.
It's also fair to mention that before restarting the host computer I tried google... found a lot of hints how to fix that problem... Good for me I did not start trying any of them.
Conclusion: killing vm from the processes list is not always good idea
Santé!
Just another "another blog"
There won't be "In this blog i will..." in this message, cuz I will not.
I'm a 30 year male, specializing in "computer science".
The idea to open the blog came to me, when I realized that it is impossible to find some good answers for some not very common questions, which popup during my work. So "Just another blog" is intendet to be one of those useless places mis-indexed by searching engines.
Hopefully, one day, anyone beats the system and finds something usefull here, which i doubt.
Adiós
I'm a 30 year male, specializing in "computer science".
The idea to open the blog came to me, when I realized that it is impossible to find some good answers for some not very common questions, which popup during my work. So "Just another blog" is intendet to be one of those useless places mis-indexed by searching engines.
Hopefully, one day, anyone beats the system and finds something usefull here, which i doubt.
Adiós
Subscribe to:
Posts (Atom)