clearing a subobject...
It COULD be related to the scheduling of events that was mentioned in another thread and which will be fixed later today (it's fixed, but the new installer is out later today). So event fires, controls update and the dereferencing is done after that. This explains why using the statement TWICE works.
When you grab the new installer later today, please let me know if that fixes your problem 
Nopes, still the same (i did a regenerate Full/Safe of my entire datalayer)
i experimented a bit further and got the following strange result:
When i set the id of the subobject to 0, the bound combobox selects the first item in the list. Whet setting the id again to 0, then the combobox selection is cleared.
But it gets weirder, in my forms i have two of those comboboxes (one for 'loonwerker', one for 'transporteur')so in my code, i first fill my two comboboxes (each has a separate list), then bind the "selectedvalue" of the combobox to the corresponding subobject id of my main entity and i have for each combobox a "clear" button with the following code:
private void btnGeenTransporteur_Click(object sender, System.EventArgs e)
{
//due to a strange databinding issue, i have to call the following line twice to update the gui before setting the value to NULL
m_currentEntity.RecTransportId = 0;
m_currentEntity.RecTransportId = 0;
m_currentEntity.SetNewFieldValue((int)ReceptionFieldIndex.RecTransportId, null);
}
private void btnGeenLoonwerker_Click(object sender, System.EventArgs e)
{
//due to a strange databinding issue, i have to call the following line twice to update the gui before setting the value to NULL
m_currentEntity.RecLoonwerkId = 0;
m_currentEntity.RecLoonwerkId = 0;
m_currentEntity.SetNewFieldValue((int)ReceptionFieldIndex.RecLoonwerkId, null);
}
If i now change the code so the '=0' assignments only appear once, i get the following behavior :
-> i first select for both comboboxes a value
-> then i click btnGeenTransporteur. The transporteur combobox selecteditem goes to the first item. If i would click the button again, the combobox would blank (what i want), but suppose i first click the btnGeenLoonwerker. The loonwerker combobox selecteditem goes to the first item, AND the transporteur combobox blanks. If i then click EITHER of the two buttons, the loonwerker combo also blanks. Now that's what i call weird behavior 
Anyway, i'll just stick to doing the '=0' assignment twice, no problems with it, but it's just weird.
It's a bit hard to track down when the combo box exactly reacts and based on what event... It could be it reacts on the OnfkfieldChanged event, not sure... I'm pretty sure it's about an event that's fired at the wrong time... Now we just have to track down which one 
To test something out, in the m_currentEntity.RecLoonwerkId property Set there is a call to OnRecLoonwerkIdChanged(). Just for test, for this particular routine, if you move that call to SetNewFieldValue() in the same entity, after the value is set and BEFORE the related entity's dereferenced, Does it work then? (to see if that's the cause).
Just to see if i'm on the right track here, the Set property of that RecLoonWerkId property is :
set
{
if(SetNewFieldValue((int)ReceptionFieldIndex.RecLoonwerkId, value))
{
OnRecLoonwerkIdChanged();
}
}
So i copied the OnRecLoonWerkIdChanged() call into the same file's SetNewFieldValue method, i have put it at the last line before "return toReturn;"
In my GUI, now i only have to put the "=0" assigment code once instead of twice for blanking the combobox 
And now i know it for sure ...it has nothing to do with LLBLGen, it's a genuine combobox "bug(?)"
I tested it with an app with a form that has a combobox and a button, and the following source
private void button1_Click(object sender, System.EventArgs e)
{
comboBox1.SelectedIndex = -1;
}
private void Form1_Load(object sender, System.EventArgs e)
{
string[] names = {"test1","test2","test3","test4","test5","test6"};
comboBox1.DataSource = names;
}
If you select an item in the combobox, and then click button1, it goes to the first item in the combobox. Clicking button1 again finally blanks the combobox.
Weird stuff 
thanks for clearing this up!
Very weird indeed... databinding IS sometimes doing weird things, but this is indeed VERY weird.
If you set SelectedItem to null, does that make a difference (i.e.: instead of setting SelectedIndex to -1 )?
i replaced the buttonclick handler with
comboBox1.SelectedItem = null;
and i get the exact same behavior ...going to the first item on the first click, then clearing on the second click.
The strange thing is, when i report the SelectedIndex
private void button1_Click(object sender, System.EventArgs e)
{
comboBox1.SelectedIndex = -1;
MessageBox.Show(comboBox1.SelectedIndex.ToString());
}
it says the first time it's 0, and the second time it's -1. What has this world come to if you can't trust an assignment anymore
HcD wrote:
i replaced the buttonclick handler with
comboBox1.SelectedItem = null;and i get the exact same behavior ...going to the first item on the first click, then clearing on the second click.
The strange thing is, when i report the SelectedIndex
private void button1_Click(object sender, System.EventArgs e) { comboBox1.SelectedIndex = -1; MessageBox.Show(comboBox1.SelectedIndex.ToString()); }it says the first time it's 0, and the second time it's -1. What has this world come to if you can't trust an assignment anymore
heh
If you bind an event handler to the comboBox1.SelectedIndexChanged event, I'm pretty sure it's called twice: once for -1 and once for 0. Still weird, but that's databinding: dark side mistery
Joined: 13-Sep-2005