[peterigzParticipant]

Ahh, possibly you’re trying to get the size before mojox has actually figured out what size they should be? Try a bit later on in the process after View.OnMeasure has been called (I’m not sure when that is though exactly or if you can hook into it somehow)

[peterigzParticipant]

That’s right I mean Monkey 1 as a module, the editor is actually written in Blitzmax.  So you can use the editor with Monkey 1 and 2, although like I say I haven’t tested Monkey 1 in a while but I can fix bugs if you find any.

[peterigzParticipant]

The editor can export sprite sheets, but you can also use the effects realtime in your game, so it’s up to what your needs are. There is a Monkey 1 version but I haven’t looked at that in a long time so I don’t know if it’s buggy or not.

Thanks, abakobo, I saw you github issue and fixed that

[peterigzParticipant]

I’m just using the docs here and trying to figure things out by looking at the source code for Ted2. I think I’ll write a tutorial for mojox once I’ve figured most things out, I like the look of mojox so far I think it’ll be nice to work with.

Regarding the sizes, try using MeasuredSize which is a property that returns a Vec2.

Monkey

pb=New PushButton("info") Print " pb W:"+pb.MeasuredSize.x Print " pb H:"+pb.MeasuredSize.y buttonUP=New Button( "",Image.Load("asset::pad_up.png" )) Print " buttonUP W:"+buttonUP.MeasuredSize.x Print " buttonUP H:"+buttonUP.MeasuredSize.y

1 2 3 4 5 6 7 8 9 10 11

pb=New PushButton("info") Print " pb W:"+pb.MeasuredSize.x Print " pb H:"+pb.MeasuredSize.y buttonUP=New Button( "",Image.Load("asset::pad_up.png" )) Print " buttonUP W:"+buttonUP.MeasuredSize.x Print " buttonUP H:"+buttonUP.MeasuredSize.y

[peterigzParticipant]

I’d be happy to contribute where I can, an open docs system (with invited users) sounds like a good way to go.

[peterigzParticipant]

I’m just starting to learn mojox too. According to the documents each gadget/widget like buttons has different fields that invoke a method or lambda. Here’s some examples for the code you gave, and my preferred way which would be to extend the element and keep the events separate in their own class (see MyButton below). This is similar to how wxWidgets works. But I’m a newb so maybe someone else can chime in as well

Monkey

#Import "gui/" #Import "<std>" #Import "<mojo>" #Import "<mojox>" Using std.. Using mojo.. Using mojox.. Global virtualResolution:=New Vec2i( 640,480 ) Class MyApp Extends Window Field name:TextField Field check:CheckButton Method New( title:String,width:Int,height:Int,flags:WindowFlags=WindowFlags.Resizable ) Super.New( title,width,height,flags ) Layout="letterbox" 'Create Docking Views Local mainview:=New DockingView Local dv:=New DockingView 'Create Buttons Local button:=New MyButton( "OK" ) Local buttonUP:=New PushButton( "",Image.Load("asset::pad_up.png" )) Local pb:=New PushButton("info") 'Create Check Button check = New CheckButton() 'Create Label Local label:=New Label("Enter Text") 'Create Text Field name = New TextField("",20) 'add the above objects to dv docking view dv.AddView(button,"left") dv.AddView(buttonUP,"left") dv.AddView(check,"left") dv.AddView(label,"left") dv.AddView(name,"left") dv.AddView(pb,"left") 'add the dv to the main view mainview.AddView(dv,"top") ' add the mainview to the Window ContentView=mainview 'Point to methods in this class for each event. buttonUP.Clicked = OnButtonUp name.TextChanged = OnTextModified name.Entered = OnTextEnter check.Clicked = OnCheckClicked End Method OnRender( canvas:Canvas ) Override App.RequestRender() End Method OnMeasure:Vec2i() Override Return virtualResolution End Method OnButtonUp:Void() Print "Button Up Clicked" End Method OnTextModified:Void() Print name.Text End Method OnTextEnter:Void() Print "Enter Hit: " + name.Text End Method OnCheckClicked:Void() If check.Checked Print "Checked" Else Print "Not Checked" End End End 'You can extend buttons and other things to package events into their own classes Class MyButton Extends Button Field ICouldBeAnything:String Method New( text:String="",icon:Image=Null ) Super.New( text,icon ) ICouldBeAnything = "Hello!" Clicked = OnClicked End Method OnClicked:Void() Print "Clicked! " + ICouldBeAnything End End Function Main() New AppInstance New MyApp( "Examples",640,480 ) App.Run() End

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 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114

#Import "gui/" #Import "<std>" #Import "<mojo>" #Import "<mojox>" Using std.. Using mojo.. Using mojox.. Global virtualResolution:=New Vec2i( 640,480 ) Class MyApp Extends Window Field name:TextField Field check:CheckButton     Method New( title:String,width:Int,height:Int,flags:WindowFlags=WindowFlags.Resizable )     Super.New( title,width,height,flags )     Layout="letterbox"     'Create Docking Views     Local mainview:=New DockingView     Local dv:=New DockingView     'Create Buttons     Local button:=New MyButton( "OK" )     Local buttonUP:=New PushButton( "",Image.Load("asset::pad_up.png" ))     Local pb:=New PushButton("info")     'Create Check Button     check = New CheckButton()     'Create Label     Local label:=New Label("Enter Text")     'Create Text Field     name = New TextField("",20)     'add the above objects to dv docking view     dv.AddView(button,"left")     dv.AddView(buttonUP,"left")     dv.AddView(check,"left")     dv.AddView(label,"left")     dv.AddView(name,"left")     dv.AddView(pb,"left")     'add the dv to the main view     mainview.AddView(dv,"top")     ' add the mainview to the Window     ContentView=mainview   'Point to methods in this class for each event.     buttonUP.Clicked = OnButtonUp     name.TextChanged = OnTextModified     name.Entered = OnTextEnter     check.Clicked = OnCheckClicked   End   Method OnRender( canvas:Canvas ) Override     App.RequestRender()   End   Method OnMeasure:Vec2i() Override     Return virtualResolution   End      Method OnButtonUp:Void()   Print "Button Up Clicked"   End      Method OnTextModified:Void()   Print name.Text   End      Method OnTextEnter:Void()   Print "Enter Hit: " + name.Text   End      Method OnCheckClicked:Void()   If check.Checked   Print "Checked"   Else   Print "Not Checked"   End   End End   'You can extend buttons and other things to package events into their own classes Class MyButton Extends Button Field ICouldBeAnything:String Method New( text:String="",icon:Image=Null ) Super.New( text,icon ) ICouldBeAnything = "Hello!" Clicked = OnClicked End Method OnClicked:Void() Print "Clicked! " + ICouldBeAnything End End   Function Main()   New AppInstance   New MyApp( "Examples",640,480 )   App.Run() End

[peterigzParticipant]

@pakz TimelineFX has a collisions module with box, line, circle and poly collisions which might be of some use to you.

[peterigzParticipant]

Happy new year! Good luck with the office, sounds like a positive step

Lots of documentation would be great, make it as easy as possible for people to get started, I’ll hopefully help out there if I get a chance to do tutorials. Looking forward to the youtube vids as well! The admob stuff Xaron mentions is probably high priority as well.

I also think Monkey 2 has loads of potential if you support as many popular libraries/tools as possible (as mentioned in email) – maptilers, sprite animators, physics engines etc., and make a youtube vid for each one about how integrate and use in monkey. It’ll be a great way to build interest and traffic as you’ll be tapping into the audiences and users of those products. But I do think better docs will increase conversion rates. It’s easy to convert old blitz users who already have a good idea, but not so sure about brand new know-nothing-about blitz users.

You said you share an office with a couple of developers who’ve never heard of blitz/monkey, ask them to use monkey 2 and get their feedback if they’re willing. But they’re not allowed to consult with you, they’re only allowed to use what’s available online to figure things out. Might help give you some direction for what needs doing.

For me personally, it’s my 3rd year of freelancing (web developer), and this year I will launch my first WordPress theme. Aim is to earn enough from that and TimelineFX (plus monthly maintenance from a few clients), to just do that full time as building web sites kind of sucks, but they do pay the bills

[peterigzParticipant]

Merry Christmas all!

[peterigzParticipant]

I checked back in my Blitzmax version of this code where it works fine but actually Blitzmax loadanimation created each image separately which basically eliminates the problem. So I adjusted my load animation to create separate images instead (which is what I thought was happening anyway until I ran into this issue) and it works perfectly. Looking around the web it does seem like a common issue people face with various hacks to fix. Incidentally this comes close to fixing where you adjust the UpdateTexCoords in the Texture Class like so:

Monkey

Method UpdateTexCoords() _texCoords.min.x=Float(_rect.min.x+0.5)/_textures[0].Width _texCoords.min.y=Float(_rect.min.y+0.5)/_textures[0].Height _texCoords.max.x=Float(_rect.max.x-0.5)/_textures[0].Width _texCoords.max.y=Float(_rect.max.y-0.5)/_textures[0].Height End

1 2 3 4 5 6

Method UpdateTexCoords() _texCoords.min.x=Float(_rect.min.x+0.5)/_textures[0].Width _texCoords.min.y=Float(_rect.min.y+0.5)/_textures[0].Height _texCoords.max.x=Float(_rect.max.x-0.5)/_textures[0].Width _texCoords.max.y=Float(_rect.max.y-0.5)/_textures[0].Height End

But it wasn’t quite perfect, the tiles just didn’t quite line up perfectly but the bleeding was eliminated. Either way I’m happy with separate images for tiles which i notice is what Playniax does as well.

[peterigzParticipant]

I see thanks. I tried filter nearest and that almost fixes it, but it glitches when y is 0.5. x doesn’t glitch at all. Not sure if that’s correct behaviour? Be nice if nearest was a solution, otherwise I can just try implementing the border technique as outlined in the link.

I’ve attached a working example if anyone wants to test.

Attachments:

1. tiletest.zip

[peterigzParticipant]

To hide the mouse:

Monkey

Mouse.PointerVisible = False

1	Mouse.PointerVisible = False

[peterigzParticipant]

It looks like SwapInterval caps at 4 for me, so the lowest FPS I get is 15fps (on windows 10), so it’s hard to tell if it’s slower than it should be. The timer method seems to work well though, with SwapInterval 0.

[peterigzParticipant]

SwapInterval means:

0 = No Vsync wait at all
1 = 1 Render call per vsync
2 = 1 render call every 2 vsyncs

.. and so on. So the higher your swap interval the slower it will render. This is an issue with all games as far as I know. You’ll find that not many FPS players play with vsync on because they want to increase FPS and therefore mouse responsiveness. QuakeLive for example generally caps at 125FPS. But they might also have a way to poll the input at a higher frequency?

I wonder if you can improve the feel of it by using the mouse speed combined with mouse position to have some kind of predictive movement? Just a theory

[peterigzParticipant]

It’s mainly because of vsync as Jesse says, so the mouse will only be polled at 60hz (or whatever your monitor is). You can disable vsync by adding SwapInterval = 0 in the window constructor which will improve things. I prefer doing this and then using some kind of timing code to separate the rendering and logic to make the game as responsive as possible. Drawback though is the potential for screen tearing as you’re not waiting for a vsync anymore.

[Author]

Posts