Visual component become invisible in design mode and cannot get them back in Fire Monkey?

I have encountered quite a few bugs in the IDE when using firemonkey - it is nowhere near as reliable as VCL (yet). In particular the '. Lfm' and '.

Pas' can become unsynchronised, so that there are components in the lfm, which are defined not in the pas file. This doesn't seem to affect runtime but sure can be confusing when you are coding... Try checking to see that all of the components in the lfm are also defined on the form. There also seems to a few issues surrounding form inheritance, where you just have to do a lot of things manually as changes to ancestors are often not picked up by descendants.

I have encountered quite a few bugs in the IDE when using firemonkey - it is nowhere near as reliable as VCL (yet). In particular the '. Lfm' and '.

Pas' can become unsynchronised, so that there are components in the lfm, which are defined not in the pas file. This doesn't seem to affect runtime but sure can be confusing when you are coding... Try checking to see that all of the components in the lfm are also defined on the form. There also seems to a few issues surrounding form inheritance, where you just have to do a lot of things manually as changes to ancestors are often not picked up by descendants.

Also note that most firemonkey components also now have a property called 'DesignVisible'. Check to see that this is set correctly.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.