Suggestion: bold Post your code :)
Another suggestion: highlight the part you feel relevant, but post a full reproduction. There may be a mistake at initialization, or even unrelated parts could interfere.
Thanks for this - I'll 'pin' this post to the top :)
Also, as a first step: Try updating your firmware to the latest version. a lot of people follow tutorials to get started with Espruino and those may use the older firmwares that those tutorials link, but issues get found and fixed all the time.
English not your native language? Make use of these online tools:
As Espruino continues along the path of the ubiquitous IoT device explosion, those in the community battle with the decision on how much of their free time to spend assisting fledgling new Original Espruino board purchasers, those with an eager desire to get started. The following are observations I have made since my introduction to Espruino.
There are an exceptional amount of web site tutorials and code examples,
but at times, one may be well, . . . just stuck.
As a consideration:
Try updating your firmware to the latest version
Same symptoms in online vs native WebIDE?
Three WebIDE variants
Struggles with Bluetooth and Windows10
Try connecting with a different device, such as an Android Phone
Reboot Windows10 Cold Start
for step-by-step recovery when device now doesn't reliably connect.
Which Bangle hardware version do I have?
Bangle.js 2 only has a single button, while the original standard Bangle has 3 buttons
Steps to locate Fonts source code (in this case the Font7x11Numeric7Seg font)
Typing 'Fonts' into the Search field at the upper right of most Espruino pages.
Noting that right clicking on almost every listed font takes one to:
Searching that list finds the desired Font7x11Numeric7Seg font.
Steps to locate Espruino source code (in this case the embedded WiFi module source)
Locate and click the Right Facing arrow adjacent to the heading, which takes one to:
Back up the tree in order to locate source code for other functions
Steps to locate Bangle app source code: (in this case the touch event within 'Touch Launcher' app source)
Find the 'GitHub' icon to the left below app title 'Touch Launcher' and R-Click open which will take you to: [Line 230]
and in addition have these excellent pages been reviewed?
The Mozilla Developer Network 'MDN' reference along with w3c.org standards are the places to go to understand the language specifics, while W3Schools has a nice interactive try before coding editor-viewer.
Still at a crossroads? Then by all means create your request:
An effective forum post would include the following:
As a suggestion:
process.envso that viewers can better visualize the environment
Having all of the above will reduce the back-n-forth need to get at the real issue quickly. Having to wait days or weeks for the supporter to gather enough information to get at the source of the issue will greatly reduce the time involvement by building a complete effective foundation first. Correctly placing the initial post will save the moderator valuable time not having to relocate to the appropriate location. 'Other Boards' means just that, non Original Espruino boards.
Create a detailed specific title
There are many community contributors that each has a specialty that is willing to assist. But, just having a title, such as 'Software Issue' most likely won't draw the attention of that specific individual for your particular situation. Wasting the time of the reader opening an un-related post is frustrating for all.
Post the results of
Remember that the viewer is not a mind reader. Having this tidbit will allow that reader to better visualize what the environment is like. That might assist in splitting between a software issue and a hardware one.
Hint: Use the Greater Than symbol
>preceding the first character in a line to highlight gray.
Hint: To highlight a code word as in the above heading, surround the code word with a valid Html element pair < code > process.env < / code > to produce
Additional help in formatting may be found using the 'Formatting help' link, just adjacent to the Cancel button, at the bottom of the edit window.
Post your code
Hint: Using the '</>Code' button just to the left of the 'Preview' button above the edit window will allow the block and error responses to have additional highlighting, making reading much easier. Line numbers allow others to easily reference a specific code entry.
Example code block:
Unrelated error examples:
Please, please don't be overly concerned about the quality of the code posting. Everyone has their own style and others may pick up on a newly discovered technique. Resolving a code block style early will speed up the observation of syntax and programming issues, providing for speedier future development.
Also, don't worry about line numbers if posting a subsequent code snippet. We are not using Basic with a GoTo: statement. ;-)
To get an effective response, please remember to review your post, from the point of view, as will be seen by the reader. No one I know is a mind reader, so having complete and concise content will aid those willing to provide their assistance. Also consider staying the course with follow-up. Those of us that provide that assistance would like to know of your success. So will others that may have the exact same issue as yours.
As a suggestion, post the date. I've seen that up to fifty percent of postings have been resolved as soon as the most recent version of Espruino has been flashed. Having that version and the current date will allow those with a bit of experience to clue in on a possible area of contention.
While waiting a response
Remember to be patient, as most are giving their time freely. Search for online content as others most likely have had the same issue previously. Using the search box on the Espruino website might return links when the exact subject or specific board is known. If not, remember that Google is your friend here. Launch a new Google page instance and type a concise request using the 'site:' keyword qualifier. Google search something like:
Remember to stay active and follow-up timely. A simple thank you goes a long way.
P.S. Thank you for supporting the Espruino community with the purchase of an Authentic Espruino board
Copyright 2019 ©