No, I just looked at it and when I needed some new, I did a similar thing Martin had done.
Whether this is good / best practice, I have absolutely no idea.
The GraphicsClient base class has the virtual method clbkSaveSurfaceToImage (SURFHANDLE surf, const char *fname, ImageFileFormat fmt, float quality=0.7f)
Most Graphic Clients should have implemented it, so code like this is used:
gclient->clbkSaveSurfaceToImage (0, "Images\\CurrentState"...
Approaches to "starting an windows application with different regional setting":
https://superuser.com/questions/1594374/starting-an-windows-application-with-different-regional-settings...
I have no definitive answer here, but for the readscenario_nextline(scn) function all you need is a valid "scn" file handle.
Same goes for the writescenario_xxx(scn,item,value) functions.
So once you got that they work!
I do not know if the callbacks, that provide that handle, are implemented to...
@jarmonik : Couldn't it be decided in D3D9Client.cpp at runtime with something like this?
bool D3D9Client::clbkInitialise()
{
// ...
g_pD3DObject = OapiExtension::RunsUnderWINE()
? Direct3DCreate9(D3D_SDK_VERSION)
: Direct3DCreate9On12(D3D_SDK_VERSION, &args, 1)...
On github page (https://github.com/orbitersim/orbiter) select "Releases" (at the right side), then under "Assets".
For your 32-bit needs this direct link should always work: https://github.com/orbitersim/orbiter/releases/download/latest/Orbiter-x86.zip
@Thunder Chicken : The PR has been merged. So you can now enjoy the new Lua functions by downloading the latest build.
Changes:
added following file i/ofunctions to Lua interface:
openfile(fname,mode,root)
closefile(fname,mode)
savescenario(name,descr)
writeline(f,line)...
Update: PR for "the rest" has been requested to merge.
...after a very very very undelightful fight between me and the CI tests ;) ...One could argue, that without tests it would have been ready to merg a week earlier :D
https://github.com/orbitersim/orbiter/pull/414
As far as I can remember (long time ago) the Markers have been incorporated into the binary, packed, "Archive" structure in the Textures Folder (for example .\Textures\Earth\Archive\Label.tree)
This has to do with performance considerations as reading those Text-files is not the fastest way to...
That's exactly what is not being "collected" by ...is it CMake, Ninja, somethingelse...
I guess this is something that currently is broken - at least for "native" Windows developers, using the Visual Studio built-in CMake/Ninja/whatever-Toolchain
It is however not a thing that should be accepted...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.