Our company have a game written on Flex. As the new member of company, I'm is trying to begin with Flex SDK game development, but struggled to find a good book or tutorial about this subject. Suggest some tutorials/books for me, please.
Okay, you say that "Our company have a game written on Flex". This is hard to understand. This would probably be more helpful to the Native English speakers here:
. Saying "Our Company" is suggesting that you either own the company or that there are other people involved. Also, saying have is using the wrong tense. Saying have is used in the past tense (I used to have a Car). It would be better expressed as "has" because has means your company presently has it, which is what you are trying to convey (My company currently has a game wrote with flex). Another place where the tense wasn't correct was where you say your company has a game written on flex. What you were trying to convey was that your company wrote a game in adobe flex. Written is used in only when paired with certain terms (“have”, “has”, “would” or “will”). Now, you may say that there is a have there. However, that have is "attached" to the game noun, meaning that it's not "paired" with written. Wrote is used in past tense (My company wrote a game with adobe flex.).
The company I work at has a game wrote on Adobe Flex
There are some more errors, however they are too small to matter.
Believe me, I'm only trying to help. Learning English correctly will set you up for a great future, and I understand how complex the language is. If you really want to understand the language correctly, I recommend learning the "four levels of grammar". They'll help you understand what words to use when you want to convey something, and will help you understand what a sentence is actually about.
On the Adobe Flex problem, I don't program in flex. I suggest looking at your code. When I was first learning about handling mouse clicks (In C++, which is arguably more complicated than flex) I kept on using the wrong parameters (MouseMove vs. MouseButton) and it ended up in unpredictable code.