I mean exactly what Ricky mentioned above Daniel.
I find it very strange in such a sophisticated system that non integer values (such as 1.3, 1.7 etc) are not valid as cue ID's.
I work on shows that have up to 100-200 cues on average and I find it hard to accept that I can't insert a cue between cue 156 and 157 without having to either painstakingly shift all the cues that come after up one number with all the knock on effect that has within the production (having to update a show callers cue document for example.) or insert a number that is completely out of sequence.
"In the other side I agree with Daniel when he says this is not logical to have cue 1.5 cue 1.7 because when you use the lighting console to trig the system you will not able to recall that kind of IDs. The best solution would be to have a cue list manager to quickly renumber cues in the project."
If I understand you correctly Ricky you are probably referring to a way that a console triggers a PB timeline via dmx (please correct me if I'm wrong). But if you are using a console anyway I can't see why the server wouldn't be controlled completely by the console on a per layer per attribute bases like you would normally do. I might speak for myself here but when I would need that kind of control (timeline triggering) I would simply use MSC out of the console to trigger the sequence which I have done on many occasions.
The bigger point that I'm probably trying to make is that if this system is ever to gain a firmer foothold in theatre or opera this needs to be implemented and I frankly cannot see why that would be a problem. I know for a fact that I am not the only video designer/programmer that shares that opinion and I'm sad to say that I have in the past talked productions out of using the system because of this seemingly 'simple to solve' issue.
I apologise if this seems blunt but I'm simply trying to make a firm point.
All the best,
Ingi Bekk