I finally got another reproducible example, using only the Smart tool.
 
1) Put the Event Inspector window in "Collapsed" mode.
2) Restart Sonar.
3) Create a fresh project with File>New>Blank Template, call it Temp1.
4) Insert a MIDI track and open the PRV window (Alt+3).
5) Create two notes with the Smart Tool. Ensure they are different notes and both start some beats into the song.
6) Select any note with the Smart Tool.
7) Hover over the "Events" tab. The Event Inspector flies out.
8) Click on "Time". It displays "0". This is definitely NOT the start time of the selected note.
9) Click on "Duration".
 
The note has moved to the beginning of the song.

jpetersen
I finally got another reproducible example, using only the Smart tool.
 
1) Put the Event Inspector window in "Collapsed" mode.
2) Restart Sonar.
3) Create a fresh project with File>New>Blank Template, call it Temp1.
4) Insert a MIDI track and open the PRV window (Alt+3).
5) Create two notes with the Smart Tool. Ensure they are different notes and both start some beats into the song.
6) Select any note with the Smart Tool.
7) Hover over the "Events" tab. The Event Inspector flies out.
8) Click on "Time". It displays "0". This is definitely NOT the start time of the selected note.
9) Click on "Duration".
 
The note has moved to the beginning of the song.

 
I can reproduce it in Lexington. I rolled back to Allston Update 1 and also see "0" in step #8, but clicking on "Duration" doesn't move the selected note to the beginning of the song. Unlike in Lexington, if I then select either of the notes again, the Time and Duration fields still show "0" (when clicked).
 

jpetersen
I finally got another reproducible example, using only the Smart tool.
 
1) Put the Event Inspector window in "Collapsed" mode.
2) Restart Sonar.
3) Create a fresh project with File>New>Blank Template, call it Temp1.
4) Insert a MIDI track and open the PRV window (Alt+3).
5) Create two notes with the Smart Tool. Ensure they are different notes and both start some beats into the song.
6) Select any note with the Smart Tool.
7) Hover over the "Events" tab. The Event Inspector flies out.
8) Click on "Time". It displays "0". This is definitely NOT the start time of the selected note.
9) Click on "Duration".
 
The note has moved to the beginning of the song.

I can reproduce this. The reason I couldn't reproduce before is it seems this won't happen if the Event Inspector is not collapsed. As far as I can tell it works as expected if small or large. Once I did what you said and started with it collapsed, I could reproduce.
 
Make sure you send the recipe to Cakewalk.

jpetersen
I finally got another reproducible example, using only the Smart tool.
 
1) Put the Event Inspector window in "Collapsed" mode.
2) Restart Sonar.
3) Create a fresh project with File>New>Blank Template, call it Temp1.
4) Insert a MIDI track and open the PRV window (Alt+3).
5) Create two notes with the Smart Tool. Ensure they are different notes and both start some beats into the song.
6) Select any note with the Smart Tool.
7) Hover over the "Events" tab. The Event Inspector flies out.
8) Click on "Time". It displays "0". This is definitely NOT the start time of the selected note.
9) Click on "Duration".
 
The note has moved to the beginning of the song.

This is very different from the original post and the thread title,which was comparing Lexington to X3. X3 doesn't have a collapsed mode for Control Bar modules, so anything involving starting with the Event Inspector collapsed can't be compared. Also, that post was about changing values of a group of notes, not about viewing the values of one note.
 
Although it's true that the EI doesn't show the value of a selected note if it's not already open when the note is selected (the values of the previously changed note - if any - are displayed). I don't see any problem with changing that note's parameters in the flyout.
 
 
 
 

Anderton

jpetersen
I finally got another reproducible example, using only the Smart tool.
 
1) Put the Event Inspector window in "Collapsed" mode.
2) Restart Sonar.
3) Create a fresh project with File>New>Blank Template, call it Temp1.
4) Insert a MIDI track and open the PRV window (Alt+3).
5) Create two notes with the Smart Tool. Ensure they are different notes and both start some beats into the song.
6) Select any note with the Smart Tool.
7) Hover over the "Events" tab. The Event Inspector flies out.
8) Click on "Time". It displays "0". This is definitely NOT the start time of the selected note.
9) Click on "Duration".
 
The note has moved to the beginning of the song.

I can reproduce this. The reason I couldn't reproduce before is it seems this won't happen if the Event Inspector is not collapsed. As far as I can tell it works as expected if small or large. Once I did what you said and started with it collapsed, I could reproduce.
 
Make sure you send the recipe to Cakewalk.

Yes, I can reproduce this as well. It only happens when the E.I. is collapsed.
After highlighting a note(s), if I hover over the E.I. it displays in the usual dark grey, but as soon as I move the cursor inside the boundaries of the E.I., the E.I. becomes a lighter shade of grey and nothing is selectable.

I'm not sure if it's by design or not but double clicking in the EI allows me to adjust any of the parameters, regardless of the size of the module.

Ignore my last post, single clicking works as well although I'm not sure it was earlier..... 
 

On playing around with this some more, I can see there's a problem in the very specific case that:
 
1. The Event Inspector is collapsed.
2. You initially select a field to edit, and then abort and select another field.
 
The default value  - or the value of a previously edited note - that comes up when you fly out the collapsed EI will be assigned to the first parameter you touched, because moving to another field is effectively the same as hitting Enter. The issue is avoided if you follow through and change the first value you click.
 
The root of the problem is Event Inspector not reading in the parameters of the currently selected note when its collapsed.
 
A valid issue, but totally different from the original post as I mentioned.

Let me try sum all that up:
 
1) With the E.I. visible (Large or Small), then:
A) with the SELECT tool,
i) clicking on a note will send the value to the E.I.
ii) but will NOT highlight the note so that
iii) clicking in the E.I. DOES NOT allow editing. 
 
B) With the SMART tool,
i) clicking on a note will send the value to the E.I.
ii) and the note WILL be highlighted so that 
iii) clicking in the E.I. DOES allow editing.
iv) With any of the SELECT, MOVE, EDIT, DRAW or ERASE tools active you can edit a previously highlighted note, too.
 
2) With the E.I. collapsed, then:
A) with the SELECT tool,
i) clicking on a note will NOT send the value to the E.I.
ii) will as before NOT highlight the note so that
iii) clicking in the E.I. DOES NOT allow editing. 
iv) If the user has not done anything yet, it is quite likely that the E.I. will be blank.
 
B) With the SMART tool,
i) clicking on a note will also NOT send the value to the E.I.
ii) the note WILL however be highlighted so that 
iii) flying out the E.I. DOES allow editing with any of the tools active, BUT 
iv) the values will NOT have been updated, so  that merely clicking inside, then clicking away will cause the highlighted note to take on the value of whatever value was present. This causes unexpected effects, typically the note jumping somewhere.
 
Essentially, the issues are:
I) The E.I. will not update in collapsed mode, and
IIa) in Lexington ONLY the Smart tool can highlight a note, whereas
IIb) in X3 both the Smart AND the Select tool can highlight a note.
 
And in Sonar 8.5.3, the Move tool can highlight a note, too (press Alt with any tool active = Move).
This I find time-saving because you then immediately see edited values in the E.I as you change
them and you can go over and tweak them in the E.I. without changing tools.
 
It might be worth a feature-request that ANY tool can select and highlight a note (well, Edit and Move would make sense).
 
I found it amusing that, if I lasso a note with the Delete tool, the values jump into the E.I. but the note is deleted!

That's good. Complicated, but it covers all the bases. I'll put that in the problem report.