You may also want to adjust default application settings. However, our defaults were carefully chosen to be satisfying for most typical cases.
Answer: Most likely your Delphi / C++ Builder installation was somehow corrupted and EurekaLog installer can not find your IDE in the Windows registry.
You should be able to see your IDE during EurekaLog's installation
EurekaLog installer looks for path values in the registry. For example: HKEY_LOCAL_MACHINE\SOFTWARE\Embarcadero\BDS\8.0\RootDir=C:\Program Files (x86)\Embarcadero\RAD Studio\8.0\ (don't forget about Wow6432Node node on x86-64 machines). Additionally, a corresponding personality (Delphi or C++ Builder) must be registered in \Personalities subkey of your IDE.
Try to reinstall or repair your Delphi installation. An easiest way to fix this is to run "Repair" of your IDE installer.
See this article for more information.
Answer: EurekaLog integrates itself with Delphi's and C++ Builder's IDE.
EurekaLog collects information about environment and builds bug reports on your request, when exception is handled or when application exits. EurekaLog uses injected data to build human-readable call stacks to show you address, module name, unit name, class name, routine name and line number. All this behaviour is FULLY customizable.
Answer: That depends on type of your application. EurekaLog can display error dialog (for GUI-based applications), EurekaLog can write text into console (for console-based applications), EurekaLog can silently log error to system log (for non-visual applications like Win32 services or web-server applications), EurekaLog can produce error HTML page (for web-applications). This behaviour can be fully customized. You can also use your own dialogs.
EurekaLog can also store bug report into file, send it to you (a developer) via e-mail, HTTP or FTP upload, and submit to bug tracker software.
Answer: Yes, it does. EurekaLog also have predefined templates of settings for DLLs and BPLs. See also our guide on DLLs.
Answer: Yes, it does. There is "Catch SafeCall exceptions" option, which is designed to catch exceptions in any COM object.
Answer: Probably no. We have profiles (templates, typical settings) for all common project types. And even if there is no template for your project type - you can just set up options manually. If there is no ready-to-use hook for your project type - you need to invoke EurekaLog from your global exception handler. The worst-case scenario is when you are building non-standard project type which do not have any "OnException"-like events or handlers. You can contact our support to find a solution.
Answer: Yes, EurekaLog is fully compatible with .exe compression/protection software, so you can use those tools without any restrictions. EurekaLog have wide range of customization options.
There are options to disable hooks installation (hooks installation can be detected as application's crack).
There are options to use hi-level or low-level hooks (trade detalization for better compatibility).
Answer: It is *.EL for plain-text reports, *.ELP for packed reports (can include screenshot and additional files), *.ELX for XML reports. See also.
Answer: There are no special limits.
Answer: Yes, there is no problem. You can disable visual feedback (error dialogs, send progress, etc.), you can set up logging, you can set up automatic bug report sending, you can set up auto-restart options.
Answer: Yes, absolutely. See this article for more info.
Answer: No problem. We support any localization tool or even no using localization tool at all. There are wide translation options available. You can localize resourcestrings, you can use Translate-like function (GetText-style) or you can just set up translated strings in options.
Answer: Yes, you can even force right-to-left text by switching "Right-To-Left" value under "Dialogs (common)" section from 0 to 1. See localization options.
Answer: RC means Release Candidate. When client founds an issue in EL, we develop a fix ASAP, mark it as XXX RC YYY and publish it on our site. So the client can download it and test his issue in new version. When we get a bunch of fixes and there are no known issues and there is enough passed time since last fix (so any who wanted to test - already do it) - then we just rename XXX RC YYY to just XXX and publish it as official release. So, generally RC builds are quite stable and can be used in production.
Beta versions are similar to RC, but we are not sure about stability of applied fixes. We do not recommend to use beta builds in production.
Alpha versions are unstable builds, using for prototyping and testing.
Answer: You should log in to your account on our web-site.
Once you're logged in to your control panel - you should see available to you EurekaLog versions. There will be a link to download the last stable and last test version of EurekaLog (if any present).
Answer: Your log in is your e-mail address (which you've used to purchase EurekaLog). Your password is sent to you in the confirmation e-mail immediately after purchase:
We have created a new account for you on our web site.
Your credentials are:
You can log into your account here: https://www.eurekalog.com/login.php
Please, save password information in a safe place, and delete this e-mail.
Note: your license serial number is not your password!
Note: you can log in here: https://www.eurekalog.com/login.php
Answer: Yes, sure - we love to hear feedback! You can ask us to add specific feature and additional information. We will add most popular and frequently asked features into next releases of EurekaLog. Unfortunately, not all features can be added. However, EurekaLog allows easy customization. There are many events handlers. So often you can add your desired features by yourself even without having full source code!
Oh, and we have OnCustomDataRequest event, which you can use to insert arbitrary information into bug reports. And you can also add additional files, of course.