Larger update of #GCodeSimulator & Printer just published.
Also please follow the #GCodeSimulator & Printer Community für news and discussions regarding GCode Simulator. (Don’t want to spam this community with too much Gcode Simulator stuff)
Originally shared by Mathias Dietz
New version of GCode Simulator (Free) and GCode Simulator & Printer is out.
Changes in V1.28
Introduced new settings panel to modify settings easily and provide some new options :
-Do not load gcode simulator logo at startup
-Remember Baud rate & Connection type
-Disable Bluetooth discovery
-Configure temperature presets
-Configure Temperature watch interval
-Configure speed for X/Y/Z manual movement
-Framerate, wakelock, … and more
New feature to home all Axis at ones (Long press on “Z-Home” )
Make Bluetooth connect async (does not block UI for a few seconds)
Fixed many memory allocation problems (garbage collector)
Improved behaviour on some devices (activity got stopped to early)
more fixes …
Please note: I will take some hours until the update is pushed to all Google servers.
If you could actually use KitKat/JellyBean native graphic constructs, this program would be so much more enticing. I bought it, I just don’t happen to use it often because of that.
@ThantiK Thanks for the feedback. I would like to understand this more. The model details text should be a native android textview (no doubt), but other than that what should be changed ? GCode rendering cannot be native and print panel + option panel are already native.
@Mano_Biletsky_Open_M
I guess it might at least stutter. Currently the printing app must be in the foreground to print, but I’m about to move the print control into a background service (like music player) to handle such cases.
@Mathias_Dietz , you follow NONE of the Android design guidelines. You use absolutely NO included Android assets. The app has black-on-black text all over the place; look at the “motors” button for example. It’s practically unreadable. It’s a great app, and I don’t want to discourage, but it looks atrocious.
First things first, you need to implement an action bar, as well as a left side slide-out, which is the standard convention in Android apps now.
There’s no need to worry about compatibility with Android 2.3 either; nothing that low is going to have USB-OTG capability, so just work on devices that are 4.1 and above.
@ThantiK
hm, I see. ActionBar is understood. The black-on-black example is obvious, I planned to remove the text here anyhow as the Android guidelines make use of plain icons without any text.
But there is no android guideline for how to build a print panel and it already uses native buttons,layouts,… I don’t see whats wrong with it (maybe icons are too colorful).
And the settings panel is 100% native.
Another thing, is maybe a theme? – Black backgrounds are so AOL-era. None of the front ends on the PC have black backgrounds. Maybe a dark/medium grey?
Personally I like the black. Another color like grey would probably cause trouble with readability. Or all the colored buttons should change to the same color.
