It's from the Unity 5.6 Update.

However like newt said, we already have that in C2.

We don't though - 9-patches don't rotate properly, and it's impossible to edit their collision polys so they're always square. 9-patches are meant more for GUIs than objects in-game.

I am wondering if there's a way to detect the layout edge? Anyone got a quick tip?

I see we have is on screen and is outside layout, but no touching layout edge? Seems like a really simple feature that should be built in.

There's the "Bound to Layout" behavior, to keep objects in layout, but agreed having something to reference to see if you're near the edge would be handy.

Pretty self-descriptive, but you know, adding rotation properties for individual particles to the particle plugin, rotation speed, angle (and rotation speed) randomisation and all that stuff. This could really improve Construct particles.

And while we are at it, let's go nuts, why not animated particles too?

Seconded. Construct particles are pretty behind the times.

glerikud

You just hit at least half of my issues. This is a good list. Usability improvements are needed to better compliment the existing functionality.

Tackla

It would be easier and less events if you just make all the bubbles one object and change the animation to set the color of the bubble if they all have the same behavior.

Like so:

Congrats2u

1- Put the GUI objects you want to fade on their own layer

2- In the layer properties, set "Force own texture" to yes for that layer

3- Set the blend mode for the fade sprites you have at the edge of the screen to Destination Out

4- Make sure the fade sprites are the top objects on the layer

(I'll count myself as an expert in as well).

To be honest, I don't mind the text in the blank event sheet at first, since from the moment you add an event to it, it disappears and is not to be seen again.

It is like a graffiti in the empty event sheet, and even adding a comment makes it go away.

As for the tooltip/field helpers, they are freaking helpful and preventing from having to go dive in the manual for a quick refresher when needed.

Especially for the kind of objects you don't use everyday, or come back to later in your development.

Sure for common actions/conditions they are "useless" after a while, but honestly it is easy to focus on the field(s) and not even pay attention to the small line on top of it.

I think the suggestion of having them grayed is actually giving them more focus on top of making them harder to read if you want/need to, which in the end defeats both purposes.

Kyatric

(I'll count myself as an expert in as well).

To be honest, I don't mind the text in the blank event sheet at first, since from the moment you add an event to it, it disappears and is not to be seen again.

It is like a graffiti in the empty event sheet, and even adding a comment makes it go away.

As for the tooltip/field helpers, they are freaking helpful and preventing from having to go dive in the manual for a quick refresher when needed.

Especially for the kind of objects you don't use everyday, or come back to later in your development.

Sure for common actions/conditions they are "useless" after a while, but honestly it is easy to focus on the field(s) and not even pay attention to the small line on top of it.

I think the suggestion of having them grayed is actually giving them more focus on top of making them harder to read if you want/need to, which in the end defeats both purposes.

Kyatric

I didn't ask for them to be greyed out. I asked for an option to hide them entirely although in an earlier user's post, if the grey was darkened a little bit, would be better than black text on solid white - right now the help text just kind of blends in with the editable form fields, so as it stands it's not as good as it could be in terms of visual clarity or defining a hierarchy of importance (help text is not as important as functionality). I don't need to be reminded of what "compare two values" does on a per-field basis. The name of the event is descriptive enough. While that's just one example, that extends across all events. If I get stuck, I can always turn them back on - maybe a hotkey toggles them? - or open the manual. Aside from needing to point out that not expecting people to read the manual is insanity, but that's another topic. Outside of being distracted by their prominence in C3, I can't remember the last time I actually read any of the hints. So it'd be nice to get rid of them. Maybe the CSS will be clean enough that it'll take just a few changes to hide them globally? That'd be good, if it's a feature that isn't going to be added in by default. Other than a dark skin, which is kind of expected these days because black on white is so hard on the eyes, that would be my first change once it's possible.

It's a pretty common feature in both development IDEs and many other widely-used applications that are designed for a broad audience made of both beginners and more experienced users. At a certain comfort level, users just don't need to be constantly reminded about what does what, y'know? Imagine if every time you rolled over an icon in Photoshop, it presented you with a highly-detailed description of what the tool does and what it's designed to be used for. That's what this feels like in C3.

Anyways, since C3 is in testing I figured I'd bring it up. I thought about mentioning it in C2 but with C3 being an IDE rewrite it made sense to wait. Obviously there are more pressing issues.

Well, like I said, I made the software (hopefully that counts me as an expert user?) and I still think it's handy to have them there. For example when you focus the Volume parameter of a Play Sound action... is it in dB or a ratio? Positive or negative? Honestly, sometimes I even coded it and can't remember what I did. The tip clears it up: it's dB attenuation, so ought to be negative, or 0 for full volume. That kind of thing is always useful IMO, whoever you are.

Ashley

I've never, ever done that, because I read that it was dB and have never forgotten it's dB. Or that X/Y coordinates start in the top left. Or what # IDs represent what buttons on a gamepad. I can't imagine anyone who's spent a significant amount of time with Construct or other development software not being able to do the same. I understand your point (somewhat) but at the same time, I run Photoshop, Illustrator, After Effects, 3DSMAX, etc. with the interface hidden 99% of the time, that software all has quite a bit more to remember than Construct hotkey-wise, and it's never been an issue. Less clutter is always good, and unnecessary text is clutter. Plus, you've already got a "Help" button plastered across every feature, so is it really that much of a concern to constantly remind people if they don't want to be reminded?

As someone said above, it seems to be a target audience thing. Hence the request for a separate mode for a more advanced audience. "Always" is a strong word, because it's not really always when you just want a reminder on occasion. I wouldn't really mind C3 looking a bit less like a beginner's toy and having large prominent help text every step of the way going all Microsoft Paperclip on users isn't helping.

How about having it like it is, just for the free version?

Take the training wheels off for the subscription.

I can see value for newcomers in having this stuff in there even after subscription, but I would also like to not have to see it myself.

I get that Construct is supposed to be easy to use and all that, but I'm not sure I really need the extra descriptions on event popups or the event sheet itself. This seems to be an ongoing concern throughout C3 and honestly, that help text just takes up space in popups and I don't really need to see it every time I create an event sheet. I can't imagine anyone who's coming from C2 does.

I'm referring to this:

I know this text was also present in C2, but it's so prominent in the new look and feel. As a side note, there sure seems to be a LOT of wasted space under the fields:

Having an "Expert" mode that rids the interface of reminders of what we meant to do in the first place would be pretty great. After all, if we need help, there's already a help button.

What features are missing? I get that you can't use them because it's locked to free edition right now, but they are going to be ready for testing in the last week. We're confident at the end of the beta everything will be working great and we'll be comfortable to start selling it.

Cool. I'll try it again when they're available .

EDIT: Maybe...those features will take longer than a week to test? Just a thought...

>

> > What's been released as the C3 "beta" is very obviously an alpha. And that's fine, but mislabeling it (not to mention putting such a hard limit on accessible features) means that, even for just messing about with it, it's not entirely worth the effort right now. Hopefully we see an actual beta in the near future, prior to the release of the commercial version. Right now it feels very...meh. I'm not excited by C2 in a browser in the slightest, especially since right now it seems to be more an inconvenience than an upgrade. I guess we'll see what happens!

> >

>

I mean Alpha/Beta are all fuzzy terms. We did run a private alpha before the beta. We're happy to call it a beta. Expect rapid improvements.

They didn't used to be fuzzy terms . Beta used to mean feature-complete with some bugs, and it doesn't feel feature-complete right now. I think the biggest issue with what's publicly available for C3 is how locked-down it feels, even compared to the free edition of C2. Some of the usability seems a step down from C2 as well. I'm sure it will improve over time. Right now it's a bit underwhelming to say the least, though I'll admit part of that is because of the lack of third-party plugin support (currently) that adds features that I've found to be absolutely necessary to make Construct a complete and functional development tool (raytrace, canvas access, some filetype import options, etc).