nobuyuki

Forum Replies Created

Viewing 15 posts - 16 through 30 (of 54 total)
  • Author
    Posts
  • in reply to: Continue Line #7164

    nobuyuki
    Participant

    might be best not to initialize strings that way anyway since strings are immutable and this creates junk for the gc to collect.  Maybe……

    Please pardon me if this is not valid mx2, I’m aware that array initialization may be different now and require something like “New Array<String>” before the open square bracket.

    in reply to: Consistency #7163

    nobuyuki
    Participant

    itch.io is a way better option than what was being done before, it makes it way easier to give mx2 some indie exposure.  Since it’s not “exactly” a commercial product, this is probably the best form it can take to apply to a new audience rather than living its life entirely in some open source repo or patreon post.

    in reply to: Ted2Go IDE #7151

    nobuyuki
    Participant

    I’m not sure what you mean, but in other IDEs (mainly jungle and VS) I just press the key when autocomplete has selected the item I want, including the dot key.

    in reply to: Ted2Go IDE #7149

    nobuyuki
    Participant

    cool, thanks!  While I’m at it, I may as well request options for completion by spacebar, open parenthesis and dot in addition to “enter”.  Keep up the good work 🙂

    in reply to: Ted2Go IDE #7147

    nobuyuki
    Participant

    hi nero,

    is there any way to reduce the autocomplete box automatically by filtering out items that aren’t in the current scope?  Currently my first test of this feature while mucking around in the bananas shows everything from all modules when I start typing regardless of whether they’re imported or not.

     

    Example (I think):  libc.clock comes up as “clock” because libc is imported by std, but outside of std.monkey2 this requires a namespace prefix unless libc is explicitly imported.   Using the definition suggested by autocomplete will result in a compile error due to missing identifier…

    in reply to: gles3.0 vs gles2.0 for mx23d #7039

    nobuyuki
    Participant

    I’m all for it.  The legacy bmax users may not like it so much if some game portals still require xp support (which only officially does d3d9), or have a large android install base without gles3 support, but since this is strictly a 3d module, I don’t see the problem, because as a modern graphics target, it will be one less reason for newcomers to “shy away” from mx23d as a viable engine for their future projects.

    GLES3 support’s adoption rate on android may not be so high because a lot of the more affordable tiers of no-name phones coming out of china and the older smartphones issued as freebies by budget carriers tend to use more established chipsets to 1. reduce the handset’s BoM, and 2.  increase the shelf life their devices without having to dedicate any money to updating driver firmware/software/etc. since less-well-established SoCs could potentially mean that the drivers for it aren’t as well-written or well-tested.

    One thing I’ll be slightly sad to see is that this means mx23d won’t support the current generation of hobbyist computers.  They usually don’t support more than gles2.0 — I know the Pi 3 still runs aging Videocore IV graphics architecture, which has required emulation authors to backport some of their more recent efforts to support it.  That’s hobbyist-level stuff, though, and not a big concern for commercial stuff.

     

    Edit:  Also note that over half of android users as of this writing are running android 5.1 (lollipop) or below, which is now 2 versions behind the current and correlates with the gles2.0 only support.  It’s also a 2-year old version of android.  Within the next 6 months you’ll probably see a large shift as people come off their contracts and “refresh” their phone.  Don’t know if that’s common in most countries, but in the US many phones are subsidized and tied to 1-2 year contracts.  So bear that in mind!

    in reply to: Try, Catch Errors #6810

    nobuyuki
    Participant

    I don’t know if mx2 does this, but every monkey uncaught exception have the same error.  It would be nice if it was able to spit out the type of exception it was if it came unexpectedly…

    And yeah, a base type with at least an ID and message fields would’ve been ideal for this!

    in reply to: About branding #5685

    nobuyuki
    Participant

    Just call it mx2 like everyone else does half the time…  I don’t think the blitzbasic name carries water the way you guys think it does with anyone not old enough to remember it anymore…

    in reply to: Monkey2 Build From Source Help #5282

    nobuyuki
    Participant

    @nerobot

    I also use sourcetree, and I think it would be useful to have!

    in reply to: would $1 patreon be insulting? #5281

    nobuyuki
    Participant

    Nothing wrong with the $1 tier. Not everyone’s making dough off monkey/mx2 right now and might not even be pulling in decent bank to begin with!  Some people just want to support continuing further development of a great language with a great heritage while working towards their own big break, and I don’t see anything wrong with that.  ‘Specially those who are still in the “wait-and-see” camp and aren’t active in the community at the moment.  Once you start donating it’s like opening a door, it says you’re ready to spend something to see something succeed and there’s power in having that “captive audience” if you’re the person being donated to 🙂

    in reply to: Win 7 adoption out paces Win 10 as it flatlines. #4950

    nobuyuki
    Participant

    That’s unfortunate.  Windows 7 is not going to continue to have first party support forever.  With 10s adoption of truly cross platform SDKs as well as the new Debian-based Linux subsystem for binary compatibility with Linux apps I see a future for Windows, but 7 is currently a dead end.

    in reply to: GLFW v3.2.1 module #4948

    nobuyuki
    Participant

    @codifies well I’ll be glad to be wrong. Updating the input driver on Windows might’ve been part of their long-time milestones, and I admit I hadn’t checked in a long while.

    in reply to: GLFW v3.2.1 module #4941

    nobuyuki
    Participant

    Doesn’t glfw still use winmm for joystick detection on Windows?  That was a real pain.  One of my aftermarket 360 pads never worked right on Windows 8 and 10 and I saw this issue reported with another game.   two of the digital axes were always “stuck” at -1.  You’d think they’d switch to xinput2 by now, if not to fix Legacy issues, but also to split the trigger axises.  Nope.

    in reply to: ItemMaker #4644

    nobuyuki
    Participant

    Neat little thing.  For some reason it reminds me of how you managed animations/directions and added hotspot metadata in MMF.  I was definitely hunting for a similar tool seeing as how it’s not easy to add arbitrary metadata to Aseprite json exports without cluttering up the UI with tons of tags.

    in reply to: Playniax news #4367

    nobuyuki
    Participant

    Tony,

    Thanks for making the framework components free!  I hope this will make the adoption of the language go a lot more smoothly.  Are we able to contribute to it at all?  Dual licensed or has one of those code giveaway agreements or such?  I really like the idea of building up the toolbox to give the mx2 community a good running start once it’s ready for commercial development.

     

    And of course, having a vertically-integrated editor like pyro2 will be awesome.  Exciting stuff!

Viewing 15 posts - 16 through 30 (of 54 total)