Author Topic: Doors CSE release candidate 2 trouble in paradise  (Read 2097 times)

0 Members and 1 Guest are viewing this topic.

Offline dreamdragon

  • LV3 Member (Next: 100)
  • ***
  • Posts: 72
  • Rating: +6/-19
  • Dragon born and Dragon raised.
    • View Profile
Doors CSE release candidate 2 trouble in paradise
« on: July 15, 2014, 01:13:25 pm »
So a few nights ago i was on the doors app release 2...
it has never done this and i do have to say i am really pissed off. :mad: :banghead:
It glitched (no surprise) but what got me going was this:
Almost all of my programs were erased, and every single grouped item vanished. In a fit of rage I deleted the candidate and i am left to sadly consider that maybe doors needs alot more work [/color](yes even the 8.0 version of doors) so it can become more stable, and more dependable. okay we may run our prototype programs whatever on a calculator emulator but in reality I dont think emulators should be used. we should instead test-run these new programs on a [/font]REAL calculator before we release it to everyone just to be safe, and keep using the program contained for a month or so to tell if there are stability issues in it.
I rest my case.

Offline tifreak

  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2708
  • Rating: +82/-3
  • My Kung Fu IS strong...
    • View Profile
    • TI-Freakware
Re: Doors CSE release candidate 2 trouble in paradise
« Reply #1 on: July 15, 2014, 01:19:52 pm »
Well, this is the first we've seen of this as an issue. What were you doing with Doors at the time of the 'glitch' and what programs did you have on it/have been using?

Also, if you want this kind of thing fixed, you should be posting bug reports to Cemetech's DCSE topic, so Kerm can see it and try to fix it.
Projects: AOD Series: 75% | FFME: 80% | Pokemon: 18% | RPGSK: 60% | Star Trek: 70% | Star Trek 83+: 40% | TI-City: 5%

Offline DJ Omnimaga

  • Former TI programmer
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55838
  • Rating: +3151/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • DJ Omnimaga Music
Re: Doors CSE release candidate 2 trouble in paradise
« Reply #2 on: July 15, 2014, 02:03:19 pm »
This flamebait bug report would be more credible with fewer post colors and describing exactly how the crash happened. For example, if you did a mistake when using the third-party BASIC libraries, it is not a bug, but rather error on user's end. Also, I have never ran into any similar problem with Doors CSE 8.1, even the RC's. Whatever crash I got was caused by buggy ASM programs or misuse of xLIBC and even then, keeping all my programs archived minimized data loss.


EDIT: Besides, Doors CSE 8.1 RC2 is outdated, since 8.1 came out days ago.
« Last Edit: July 15, 2014, 02:07:44 pm by DJ Omnimaga »
In case you are wondering where I went, I left Omni back in 2015 to form CodeWalrus due to various reasons explained back then, but I stopped calc dev in 2016 and am now mostly active on the CW Discord server at https://discord.gg/cuZcfcF



Official Website |T-Shirt store | Reverbnation | Facebook | Youtube | Twitter | Spotify

Offline Keoni29

  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2466
  • Rating: +291/-16
    • View Profile
    • My electronics projects at 8times8
Re: Doors CSE release candidate 2 trouble in paradise
« Reply #3 on: July 15, 2014, 02:10:44 pm »
It's a good idea to make backups of your device regularly when you are developing software. You can just fall back on a backup in case of a fatal reset.
If you like my work: why not give me an internet?








Offline Streetwalrus

  • LV12 Extreme Poster (Next: 5000)
  • ************
  • Posts: 3821
  • Rating: +80/-8
    • View Profile
Re: Doors CSE release candidate 2 trouble in paradise
« Reply #4 on: July 15, 2014, 02:35:59 pm »
It's a good idea to make backups of your device regularly when you are developing software. You can just fall back on a backup in case of a fatal reset.
Indeed, no matter what happens, data loss is your responsibility for not making backups as a safety measure.

Offline DJ Omnimaga

  • Former TI programmer
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55838
  • Rating: +3151/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • DJ Omnimaga Music
Re: Doors CSE release candidate 2 trouble in paradise
« Reply #5 on: July 15, 2014, 03:30:12 pm »
Yeah I agree about the backup part. With every ASM lib for BASIC programmer, as well as any language other than TI-BASIC, if you do a mistake, it can freeze your calc, reset the RAM (although not as frequent with Doors CSE installed) or render it unstable. Many Axe Parser users lost countless amounts of data for similar reasons, and it's the price to pay when coding on-calc.

Of course, if someone is convinced there is an actual bug in Doors CSE itself, then he can post it in the Cemetech thread as Tifreak said, but in the case of the original post above, the bug report needs a lot of improvements in order to be taken seriously.
« Last Edit: July 15, 2014, 07:33:22 pm by DJ Omnimaga »
In case you are wondering where I went, I left Omni back in 2015 to form CodeWalrus due to various reasons explained back then, but I stopped calc dev in 2016 and am now mostly active on the CW Discord server at https://discord.gg/cuZcfcF



Official Website |T-Shirt store | Reverbnation | Facebook | Youtube | Twitter | Spotify

Offline TIfanx1999

  • ಠ_ಠ ( ͡° ͜ʖ ͡°)
  • CoT Emeritus
  • LV13 Extreme Addict (Next: 9001)
  • *
  • Posts: 6173
  • Rating: +191/-9
    • View Profile
Re: Doors CSE release candidate 2 trouble in paradise
« Reply #6 on: July 16, 2014, 07:40:50 am »
Well, this is the first we've seen of this as an issue. What were you doing with Doors at the time of the 'glitch' and what programs did you have on it/have been using?

Also, if you want this kind of thing fixed, you should be posting bug reports to Cemetech's DCSE topic, so Kerm can see it and try to fix it.
^Pretty much this exactly. Posting a rant about it here does nothing. Also, common sense says back your stuff up. Especially if you are running a test build of something that may be unstable.