Hi, Because of a new FPC field order optimization it will not be possible in future to use cracker classes, please read the threads: http://www.mail-archive.com/fpc-devel%40lists.freepascal.org/msg26432.html and http://www.mail-archive.com/fpc-devel%40lists.freepascal.org/msg26290.html http://www.mail-archive.com/fpc-devel%40lists.freepascal.org/msg26355.html
In MSEide+MSEgui we need cracker classes and mad workarounds in order to implement extensions and to bend the original behaviour. I think the time has come to leave FCL compatibility and to clean up the whole insanity. Do you use any third party components integrated in MSEide which can be placed in forms or datamodules at design time? We need to find a solution for them because tmsecomponent will not descend from TComponent anymore. Another problem is db.pas. There probably the cleanest solution is to duplicate db.pas in MSEgui with a compatible API, streamlined implementation and a new unit name. What third party DB components which depend on db.pas do you use? Can we drop MSEide support for TMemDatset and friends? Thanks, Martin ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ mseide-msegui-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
