[codifiesParticipant]

Thought you could only override an abstract (which is a shame!)

extended new calls base new…

Monkey

[crayon-5cba9f414508b843169255 inline="true" ] Class base Method New() Print "base new" End Method Method amethod() Print "base method" End Method End Class Class extended Extends base Method New() Print "extended new" End Method End Class Function Main() Local b:base = New base() Print "-----" Local e:extended = New extended() Print "-----" b.amethod() Print "-----" e.amethod() Print "-----" End Function

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27

[crayon-5cba9f414508b843169255 inline="true" ] Class base Method New() Print "base new" End Method Method amethod() Print "base method" End Method End Class   Class extended Extends base Method New() Print "extended new" End Method End Class   Function Main() Local b:base = New base() Print "-----" Local e:extended = New extended() Print "-----" b.amethod() Print "-----" e.amethod() Print "-----" End Function

[/crayon]

[codifiesParticipant]

looked at COrange but not sure if its regularly maintained, SoftPixelEngine the last version is over three years old

Both regular maintenance, and some kind of terrain support are important for me…

[codifiesParticipant]

… it does, but the crying shame is that the terrain “plugin” has issues…

I’m trying to weigh up the pro’s and con’s of various solutions

native mx2 code only, – means porting a lot of different techniques, terrain, lod, ad nauseam BUT probably the best in terms of maintenance and likely to be usable on the widest range of platforms

find something like horde with C API that easy to wrap, while wrapping should be negligible, maintenance and bug fixes mean contributing to a project in a foreign language and or waiting for the project to fix the issue or accept a patch

write a C library “interface” (to something like the excellent and not too bloaty Irrlicht) this isn’t difficult coding but could be a lengthy process

I’m still not decided what’s the best solution…

[codifiesParticipant]

just out of interest try installing in a path without a space and without admin privileges (you should never run stuff as admin…(unless its an installer…))

[codifiesParticipant]

Its fairly common in a number of GUI’s that you can’t actually call anything creating a UI item from within an event, try just setting a flag in the event and responding to the flag in your main loop…

[codifiesParticipant]

I do wonder why it bothers compiling all modules, maybe it should juat gen the api docs and nothing else, then the first time a module is #imported then its compiled (but only for the build type – debug/release)

Are you sure litehtml can’t copy/paste, are you implementing it, using the apropriate methods?

Module manger, you dont use it so no one should ???

[codifiesParticipant]

any examples of your work, always interested in collaborating with artists…

[codifiesParticipant]

There could be loads more mojox examples, and I’m not sure I’d be satisfied, if you get a solution be sure to post it here…

[codifiesParticipant]

The problem is that the array isn’t actually physically in the struct and good job because it would be copying the whole array each time you passed it anywhere…

I definitely think structs are useful for just small collections primitives for example four values defining a rectangle, trying to use it as light weight class is going to be more trouble than its worth…

[codifiesParticipant]

…and benchmarking, in the time it takes to test a few thousand calls, your PC could be doing something else, to stop doing it just in time for the next test, benchmarking is fraught potential pit falls…

[codifiesParticipant]

Field arr:=New Int[20]

isn’t that in effect a pointer, so the pointer isn’t modified but rather what it points to (which isn’t actually in the struct) ie **New** Int[]

[codifiesParticipant]

err careful there, passing a reference to a class could be a lot faster than copying (passing by value) a struct, especially if you’re structs got more than a few members…

Of course you can always pass a pointer to a struct….

[codifiesParticipant]

a wiki would be great for little nuggets like this…

[codifiesParticipant]

you could just use a text editor and compile using a terminal or even a Makefile…

I should dust off my PI sometime… but I’m not a systemd fan, and despite what some people think systemd isn’t optional in Jessie, there are that many dependencies that its impossible to disinfect a system, AntiX Linux now have loads of packages, many with only package dependencies removed, its almost as if it were done on purpose… I digress … could be an excuse to try out Void Linux on PI it works excellently on my laptop… anyway…

../../monkey2/bin/mx2cc_linux makeapp mojotest.monkey2

will build your app obviously your relative path to mx2cc will probably be different

if you run mx2cc (there’s a pi one) you can get a list of all the parameters

[codifiesParticipant]

@adamstrange I think the point could have been made in a more diplomatic manner…

that said the documentation is a bit on the weak side, just documenting an API is sadly seen as enough (by all too many projects), but Mark is working on his own, and simply does not have enough time to document things fully.

I’ve made a handful of posts on the document comments, and I definitely think a Wiki (an official one) is needed, where each command gets 2-3 simple examples, and all the things that come out in blog and forum posts can be collected in one authoritative place.

[Author]

Posts