Error Msg on save

[KenL_MCSE]

Anyone ever see this before? I am getting it when trying to save. And when I try a different name I get the same error.

Sequence works fine, just won't take any new updates...

Attached files

[JBullard]

Read this thread. It might help

http://forums.lightorama.com/forum72/26985.html

[KenL_MCSE]

I found my problem and fixed.

Anyone reading this if you are not a developer and if you are you are not an expert at XML then never ever ever try to fix or modify a LOR file!!!

The problem was I had created some RGB channels and then deleted them. It seems all of them were not removed out of the channel list. And when I added new channels the same index was assigned; the app did not like duplicate records.

Anyway here is what I removed - notice channel 217 is missing - because that was the reinstantiated channel record. which had the same index identifier

[JBullard]

Glad you found the problem

[plasmadrive]

So that I don't double post.. Here is the description of the problem with this error that I found...
http://forums.lightorama.com/view_topic.php?id=28305&forum_id=72&highlight=save+file+error

This could cause some people some real heartaches if they edit for hours before saving..

[plasmadrive]

Well last night I got the very headache. I could not save after about 30 min. of programming. Very frustrating.

I did do something though that may help your code guys out there, (not me though).
I imported my channel config three times because I deleted one of my channels and then decided to use it again. So I went to add it and the setup looked wrong for some reason. (it didn't work the animator. (forgot to update, doh!)

Anyway, I deleted that channel again and reloaded the config. I went about programming and when I tried to say.. CRAP! It happened again. Definitely a software bug.

[JBullard]

plasmadrive wrote:

< snip >

Anyway, I deleted that channel again and reloaded the config. I went about programming and when I tried to say.. CRAP! It happened again. Definitely a software bug.

Software bug? Wouldn't that affect every user ..... every time?

I don't believe that this is a software bug.

[plasmadrive]

Hi JBullard,

Actually it could be that if anyone did what I did, it would effect them all the same. The reason I call it a software bug is because the software only allows you to use the controls it allows you to use. If it crashes, or screws up (won't save) as in my case and apparently several others, there has to be a software issue. (it has been posted before) Read what Kent wrote above..

As my old friend used to say, it shouldn't break because you use it like it was intended. By that, I mean, the GIU should not allow me to get to an unrecoverable situation. There was nothing I could do to sort it out once it was done. (I don't write code nor should I need to to make this work).

That means lost time and output. That manifests itself into hair pulling and excess coffee drinking... Which in turn means I have to trek to the house to pee late at night.. Arrrrgggghhhh$%^#%^$ :-{

I know my PC is fine as it is my engineering PC and I have no issues with it.

Most of the time it S3 runs fine. But not always when you do certain things.. I bet I could duplicate it if I had the time to play with it. It has happened to me several times but only after I have imported a channel config and modified it. So that would be where I would start to look if I wrote code. Oh.. and my configs work fine.. I think it is the modifying that is causing the problems.. but not sure.

[JBullard]

You are using S3 software?

hmmm, this was posted in the S2 software forum

[plasmadrive]

My Bad.. I think that was because I first was looking for someone that had the same issue as me and I didn't realize it was in the S2 software pile until after my first post.. then of course being lazy, I piled on with my second post..

Sorry about that..