newt's Recent Forum Activity

  • tokenat("text", index, separator)

    text="1,5,6"

    int(tokenat("text", 0, ",")&tokenat("text", 1, ",")&tokenat("text", 2, ","))

    • Post link icon

    Well you have to look at the math.

    Even with the decimation from the loss of "hobbyist" users they will still have a viable business even with a subscriber base of just a few thousand.

    Of course that means they will have to try to retain those users by offering a better product.

    It also means they can try to retain those users by locking them out of the ability to edit their own content if they were to unsubscribe.

    You should probably stop asking for for that. It's just not going to happen.

    No company would ever give up that kind of control.

    Sadly, more professional, feels a lot less friendly.

  • Alright, I guess I got it backwards.

    The x component for the first loop would be 0.

    That's not a row.

    Thanks to all that took a look.

  • I expect

    for x= 0 to 3

    ->for y= 0 to 3, create object at x component= loopindex(" x"), y component= loopindex("y")

    To give me:

    0,1,2,3

    4,5,6,7

    8,9,10,11

    12,13,14,15

  • I've updated the capx to illustrate the difference with some text.

  • I just haddn't linked the sheet for the first save.

    Sorry, it should be correct now, otherwise just link 1 to 1, 2 to 2.

    Still sure something's changed with loops however.

  • Has the order of operations changed?

    https://www.dropbox.com/s/veyunu06021qb ... .capx?dl=0

    In the capx I have a nested loop x, and y

    On the first layout the object is created at y loopindex, and the x loopindex, and is created in columns.

    Run debug to test.

    On the second it's created at x loopindex, and y loopindex , and goes in rows.

    I always thought it was the other way around where x, then y made rows.

  • Yeah, there is a lot of wasted space, and a grid would be doable.

    In fact I wouldn't mind just getting rid of the scroll.

    You're probably right on the speed read thing.

    That might be better for large amounts of text.

    Thanks jobel

  • Update:

    There is now a web app.

    https://pigmalien.github.io/zappnews/index.html

    I probably should have done this first.

    Especially since working with html outside of C2 is such a pain.

    And the export doesn't give us many options for adding html that C2 can't do.

    Kind of odd when you think about how web apps would be considered the main export.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • Lets just say its all about the timing.

    https://pigmalien.github.io/dohelix/

  • One thing that does stand out as being one of webasm's advantages: security. Since it runs binary/bytecode the browser's console window can no longer be abused to hack into a game's code that easily.

    Is this correct?

    Probably.

    It's kind of hard to say for sure how it will be integrated into browsers.

    There might be some exposed code, but the ability to manipulate it will most likely be limited.

    You have to remember its just for browsers, so without knowing that it will have wrappers, it's kind of limited.

    That is to say that if the current trend of pushing apps into browsers does not become more common.

  • The engine would have to be rewritten from the ground up, including plugs. In a different language.

    It's basically the same as asking for a native export.

newt's avatar

newt

Member since 12 Nov, 2008

Twitter
newt has 27 followers

Trophy Case

  • 16-Year Club
  • Entrepreneur Sold something in the asset store
  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Forum Hero Made 1,000 posts in the forums
  • Forum Wizard Made 5,000 posts in the forums
  • Forum Unicorn Made 10,000 posts in the forums
  • Popular Game One of your games has over 1,000 players
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • Enduring Visitor Visited Construct.net 90 days in a row
  • Unrelenting Visitor Visited Construct.net 180 days in a row
  • Continuous Visitor Visited Construct.net 365 days in a row
  • RTFM Read the fabulous manual
  • Email Verified

Progress

31/44
How to earn trophies