Button behaviour problems.

Hi guys,I've made a number of flights now and on the one hand I'm impressed with a number of details which lead me to believe that this is a potential winner. However, there are still a number of issues to be dealt with, as PMDG will readily admit.One point that I would like to address is the odd or in my opinion undesirable way a number of buttons behave in various situations.- Undesirable automatic button behaviour: a number of times I see buttons on the overhead panel move by themselves. Take for instance the APU bleed switch, on an number of occasions it will trip to off when I switch the APU to off. I could get two of the window heat switches to trip to off by fiddling with the electrical power so that their bus was off. The yaw damper switch when set to on will switch back off after some time under some circumstances. There seem to be some interrelations that I'm sure are not there on the real thing. - MCP buttons: if I start a new flight from scratch, by creating a flight and choosing the PMDG737, I have had no problems with the autopilot. However, if I make one flight and proceed with a new flight or save a situation after having made a flight and then use that situation to start a new flight, the MCP has shown some odd behaviour, for instance at one point in flight it became impossible to move the A/T arm switch, however, by clicking on it I could cycle between arm and off, after VOR LOC was captured the Heading Select switch was still illuminated, in fact even after I disengaged the A/P by pushing the disengage button down the AP button itself was still illuminated.- One way buttons: I have seen some comment already on the undesirable effect you get with some buttons that you can't move the way you want them, for instance the pack switches that you have to move from auto to high to then get to off, so I won't go any further into that other than to say that I think for a really high fidelity simulation I consider this a serious issue.- Button settings at start-up and after saving a situation: to begin with the latter, I think it's a great pity that the button settings aren't saved with a situation, making it virtually impossible to make for instance a number of landing trials, which I usually do with a new model. However, after some time my flights are mostly restricted to complete flights from "cold and dark" to "cold and dark" at the other end, so I could learn to live with that. But it strikes me as odd that when I create a flight from scratch and choose the PMDG737 I get a more or less cold and dark cockpit, but with some very odd button settings. Most notable is that the fuel cutoff switches are at idle! So, in short, I really do want to be able to save at least a cold and dark situation with the buttons in the position that they usually have in that state.- Repeat function absent: I'm not sure that's the right word for it, but what I mean is on some buttons holding the left mouse button over it will only produce one click. Take the radio panel, you actually have to repeat clicking until you get the right frequency. Or the cruise altitude setting on the pressurisation panel. If you make a short flight at FL160, you actually have to click your mouse 38 times to get it down from FL350! My doctor says that's not good for me.I may be back with more comment in the coming days, but again, I would like to say that I do think this is a potential winner, that has a lot going for it. My compliments for that.Leo Bakker