Rich's Forum Posts

  • It's been added for the next build

  • For what it's worth, I just reproduced this. Only when using your images, for some reason.

    It seemed to import OK, so I minimized to go post this, then I maximized it and the layout editor won't display.

  • Agreed, I moved it

  • Whilst that's a good idea in theory, event sheets are independent of layouts. If you created an event sheet and add some events, there has to be objects there to use, if that makes sense.

  • Direct-X runtime doesn't have this problem, no. Hopefully it'll be resolved soon enough.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • This is of topic, don't shoot me please.

    Could someone post or pm a list where you explain what DLL, VS, Dev C++, SDK and IDE are?

    A DLL is a file which executable files call functions from; these can be informational, or functions which do specific things. Direct-X for example is programmed into DLL files, which the Construct Runtime calls functions from. Every plugin created via the SDK is a DLL file.

    The SDK is a bunch of C++ files which creates a DLL file compatible with Construct and the runtime.

    VS is Visual Studio, the program which compiles the SDK source files and creates a DLL file. It's basically a text editor with syntax hilighting, a resource editor (to set up dialogs, icons, etc).

    So basically, you use Visual Studio to edit and compile the SDK source files, which creates a DLL, or plugin.

  • This is awesome, fun concept. Thanks for including the source, it was interesting to have a poke

  • This is unfortunately a known problem with the application runtime. As of yet there's no indication as to what it is, but Ashley will hopefully be debugging it soon, as it is a priority.

    Sorry for the inconvenience.

  • Delete the object holding a the first loaded sprite. Feels to me like all the other object sharing that sprite, refer to this base one. And deleting the first one feels buggy. Spared me a lot of crashes.

    This used to be the case, but a new system ensures that this should not be a problem.

    Make triggers and conditions in 1 event. The triggers should be always on top of the tree, the conditions should be sub events.

    Is there any particular reasoning for this? It's fair enough if you want to do a 'switch/case' style event, with multiple subevents, but otherwise it'd be rather convoluted.

    Leave 's p a c e s' in objects names, layer names, even behavior names.

    This is unintended, if you find a way to put spaces into names then post it as a bug, it shouldn't be possible.

    Overall I'd say that currently - in this build - the Picture Editor is fairly buggy (though this will be reverted for 0.96.2), that there are some problems undoing certain things, and that there's issues when moving/deleting alot of private variables, layouts, etc. These will all be adressed soon though.

  • Picture Editor has some changes which crash on some graphics cards. It'll be reverted along with some other fixes for 0.96.2 fairly soon.

  • I don't understand what you wish to edit.. if you insert some conditions and actions with parameters, you can click the parameter and edit it without going through dialogs (hover over it then click).

    Python allows total flexibility with text-based editing, if that's what you want.

  • Whilst there does always seem to be some problems with the Picture Editor, I can happily say that the problems of this build are not permanent. The system behind it was changed to use float coordinates, which do not work on some graphics cards. Many people can use this build with no problems. Next build reverts the system so all the new problems and crashes are gone.

  • An All-Inclusive Animations Editor. That way, people won't have to search Constructs entire interface to figure out how to change things like animation frame rate.

    Personally I think the Animator fits in with the rest of the UI; you click an animation, you see its properties. Maybe there should just be more tutorials.

    Also, maybe the animation speed system could be altered slightly so that you can have one frame of an animation show at a different rate than the other frames ... basically a different speed for each frame, instead of just one speed for the whole animation. Or a frame delay, if you want to do it that way.

    Click a frame, then change its speed. It's not a delay, but allows for slower frames.

    I've noticed that there is a rectangle outline tool and an oval outline tool, but Where is the Filled Rectangle tool ? ... and the Filled Oval ? .. they are just like the outline tools but make it filled in.

    Click Rectangle, then see the styles at the top.

    I also noticed that you've gone with the Eraser method instead of the simpler more efficient and much quicker method of erasing by drawing with the transparent color. If some people like the eraser fine, but it would be nice if you would include the Erase by Transparency method as well.

    And I know that has to be an extremely simple fix, since the flood fill tool can erase with transparency already. Yet for some peculiar reason, the pencil and brush tools won't erase by use of the transparent color. Please please fix this. It really does save alot of development time to not have to switch back and forth to the eraser all the time. I erase as frequently as I draw.

    I agree with this <img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile" />.

  • The HTML object I think is only meant to display formatted text; not HTML pages.

    Someone would have to write a plugin to utilise IE to display webpages.

  • As Arima said, control held while dragging is a standard mechanism to copy things - in both editors - and there is no plans to change this.

    The context menu could do with a revamp; it's missing standard commands, I agree.