czar's Forum Posts

  • Hi,

    My project is being designed for a 4:3 ration. However, when exported to cocoonjs on phones etc the layout will be more like 16:9 or 3:2.

    The problem I am having is with wrap. I have an object set to wrap and in letterbox scale everything is working as expected. However, when I set to "scale" (which emulates what will happen when I put it on a tablet/phone device) the object wraps incorrectly and now disappears part way across the screen.

    How, do I reset wrap so that it knows about the current size of the layout?

    I have attached a simple capx to show what I mean.

    Run it first and see bullet moves off the screen and comes back as expected.

    Now, set the project to "scale" and the bullet disappears about 3/4 across.

    dropbox.com/s/bp8xd3rv5t755ox/WrapProblem.capx

  • I updated my link.

  • Solved the problem.

    When setting X change to touch.X("UI")

    Easy :)

  • Yann I love this example but I have one problem with it. I am using the touch version. My UI layer is scale 0, parallax 0,0. In letterbox scale everything is super. However, I noticed when I run it on a 16:9 tablet and I touch the slider it instantly jumps to the right. So I tried setting my project to scale and bang it does it too. So it appears that if the layout is in scale then the set x calculations are incorrect.

    dropbox.com/s/8ic6cdkc9mudw6n/slider-touch_SCALEPROBLEM.caproj

    It is starting to do my head in. Am I missing something obvious? Help!

  • But photocopiers weren't

  • Patriick nice one

  • Could we please get a function so that we can easily figure out which layout a sprite is used? At the moment I have to save as xml files and then search with 3rd party tool.

    At the same time when an existing sprite is loaded with a new image can we have the option to retain current size? At the moment if I replace a 600x600 image with 512x512 image all instances seem to jump to 512x512.

  • Crikey - I didn't realise this I have been agonising about this very issue for a few days now. Ashley and chance of making this more user friendly?

  • Ashley - love the colour coding - any reason it is not applied to the whole event sheet? It would make the code easier to follow.

    and pretty please

    ctrl-home jump to top of event sheet

    ctrl-end - jump to bottom of sheet

    ctrl-shift-1 set bookmark 1 (where one is one to to nine)

    ctrl-1 jump to bookmark

    Bookmarks per event sheet

  • Thanks for the keyboard short cuts. I will start using them.

  • GenkiGenga

    The deactivate works on all event sheets, they don't have to be included. The problem I was having was that one layout was deactivating code belonging to another event sheet.

  • California

    HOw do you mean?

    I would like to have it so that layout is visible and taking up as much room as possible and then be able to switch to show the code. Just like other RAD style IDEs.

  • I spent an hour trying to trace a bug today. (Not helped by lack of debugger.)

    Of course it was a very bizarre "bug"

    It turns out that Deactivating a group "MyGroup" will deactivate all groups of the same name in all event sheets, not just the Event Sheet that does the activation/deactivation.

    It really highlights the fact that C2 needs to have some code analytics.

    1. Groups with same name

    2. unused objects

    3. unused variable names

    etc etc

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I am working with C2 everyday and it is really highlighting some of the major deficiencies. Debugger we are all aware of but many little things too.

    1. It should be much easier to switch between a layout and the associated event sheet - e.g., F12 could toggle between the two

    2. If I open the even sheet I would expect that the layers panel is updated to show the layers of the associated layout (if one is available). This has caught me out so many times now.

    I really hope you guys put more time into usability of C2 - the features are awesome but working with it on big projects is painful. It is like writing a thesis in notepad. Can be done but very painful.

    It would be great if a roadmap was published so that we could anticipate what might be on the short/medium term horizon.