Memory Read/Write error message

  • detroit671
    8th May 2014 Member 0 Permalink

    While playing TPT, I got a "Memory Read/Write Error" while using the Property Edit tool. It said to report it to the website. What do I do now??

  • jacob1
    8th May 2014 Developer 0 Permalink
    Did you select the property edit tool from the element search? If so, that's a known bug :)

    If it's something else though you should give more details. That's the only PROP crash I know of.
  • greymatter
    8th May 2014 Member 0 Permalink
    @jacob1 (View Post)
    Yep. Doing that gave me a runtime error.
  • Squirtle
    9th May 2014 Member 0 Permalink
    Same, it gave me the BSOD... I didn't know that TPT had a BSOD... lol.
  • KydonShadow
    9th May 2014 Member 0 Permalink

    My prop tool is pretty effectively broken. When I click PROP in the element bar, it opens the UI immediately, but then wont open again whenever I click on anything else...

  • jacksonmj
    9th May 2014 Developer 0 Permalink

    @KydonShadow (View Post)

    That's what it's supposed to do, as of v89.2 (since February, according to http://tpt.io/.247439). Whenever you want to reopen the PROP tool UI, click on PROP again in the element bar.

     

    This is so you can use PROP like any other tool, without the UI popping up and requiring you to re-enter the value every time you click to apply it to something, like it did in older versions. In addition to the UI opening change, PROP no longer defaults to flood fill. Instead, it behaves like any other tool. Ctrl+shift = flood fill, ctrl = box, shift = line, etc.

     

    @greymatter (View Post)

    If you're referring to selecting the property edit tool from the element search, then yes, it will. That's why it's called a known bug.

    Edited 3 times by jacksonmj. Last: 9th May 2014
  • h4zardz1
    9th May 2014 Member 0 Permalink
    okay, but then try to spark and run this.
  • wolfy1339
    9th May 2014 Member 0 Permalink

    @h4zardz1 (View Post)

     Ya, i get it to