Coding app beta test » Discussions

New features and ideas

  • Member
    July 22, 2019
    Is there something missing from the app that you would like to see? Perhaps a feature that you’ve been looking for but haven’t managed to find? Play an active role in our development and let us know here!
  • August 9, 2019
    I was thinking of some kind of read/write script functionality, where inputs to joysticks, sliders, and buttons are recorded for a certain amounts of time, then can be played in a loop.
  • August 13, 2019

    I wonder about any way to build a scenario like:

    Having 2 WeDo distance sensors connected.

    Starting a timer and counting the seconds when one sensor is detecting an object (like distance lower than {variable}). Stopping timer and displaying the counted seconds, when the second sensor is detecting an object.

    Any idea about how to implement?
  • August 14, 2019
    M. Christiansen

    Ive made something like a timer. I made a loop that would add to a variable every 0.25 seconds.
  • October 12, 2019
    A possible functionality that I think might be nice to add is a camera functionality to the app, for recording videos while controlling your Mocs.

    This might be a good idea for builders where there phone is their primary video camera and post a lot of videos on social media and their phones.

    Either a camera function be add to the app, or if the app could run while using other apps instead.
  • Member
    April 3, 2020
    it should be interesting to add a Trigger section.

    Indeed, when initializing your app on a start event, triggering an event can avoid code duplicated by "simulating" the touch start event.

    For example:
    I would like to initialise all switches of my train track when I start the app.
    Now, I have to initialise all button and motors on a start event but also on each touch start of my buttons. With a trigger, I will just have to trigger the touch start event to all my buttons on a start event.
  • Member
    December 21, 2020
    Hi it would nice if with the the smart motor, we would be able to see the actual speed, and work with it as a value (similarly to position). Another interesting function in this category would be "hold" (see in pybricks e. g.), where you can tell the motor to keep a certain position, and always return to it (just like a servo, but we could use this to make a vehicle stop very quckly). One step further, there could be motor speed function, which would to keep a certain speed by constantly adjusting the necessary torque. If the smart motors could combine the benefits of both linear and servo motors, that would be amazing.

    I must note here, that I am not aware of what the limitations of the firmware(s) are, I only know that the system is physicly capable of such things.