![]() This was due to a font-size adjustment in Windows. 32-bit programs work on 64-bit processors, just not as well. Anyway, I don't know how to compile 64-bit Java. Well then you shouldn't have got a Mac (jkjk, well kinda). Why is there only a 32-bit version of ZomgTimer? If it says 圆4, you have a 64-bit machine.īut. If it says x86, you have a 32-bit machine. Here it will give you "x_-based PC." The blanks will either be 86 or 64. When it does, look for "System Type" in the information that appears. Go to Start > Program Files > Accessories > System Tools > System Information How do I know if my computer is 32-bit or 64-bit? - Note: this is no longer necessary. I'll be putting out info to work around any necessary things that I can't include in it. ZomgTimer is pretty much a finished product. It's the better of the two as it has more options, better UI, slight accuracy improvement and it's more easily upgradeable for me. ![]() Please report any issues you may find.EonTimer is entirely Windows based. Add base documentation for getting started and how to contribute to EonTimer.Add unit tests to provide code coverage and hopefully increase stability of the program.My goals for the next release (after taking a short, much needed break) are: Fixed an issue where the last timer action would occasionally not fire. ![]() Fixed an issue where the first time running the timer would cause the first beep to lag due to a buffering issue.Switched to JavaFX MediaPlayer from Java's base Sound API for a consistent JavaFX platform.Added a "Set Target Frame" button specifically for setting the "Target Frame" instead of tying that functionality into the "Update" button.Timer will now display how much time has elapsed until the "Target Frame" is set so that a second timer application is no longer required to track elapsed time."Calibration" field remains so that manually calibrations are no longer required.Implemented the Generation 3 Variable Frame Timer with new functionality not present in ToastPlusOne's EonTimer implementation:.This should make it easier for anyone to contribute to EonTimer if they desire. Migrated GUI source from hard-coded source to FXML files.This should make it easier to manage the code base going forward with hopefully the realization of performance benefits while running the timer Switched from spinning up a new Thread for running the timer to a hybrid of using reactive programming and Kotlin coroutines.Switching from Java to Kotlin to reduce overall code base and to increase code expression.Using Spring Boot internally without starting a web server for the added benefit of autoconfiguration and dependency injection.Switched to the application plugin for Gradle to build EonTimer instead of building an UberJAR. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |