03-06-2009 09:28 AM
There is something odd about your enum that I can't quite figure out. (Actually while toying around with things, LV crashed on me.)
There are a lot of coercion dots along your blue enum wire. Your case structure has a mix of numbers and names. Usually with case structures wired to enums, the cases will all be named. I think this could cause unexpected behavior in your program.
When I deleted the wire going from the case structure to the right hand shift register, a lot of coercion dots went away. And the numbered cases in the case structure suddenly became named. But there were stil coercion dots where the constants in the cases run into the right hand tunnel of the case structure. If I re-add the wire from the case structure to the shift register. Some of the named cases go back to numbers.
All the constants appear to be identical, so I don't know why they are getting coercion dots.
I would recommend taking one of your constants, and turning it into a typedef control. Then go back and replace all the constants with the type def constant. You can search the forums if you aren't familiar with how to use type defs. The advantages are that all the constants will be consistent. And if you need to add a case at a later date, you can add it to the type def enum control one time. You won't have to go back and updated dozens of instances of the constants.
03-06-2009 09:28 AM
03-06-2009 09:31 AM
cmhand wrote:
Okay so I think that has to do with the enum thing...when I added more frames to my sequence and then added them into the enum thing the title turned red and all the previous titles on the frames changed to numbers...why is that and how do i fix it???
Wow, a lot of other messages popped up while I was typing mine. Please take a look at my message right before this. That should get you on the right track.
03-06-2009 09:32 AM
03-06-2009 09:35 AM
03-06-2009 09:36 AM
Ravens Fan wrote:There is something odd about your enum that I can't quite figure out. (Actually while toying around with things, LV crashed on me.)
There are a lot of coercion dots along your blue enum wire. Your case structure has a mix of numbers and names. Usually with case structures wired to enums, the cases will all be named. I think this could cause unexpected behavior in your program.
When I deleted the wire going from the case structure to the right hand shift register, a lot of coercion dots went away. And the numbered cases in the case structure suddenly became named. But there were stil coercion dots where the constants in the cases run into the right hand tunnel of the case structure. If I re-add the wire from the case structure to the shift register. Some of the named cases go back to numbers.
All the constants appear to be identical, so I don't know why they are getting coercion dots.
I would recommend taking one of your constants, and turning it into a typedef control. Then go back and replace all the constants with the type def constant. You can search the forums if you aren't familiar with how to use type defs. The advantages are that all the constants will be consistent. And if you need to add a case at a later date, you can add it to the type def enum control one time. You won't have to go back and updated dozens of instances of the constants.
I was having the same issue. When I deleted the shift register and enum and started from scratch it seemed to all go away though? Weird.
03-06-2009 09:41 AM
03-06-2009 09:49 AM
03-06-2009 09:49 AM
03-06-2009 09:53 AM