Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
hyperPad

hyperPad Forum

  1. Home
  2. Comments & Feedback
  3. Multithreading

Multithreading

Scheduled Pinned Locked Moved Comments & Feedback
2 Posts 2 Posters 372 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T Offline
    T Offline
    Thecheater887
    wrote on last edited by Thecheater887
    #1

    I'm well aware of the @administrators stance on this, but....

    Would it be possible to use some sort of async, await, or multithreading? Optionally, of course.

    I just feel like putting the bulk of a pathfinding AI on a separate thread, or downloading data asynchronously would be a LOT more battery and frame efficient than the current one-thread style.

    Potentially to be added with the code blocks ("Functions") update, allow it to run async, and allow us to await completion.

    I know it's another radioactive block added onto an already unstable house of cards, but with the demands of games and gamers, is it really going to stay an option if we as developers want to stay serious?

    D 1 Reply Last reply
    0
    • T Thecheater887

      I'm well aware of the @administrators stance on this, but....

      Would it be possible to use some sort of async, await, or multithreading? Optionally, of course.

      I just feel like putting the bulk of a pathfinding AI on a separate thread, or downloading data asynchronously would be a LOT more battery and frame efficient than the current one-thread style.

      Potentially to be added with the code blocks ("Functions") update, allow it to run async, and allow us to await completion.

      I know it's another radioactive block added onto an already unstable house of cards, but with the demands of games and gamers, is it really going to stay an option if we as developers want to stay serious?

      D Offline
      D Offline
      Deeeds
      wrote on last edited by
      #2

      @Thecheater887 Here's a long read that's well worth your time: https://developer.apple.com/library/content/documentation/General/Conceptual/ConcurrencyProgrammingGuide/OperationQueues/OperationQueues.html

      1 Reply Last reply
      1

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Search