MAPVIEW upgrade

[kevL]

new toolbar look

+ fixing holes, lots of holes glitches oversights etc

TopView and TopRouteView(Top) are playing nicer together ...

search feels pretty sturdy, next is out of bounds nodes getting RouteView and TopRouteView(Route) to play nicer together i guess.

[kevL]

preview
https://drive.google.com/file/d/1oz2aj1BnOvlsynPDWI2vtwY2MJ2eOpd9/view


edit: wow, glitches galore when a guy pokes his nose around for a bit,

guess I'll have to start versioning :\

ver 2.2 https://github.com/kevL/OpenXCOM.Tools/tree/master/Distribution

suggest: backup your current exe's and dll's since ver 2.2 has beta-like stuff in it. ( /settings folder has not changed )

I'll be fine eventually. -o-

http://files.libertyfund.org/pll/quotes/207.html

[hellrazor]

Thanks for your effort so far. I am gonna try out your new version.

Even thou I am still missing some way to run this natively under Linux...

Fixing that paths are read the normal with "/" would help a lot...

EDIT: The configconverter seems to be working correctly. What also would be nice is if you would allow convert of Images.dat file, which handles custom MCD File entries.

[Stoddard]

Even thou I am still missing some way to run this natively under Linux...

It does run under wine, although quite slowly.

Instructions:

• Add wine repository as per https://wiki.winehq.org/Ubuntu
• install wine-stable: apt update ; apt install winehq-stable winetricks
• initialize 32bit prefix: WINEARCH=win32 winecfg
• Install dotnet35sp1: winetricks dotnet35sp1

re TFTD - it does spew some fishy warnings about route nodes being outside the map for some of them

[hellrazor]

It does run under wine, although quite slowly.

Instructions:

• Add wine repository as per https://wiki.winehq.org/Ubuntu
• install wine-stable: apt update ; apt install winehq-stable winetricks
• initialize 32bit prefix: WINEARCH=win32 winecfg
• Install dotnet35sp1: winetricks dotnet35sp1

re TFTD - it does spew some fishy warnings about route nodes being outside the map for some of them

I know you can run it under wine, but that really is not performant in any way.

The main issue with running it under linux, ewith a mono compiled set is a Alpha transparency issue.
See here: https://openxcom.org/forum/index.php/topic,1321.msg46066.html#msg46066

Not a problem of MapView in itself thou.

[Stoddard]

Well yes, it's unacceptably slow under wine.

Compiling with Mono fails -

Code: [Select]

CSC: error CS2001: Source file `XConsole.cs' could not be found



@kevL maybe you know what's this about?

EDIT: aha, it's XConsole.cs in .csproj, but xConsole.cs on disk.

[hellrazor]

You know what would be really cool, if you could just import your OpenXcom TERRAIN definition via YAML into MapView.

Then just paths to MAP, RMP and MCD files would need addition, adjustment (for custom stuff).

[kevL]

EDIT: aha, it's XConsole.cs in .csproj, but xConsole.cs on disk.

Ben was in mad genius mode when he originally coded Mapview ... (and MV is a work of genius) ... the "mad" part, however, means that the original code is a spaghetti monster.

i'll be frank : I spent over 1000 hr sorting things into something more maintainable. There's lots left to do, in that respect.

thanks for pointing that one out - I could see it being a problem especially under linux/Mac

But i don't have linux or Mac or TFTD. /shrug

You know what would be really cool, if you could just import your OpenXcom TERRAIN definition via YAML into MapView.

Then just paths to MAP, RMP and MCD files would need addition, adjustment (for custom stuff).

y, it would be ... unfortunately my headspace is elsewhere atm. It'd take me many many hours to get back in there and do it correctly ..,


Ps. both you guys strike me as experienced Xcomers, so just poke away at it if you want and i'll wait for something concrete (from my perspective) to pop up

pps. XConsole is a thing that's been disabled in Mv2. It's one of those things that I left the code in though (many other things were outright deleted) - it's basically a debugging tool, but if you're debugging you probably have an IDE so it's unnecessary.

ppps. I think i fixed it : https://github.com/kevL/OpenXCOM.Tools/tree/master/XCom

[Stoddard]

I'll just document this here so that it isn't completely forgotten:

• This xconsole thing is the only thing that fails the build under mono/linux. I just edited the .csproj to point to xConsole.cs
• The second thing is cursor.pck not being found because of backslash - just change it to forward slash in XCom/SharedSpaceServices/SharedSpace.cs:17
• the build also spews errors for not being able to copy exes somewhere, this can be safely ignored
• the transparency bug is in Mono and is apparently being worked upon - see https://github.com/mono/mono/issues/8514 https://github.com/mono/libgdiplus/issues/491

[kevL]

I'll just document this here so that it isn't completely forgotten:

• This xconsole thing is the only thing that fails the build under mono/linux.
• The second thing is cursor.pck not being found because of backslash - just change it to forward slash in XCom/SharedSpaceServices/SharedSpace.cs:17
• the build also spews errors for not being able to copy exes somewhere, this can be safely ignored
• the transparency bug is in Mono and is apparently being worked upon - see https://github.com/mono/mono/issues/8514

1. should be fixed in latest commit [but I changed the filename on disk instead of in the project file... to keep things consistent with the other XC*.* files]
2. not sure how that plays out on Win systems ... probly ok but investigation req'd
3. look at the post-build events for the MapView assembly; delete them. I'm simply copying the .exe's and .dll's to a working directory (release and debug builds - but am going to delete the debug post-build copying since I'm doing things differently here/now). Anyway, look through the build events, blablah
4. okay

[Stoddard]

1. should be fixed in latest commit [but I changed the filename on disk instead of in the project file... to keep things consistent with the other XC*.* files]

Thank you.

2. not sure how that plays out on Win systems ... probly ok but investigation req'd

Should be ok, but I'm no windows person

3. look at the post-build events for the MapView assembly; delete them. I'm simply copying the .exe's and .dll's to a working directory (release and debug builds - but am going to delete the debug post-build copying since I'm doing things differently here/now). Anyway, look through the build events, blablah

Yeah, please remove that, it kinda messes up the future automated builds.



EDIT:

the build is here  https://lxnt.wtf/oxem/#/MapView
the patches applied:
https://github.com/StoddardOXC/OpenXCOM.Tools/commit/141ae7fff8f73e797c4da1565ba966eac107aff6
https://github.com/StoddardOXC/OpenXCOM.Tools/commit/287b9bbae6ab401ba416e31605c202efdb5f3725

now we only have to wait for the mono people to sort out the transparency, and MapView would finally be usable on linux.

[kevL]

re Path separator

https://github.com/kevL/OpenXCOM.Tools/commit/46dbaa754e30fbfa67dac796262e3cc3bcc3773b

[Stoddard]

re Path separator

https://github.com/kevL/OpenXCOM.Tools/commit/46dbaa754e30fbfa67dac796262e3cc3bcc3773b

It works.

Thank you.

[kevL]

sweet

just have to wait for the mono guys to get up to speed, looks like they're hot on the trail too



@Stoddard
beware : https://github.com/kevL/OpenXCOM.Tools/blob/master/MapView/Forms/MainWindow/XCMainWindow.cs#L1036

etc.

[Stoddard]

beware : https://github.com/kevL/OpenXCOM.Tools/blob/master/MapView/Forms/MainWindow/XCMainWindow.cs#L1036

etc.

Yeah, like I said I'd first wait for the mono bug resolution.