https://www.scirra.com/tutorials/73/sup ... reen-sizes

Summary -

1. Use letterbox scale - design for any aspect ratio you want (easy, lazy, black bars)

2. Use scale outer - design to allow users with wider screens to see more of your background/layout

2. Use scale inner - design keeping in mind users with narrower screens will get portions cut off

Either way, I generally like to start designing with the squarest aspect ratio in mind.

I believe a single value in construct uses a 32 bit float, or roughly 2 billion. If you need more than that you can use a second value as a multiplier, so 2b squared. You can probably accomplish an infinitely scaling number system by pushing out an array whenever you need to. The bigger design decision for you would probably be how to represent this number on screen for the user.

Edit: never mind, construct uses doubles, so your maximum number is 9007199254740992.

After a certain point the lower digits won't be significant at all so it probably wouldn't matter anymore.

Construct.net, it is web based. You'll also get the first year for free if you got c2 recently.

Maybe preview on LAN with WiFi?

Or try it on the Construct 3 beta that is running right now, since you'll be able to use C3 on your phone.

Regarding second question, for If you want only N-M, set the sliderbar minumum to 13 and maximum to 14.

Another way might be to have an event at the end, if sliderbar is >14, set to 14. If less than 13, set to 13.

Your problem is caused by event 60.

You may want to add the condition to only have that event run if SliderBar isPlaying is True.

The new start page is a bit painful. I'd like recent projects to be on top/open by default, but I can understand the rationale for demos/showcases to be on top.

Good - Easily accessible examples and tech demos! Thumbnails are good to have. New Templates!

Bad - Browsing through examples is a pain, due to the thumbnails. Can only see 1.5 items at a time, and there are a lot of them. Edit 2: I found this was because my screen/layout was JUST not wide enough to have the thumbnails next to the description. Instead the thumbnails get stacked vertically. Hope this gets tweaked.

All the grey buttons are important/useful, but have to scroll to see them on my monitor. Hopefully there can be a emphasis on showcases as well.

Edit: In terms of what a new user should see, I think the beginners guide (both of them, top down shooter and platformer) should be prioritized with the highest emphasis. The manual would probably be second, with a special mention towards How events work (I still have trouble navigating to/finding this page myself. I usually just search for it, but that only works because I know what I'm searching for. Considering how important it is, I think it should be more easily accessible.)

If a third beginner's guide/tutorial were to be considered, I'd like to nominate the vertical space shooter template as a good candidate for an entry level project. Or maybe just updating the end of the ghost shooter tutorial to recommend studying the vertical space shooter template on their own as the next step.

I'm no expert, but rather than the pathfinding algorithm itself that is improved, I believe the gain is from the control you get over how the movement is implemented.

I think that is mostly it for now, and as I continue testing if I encounter anything else that particularly bugs me I'll write about it.

I apologize for the wall of text, but to put things in perspective it could have been a hundred times longer had I been writing about C2, except most of the issues I would have griped about were already addressed. I think Construct is already an excellent product I just wanted to close out with a thank you to the Construct team for the great job done and many improvements in C3. I have had a mostly positive impression of C3 amidst the negativity that has been floating around. I hope that my suggestions may possibly be of some use to further improve Construct in the future.

Animation Editor!

I find it a little frustrating that the toolbar to the left switches between Animation Properties and the Color Palette depending on what tool is selected. Particularly when real estate is mostly available as there really are not too many animation properties. I'd like to suggest the Animations Properties be docked on the right either above or below the Animations List. Makes sense to me, especially as they are related. Then the left toolbar can always have the Color Palette open.

This leaves us with the Image Points dialogue. I feel like this is a huge feature that is hidden behind a tiny button. I think something should be done to make it a bit more prominent, maybe having it's toolbar always open as well, docked below the Color Palette. But then it might start getting too cluttered... Also related to the image points, is that a fairly common problem is when someone moves the origin point for one animation frame and not the others. Maybe there could be some way to present the "Apply to whole/all animations" more prominently as well. By the way, thanks a ton for the new quick assign option!!

Additionally, I think it would be nice to have the option to show all imagepoints at once, maybe as a toggle. They can be differentiated by color or shape, like how the origin looks different from imagepoints currently.

For the Color Palette, !PLEASE! allow for the picker to be constrained to the palette and continue picking even when the mouse is not over the palette! This behavior is already implemented in the new configure grid color popup dialogue. This allows for more precise picking of colors around the edge of the palette (the ones I'm aiming for 90% of the time). I feel very strongly about this, and it is literally one of the first things I noticed when I started using C2 5 years ago. When Construct is described as a "tool for artists", it is especially noticeable.

A minor thing I think would be nice also would be to include one more row of swatches above the palette - a preset row of basic primary and secondary colors.

A huge request would be layers and transformations with tweening support, but I understand that isn't exactly easy, so I'll leave it at that. But I will add that it's something I definitely missed coming from Flash. (Shoutout to Spriter here for saving the day!)

Regarding the tabs - There may have been a specific reason it was made like this that I overlooked, but I really dislike this tab system (no disrespect meant to the original designer). I also know this could be an impactful workflow change, and some people might not welcome any changes.

It isn't really scaleable when more layouts and sheets are added. I know you can close them and find them again in the project bar, but it is clunky. The frustration is further compounded when opening multiple projects - there is no real way to tell which "Layout 1" belongs to which project, and they can get mixed up. Furthermore, closing the tabs for a certain project doesn't actually close that project, and then you have to find it in the project bar, which has the additional challenge of identifying the correct one in the event that they are all named "New Project" with "Layout 1".

I always made an effort to open separate projects in separate windows in C2, and was hoping this could be default behavior. I suppose in C3 each project would be its own browser tab instead. Alternatively, maybe separate projects could have their own tabs in the C3 interface rather than each layout and event sheet.

My proposal for solving the clutter would be to have dropdown list boxes for layouts and events instead. An example from a CAD software here:

As each layout is by default tied to an event sheet, when a layout/sheet is selected in their respective list, the other box could change to the relevant layout or sheet as well. This would hopefully also reduce confusion about which layout is tied to which sheet.

I'm going to assume this particular suggestion will be a bit contentious as it involves workflow changes and more than a little bit of work on the backend, but do hope it will be considered. Also I'm sure I missed some positive aspects from a different point of view, so maybe some other users can chime in regarding that.

EDIT - I played around with the interface a bit more and I think I understand a little better now, that event sheets and layout tabs can be docked anywhere on the interface just like toolbars (This was somewhat possible in C2 in a much more limited manner. I never realized it could be done until just now, after 5 years of use though...). I guess if that is something that people will take advantage of I can see why they are tabs. I will still say that it isn't immediately clear that this is possible - even where the toolbars are stacked and have tabs they are on the bottom, rather than the top, so I don't immediately make the connection that they are treated the same way.

I do also want to second the mention that the rounded tabs look really out of place with the rest of the overall look and design.