In my old VS 2010/Delphi Prism environment, when I typed a new property name like âAbcâ and then typed âread fâ, I was presented with the choice of the backing field named âfAbcâ.
That still happens.
But when I used to type âwrite setâ, I would get a choice of âsetAbcâ. That doesnât happen any more.
Is that missing, or am I doing it wrong?
⌠time passes âŚ
Hmmm⌠when I create a NEW project, it seems to be working correctly. But in the one I just created that didnât work, when I go back there, it STILL doesnât work. Not sure what is breaking it.
It doesnât even do the âfAbcâ part now.
⌠time passes âŚ
Now this is just bizarre. I got rid of the property I typed in. I did a clean. I did a rebuild. I think I positioned my cursor at the end of a property line and pressed enter to get a new line for a new property, and IT PUT BACK MY DELETED LINE.
Somebody got a clue on this?
⌠time passes âŚ
I shutdown VS and restarted it and reopened my project. Now it is working.
⌠time passes âŚ
OMG, no it didnât work. It prompted for the âfSelectedPersonâ (in this case), and put it in after the read, but it didnât generate a private backing field. What the heck is going on here?
⌠time passes âŚ
I DID find my previous post: How do I make the event handler method auto generate the code?
Apparently the behavior is still not fixed. (or else I need to download a beta or something)
⌠time passes âŚ
Ew, this seems a mess. Sometimes I get the âfAbcâ and sometimes I donât. Sometimes I get the âSetAbcâ and sometimes I donât.
It looks like if I type âread fAbc write SetAâ, âSetAbcâ is not a choice.
But if I close the popup, and then press âCtrl-Spaceâ, THEN the choice is there.
Why would it not show up on the first popup?