DiegoM's Recent Forum Activity

  • Can you share the project you are working on? Or an example that shows the problem?

    From your explanation it should work.

  • The Pin behaviour is not going anywhere, don't worry about that. It is too widely used to even consider getting rid of it.

    I guess that "replacing" was the wrong term to use.

    What happens is, scene graph transformations solve a lot of the problems where the Pin behaviour fell short or was too cumbersome to use. So in that sense it is a replacement.

    Having said that, both features are widely different in their inner workings, so the Pin behaviour can never really be completely replaced.

  • It's better if you submit an issue in our tracker, as this thread might be quickly forgotten.

    As for key count and performance, I really don't know. Haven't really tested Javascript's limitations myself in that regard, so I can't tell.

  • The limit is arbitrary, it has to have one as memory is not infinite.

    I did notice a couple of things though.

    1) It looks like it is a bug that you can continue to add rows after the limit is reached.

    2) Dictionary could most likely do with a larger limit.

    I think the 1000 limit was put in there because of the array editor, where you can have 100 sheets of 1000 rows and 1000 columns each, which can potentially be a ton of data.

    In the case of dictionaries the limit could be much larger, because the columns are always 2 and there are no sheets.

    In the mean time you'll have to deal with 1000 limit.

  • If I had to guess I'd say it is possible to add what you want. If I were to do it though, I would need to first understand the subject. I really have no idea about noise and it has never been something which I found particularly interesting.

    If there wasn't anything else for me to do, I wouldn't mind giving it a try. But I already have a bunch of other things waiting to be done.

    So I guess you will need to re-invent the wheel? It would probably be faster than waiting for me to figure out all that stuff.

  • Have you tried writing a script in C3 and use DOMParser? You still need to do some coding, but it's all kept in C3.

    I'm sure extracting data from HTML like that will be much more convenient than working with regular expressions and raw text.

    Either way I think you are going to need some coding because C3 really doesn't have anything built for this specific task.

  • I am not super familiar with PHP, but if you need to do DOM parsing, you are better of using a library. Avoid rolling your own regular expressions like the plague, it will only cause you trouble in the future.

    Looking around I found this PHP DOM manipulation library github.com/ivopetkov/html5-dom-document-php/, have never used it, but it looks promising and has a bunch of stars in github. And it seems to have documentation, which is always a plus.

    Even if you are using a library, the problem with scraping is that it depends on the layout you are trying to get data from, so if that changes, you need to update your code. Because of that reason, in the past I found that it is better to keep your queries just specific enough to get what you want, in the case the layout changes a little bit, but not too much, you might get away without changing anything on your side.

    What does this has to do with C3?

  • This is a regression bug introduced in the latest beta, will be fixed in the next beta.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • You do not have permission to view this post

  • Here is a very contrived example showing DrawingCanvas's Save Image action to save the state of the canvas, then uses the On Saved Image trigger plus the Saved Image URL expression to set the saved image into an empty Sprite instance.

    dropbox.com/scl/fi/02cteu7w4xdjxu0gfaiff/DrawingCanvasSaveImage.c3p

    For the case that you are describing, I think what you would need to do is keep track of the url of the saved image on the trigger, so you can retrieve it later on, outside of the trigger.

  • If you were able to set depth to more than 100, that was definitely a bug. Not being able to do it is the correct behaviour.

    I don't think there is any particular reason for the limit being at 100, it seems like it was just set as a sensible limit. Obviously it can not be infinite as that could eventually lead to running out of memory.

    The thing with the depth property is that each additional increment is essentially adding a whole extra sheet. If you are using relatively small sheets, let's say 10x10 for example, that is fine. In that case each depth increment would be adding an extra sheet with 10 rows and 10 columns, which would add up to a total of 100 new cells. If your sheets are larger though, each increment could potentially be incrementing the total cell count dramatically.

    The limit for width and height is currently set at 1000, in the case of using a sheet of 1000x1000, each depth increment would be a million extra cells, which could rack up memory pretty quickly if left unlimited.

  • Just checked this to be sure, and seems that 100 depth has been the limit since the feature was implemented. So I am not really sure how you were ever able to do more than that.

DiegoM's avatar

DiegoM

Member since 24 Apr, 2015

Twitter
DiegoM has 1,424,752 followers

Trophy Case

  • 9-Year Club
  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Regular Visitor Visited Construct.net 7 days in a row
  • RTFM Read the fabulous manual
  • Email Verified

Progress

15/44
How to earn trophies

Blogs