Author Topic: Crash 4.1.1  (Read 6589 times)

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: Crash 4.1.1
« Reply #15 on: June 03, 2015, 01:10:16 PM »
That must be the new user detection code.  It has a list of people who said they like Vixen and induces random crashes...lol.

Offline Phrog30

  • Hero Member
  • *****
  • Posts: 1234
    • View Profile
Re: Crash 4.1.1
« Reply #16 on: June 03, 2015, 02:46:26 PM »
Here's the video. All clicks were with the left mouse button. Sean, I used your setup.

http://stevesimages.com/xl4/xl4-click-crash.mp4

I know.. there's absolutely no valid reason to click on an empty panel because there's nothing you can do there.
No valid reason? Maybe you've been inverted for too long.

Offline flyinverted

  • Administrator
  • Hero Member
  • *****
  • Posts: 756
    • View Profile
Re: Crash 4.1.1
« Reply #17 on: June 03, 2015, 03:54:42 PM »
Do tell Phrog, why would you need to click on the sequencer grid before you have any timing marks or effects?
Maybe I'm missing something.
Steve Giron
Maricopa County, AZ
xLights user with a boat-load of channels.

Do not ask to know all the answers, but ask to understand the question.

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: Crash 4.1.1
« Reply #18 on: June 03, 2015, 04:06:47 PM »
It does seem like more of a test what can break action which is great if that's what your trying to do.  Maybe we should send development builds to Phrog before releases. :)

Offline flyinverted

  • Administrator
  • Hero Member
  • *****
  • Posts: 756
    • View Profile
Re: Crash 4.1.1
« Reply #19 on: June 03, 2015, 04:16:44 PM »
You can click on the wave-form to add timing marks, and that is on the sequencer tab, but above the grid.
Steve Giron
Maricopa County, AZ
xLights user with a boat-load of channels.

Do not ask to know all the answers, but ask to understand the question.

Offline Phrog30

  • Hero Member
  • *****
  • Posts: 1234
    • View Profile
Re: Crash 4.1.1
« Reply #20 on: June 03, 2015, 05:01:09 PM »
Do tell Phrog, why would you need to click on the sequencer grid before you have any timing marks or effects?
Maybe I'm missing something.
Simple, a new person, just creating a sequence. You really want that to be their first experience?

I tend to think about those things. You don't see the importance, I do.

James

Offline Phrog30

  • Hero Member
  • *****
  • Posts: 1234
    • View Profile
Re: Crash 4.1.1
« Reply #21 on: June 03, 2015, 05:02:22 PM »
It does seem like more of a test what can break action which is great if that's what your trying to do.  Maybe we should send development builds to Phrog before releases. :)
Absolutely! I told you several days again, I can't write high level code, but I sure can break it.

Offline gerry

  • Hero Member
  • *****
  • Posts: 695
    • View Profile
Re: Crash 4.1.1
« Reply #22 on: June 03, 2015, 05:09:39 PM »
In defence of Phrog  :), I have quite often done the same , but did not get any crashes.

I am newish to xlights and come from an LSP background , where when u create a new sequence, the default option is to to create timing marks (you can pick the frequency or deliberately say None) and the default option is to copy all your models in (you can nominate from which seq ) - most people use the previous seq.

When you open  LSP and select open a seq , it shows u a list of recently used sequences as part of the dialogue with the last one on the top .

So when the sequencer tab is then presented (very similar to the xlights view now), you are ready to go.

I am on my 3rd seq in xlights now (and have been doing odd imports ) and I mostly get caught out either not having timing marks defined or not having models defined on the sequencer tab, but know now after a few seconds what I have missed.
(mostly when I see everything greyed out)

Just a question of getting used to it, but I can see how anyone would click on the seq tab to see if it would make a diff to the greyed out icons - I have done that previously.
 
 
Gerry

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: Crash 4.1.1
« Reply #23 on: June 03, 2015, 06:16:29 PM »
Well I was just able to watch this video.  I see it crashed in CheckForPartialCell which means you can blame me since I just added that function last 3 days.  It uses some variables that apparently aren't always set so I'm trying to figure out all the protections to put around the call so we only call it when everything is valid.

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: Crash 4.1.1
« Reply #24 on: June 03, 2015, 06:28:54 PM »
By the way the comments to Phrog were meant in good fun.  I was laughing to myself thinking wow he's taking this beta testing seriously.

Offline Phrog30

  • Hero Member
  • *****
  • Posts: 1234
    • View Profile
Re: Crash 4.1.1
« Reply #25 on: June 03, 2015, 06:28:57 PM »
Nah, no blame. It's the nature of the beast. 8)

Offline Phrog30

  • Hero Member
  • *****
  • Posts: 1234
    • View Profile
Re: Crash 4.1.1
« Reply #26 on: June 03, 2015, 06:29:54 PM »
By the way the comments to Phrog were meant in good fun.  I was laughing to myself thinking wow he's taking this beta testing seriously.
Didn't take it wrong. I do take things serious though. That's a good and bad thing.

Offline gerry

  • Hero Member
  • *****
  • Posts: 695
    • View Profile
Re: Crash 4.1.1
« Reply #27 on: June 04, 2015, 12:28:28 AM »
Heh Gilrock,

Even I am taking this seriously :) .
Fully plan to use what I am doing for my show this year. Best time to learn .
And if it so happens to test the Beta that's great . If no one works on it now , then the bugs will just remain dormant !

Plus if u have a new user trying to use it , more idiotic things will be done that normally would not get exercised and tested.
 
Gerry

Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: Crash 4.1.1
« Reply #28 on: June 04, 2015, 07:22:14 AM »
Yeah but I joked that he was taking the beta testing seriously.  What that means is you do a bunch of outrageous things a normal user wouldn't do to try to break the code.   If your sequencing for your actual show great...but that's not serious beta testing. :)

Offline mararunr

  • Sr. Member
  • ****
  • Posts: 271
    • View Profile
    • Bentonville Heart Lites
Re: Crash 4.1.1
« Reply #29 on: June 04, 2015, 07:33:49 AM »
Yeah but I joked that he was taking the beta testing seriously.  What that means is you do a bunch of outrageous things a normal user wouldn't do to try to break the code.   If your sequencing for your actual show great...but that's not serious beta testing. :)
That's alpha testing (trying to break it), greatly reduces beta breaks.  That's why some github issues got closed without resolution.  I believe they were called irrelevant bugs.
Bentonville Heart Lites (www.facebook.com/bheartlites)