• Re: Possible bug in msg_gettxt/msg_gethdr?

    From xqtr@21:1/111 to g00r00 on Mon Mar 9 12:23:36 2020
    Awesome find!
    I was really struggling to figure out why it was messing up for you but that absolutely explains it. The way it is set up you do have to get
    the header before the text!

    I thought that because you call the function like msg_gettxt(msg) it gets the data using the msg object and didn't require to read the header first.

    I feel like an idiot :) I was frustrated for many hours, many times trying to find what the hell i was doing wrong and it was in front of me all the time :)

    :: XQTR :: Another Droid BBS :: andr01d.zapto.org:9999 :: xqtr@gmx.com

    --- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
    * Origin: Another Droid BBS # andr01d.zapto.org:9999 (21:1/111)
  • From g00r00@21:1/108 to xqtr on Mon Mar 9 19:58:01 2020
    I thought that because you call the function like msg_gettxt(msg) it
    gets the data using the msg object and didn't require to read the header first.

    I didn't really intend for it to work that way, but that is how it does work after looking at the code.

    I feel like an idiot :) I was frustrated for many hours, many times
    trying to find what the hell i was doing wrong and it was in front of me all the time :)

    Its totally my fault, sorry.. I should have realized that limitation and documented it.

    I have updated the msgread.mpy example in the new installation to mention that gethdr has to be called first.

    --- Mystic BBS v1.12 A46 2020/03/09 (Windows/64)
    * Origin: Sector 7 (21:1/108)