|
|
|
Q: Is the RapidQ language easy to learn? A: Very easy! All you need to do is... look at some coding examples to see that it's not cryptic like other languages. I think that's why it's rated as number one on so many websites. |
|
Q: When I install RapidQ... will it mess up my computer? A: No! It does not change any settings on your computer and it only adds one entry into your computers' Registry file. That entry simply tells RapidQ where to open it's own window, every time you use it. |
|
Q: When I install RapidQ... does it take up alot of disk space? A: Again... No! It's very small in size (especially when you compare it other programming languages). |
|
Q: What is the best way to install RapidQ? A: It comes in a zip file named "rqbeta.zip", which means... you'll need a program (such as WinZip or WinRar) to "unzip" it. Create a folder on your hard drive (you can name the folder RapidQ, if you'd like) and then simply unzip it to that folder. You should also obtain a copy of the latest version of the Libraries and install them too. Oh yea... almost forgot. You'll need to create desktop shortcut to "rapidq.exe" too. |
|
Q: If RapidQ is no longer under development... is it worth my time and effort? A: A definitive... Yes! Although the compiler can no longer be enhanced, the libraries can be. Also... users are constantly creating workarounds to the compilers' limitations (that's why it's a good idea to join the RapidQ group on Yahoo). It's unbelieveable that... what seems like a dead program... is actually very much alive and well. |
|
Q: If the compiler has limitations... does that mean my programs will have limitations too? A: Nope! You can create programs ranging from very simple to extremely elaborate. It totally in your "hands" (or should I say... "mind") as to what you want to create. |
|
Q: I've compiled and ran my program but I got an Exception error message. Why? A: There could be any number of reasons for that error message. But the core reason is due to... a coding error. For instance... you might be trying to do something with a component that's out of it's "Property" limitations. Another instance might be... you have an OnResize event subroutine that's trying to resize a component that is not visible yet (solution: use if/then to determine if the form is showing yet). Check your coding of ALL components and you'll probably find the reason for the error message. |
|
Q: I've compiled and ran my program but when I close it... the icon on the taskbar remains. Why? A: Try setting up an OnClose event subroutine for the form. You'll need to add these 3 items to your code (in the proper places)...
|
|
Q: I've compiled and ran my program but when I click on a menu item... the form disappears and the icon on the taskbar remains. Why? A: I've had this happen to me because I made use of the SetFocus (API function), within a OnResize event subroutine, on a component that was not visible. I corrected it by waiting till the component was visible and THEN used the SetFocus. |