![]() Adding features to our bouncing balls demo.Making decisions in your code - conditionals.Basic math in JavaScript - numbers and operators.Storing the information you need - Variables. ![]() What went wrong? Troubleshooting JavaScript.JavaScript - Dynamic client-side scripting.Typesetting a community school homepage.HTML table advanced features and accessibility.From object to iframe - other embedding technologies.Which gives me another idea for the future. Oh and I did a quick check on vertical sliders, it seems the standard method is to use a transform:rotate in CSS, then you can use the built-in methods. Once we get through the holiday season I'll have more time and will try to throw together a mock-up of what I'm thinking. again instead of scrolling down, what about having a few of the important ones at the bottom, then using CSS to bring up a small window when you tap a button? Ideally you would want to eliminate all scrolling on every page since scrolling is a real pain on mobile, but that'll take quite a bit of rearranging to accomplish. I was also thinking about the function group at the bottom of the throttle. Since the space is already being used, maybe it would make more sense to create more tabs at the top for direct access to specific features? For example, if you were actually using this as a throttle during operations you would need instant access to the turnouts rather than switching tabs and then scrolling down. Part of the problem is likely that I simply don't know where to find everything, and having everything as parts of two separate tabs kinda makes it a bit more confusing. Otherwise the dev code branch seems to be working great! And while it is nice that power is automatically turned on to the track when you connect to the web interface, it would also be helpful to still have an option to turn the power off again. I realize the web code is still in progress so I would guess creating a list of locos and not having to re-type them every time is one of those things still to come. Also if you hold your finger on the throttle control, chrome is now popping up a right-click menu and you have to stop and clear that. When trying to run it from a cell phone it's impossible to slowly run up the speed. The throttle itself could stand to be a bit bigger. This seems to follow the DCC++ command page, which states that throttle settings should be in the range of 0-126. First off, the web page allows throttle settings up to 128, however if you set it to 127 or 128 the loco stops. Can you please describe how?Īfter playing with the new web page code this week I have some issues I wanted to point out. Actually I have no idea how to resolve this problem. The only library installed for SH1306 is the version " esp8266-oled-ssd1306/releases/tag/4.0.0". The new one came with a HELTEC OLED display, but unfortunately I'm now running into the same trap as already posted: "invalid conversion from 'const char*' to 'const uint8_t* '. The "old" board seems to have a poor voltage regulator on. With a new module no BrownOut detection is triggered any more. Don't need the second PROG track output in this setup. Preferraby using ESP8266 instead of ESP32, because its smaller. My personal idea: I would like to build the DCC++ station into the loco and supply the DCC signal directly into the loco-decoder (don't want to scap the expensive, high performance ESU sound decoders though). Presented it last weekend at the RocRail users meeting resulting in a discussion on how to benefit from the WiFi interface. All questions resolved now and the ESP32 is running fine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |