Monthly report (Full Version)

All Forums >> [New Releases from Matrix Games] >> World in Flames



Message


PaxMondo -> Monthly report (3/5/2019 2:24:04 AM)

Steve?




pzgndr -> RE: Monthly report (3/6/2019 12:49:14 AM)

Hopefully Steve is having more success with Delphi 10 Berlin than I had with C++Builder. Trying to convert Empires in Arms from CodeGear C++Builder 2007 with AnsiString to Berlin 10 with UnicodeString and other updates was beyond my humble abilities. I got deep enough into it to decide it wasn't worth it and got back to what was working for me, but wasted a few months doing so. Curious to see his next report update, again hopefully with some good news.




Shannon V. OKeets -> RE: Monthly report (3/6/2019 4:42:31 AM)


quote:

ORIGINAL: pzgndr

Hopefully Steve is having more success with Delphi 10 Berlin than I had with C++Builder. Trying to convert Empires in Arms from CodeGear C++Builder 2007 with AnsiString to Berlin 10 with UnicodeString and other updates was beyond my humble abilities. I got deep enough into it to decide it wasn't worth it and got back to what was working for me, but wasted a few months doing so. Curious to see his next report update, again hopefully with some good news.

I ignored most of the warning about string conversions. That was back in 2015 when I converted to Delphi XE8. Some of them required fixing, but there were also a lot of warnings about the compiler/linker making some 'automatic' conversion assumptions. The dozen of so that still appear every time I do a full build don't seem to matter to how the program executes.




pzgndr -> RE: Monthly report (3/6/2019 1:44:42 PM)

Good to hear!




Shannon V. OKeets -> RE: Monthly report (3/9/2019 12:16:51 AM)


quote:

ORIGINAL: pzgndr

Good to hear!

The 2 main problems I had to overcome (MWIF now compiles and builds under Delphi 10.3) were:

1 - DPI (dots per inch) is set to Monitor2 - which MWIF doesn't need. Setting DPI to 'none' works the same way as Delphi XE8 does. When the value is Monitor2, all the text shown on the screen is too large. That makes virtually everything about the game unusable.

2 - vcl.SetSizeConstraints now fails if the sole parameter passed to it when it is created is nil. That's because the parameter is used (as FControl) and a nil value generates a fatal Access Violation. I now have the MWIF code pass a TWinControl value based on Owner. If you want more details about this, let me know.




Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.671875