ppstudiomty's Forum Posts

  • I'm working in the scrollview just right now, and I was wondering if anyone has any specific concern or feedback about what you expect from a scrollview.

    By now I've already covered the following for it:

    Minimum expected:

    • Scroll content clamped to scrollview size
    • Children interactions are limited to scrollview quad
    • Vertical, Horizontal and Both movements are supported as well as Mouse-wheel scrolling for the first 2.
    • Swipe gesture with inertia supported
    • Actions: Scroll-to-position (relative and absolute), and Scroll-to-object (child object) are available

    New

    • Scrollview behaves like a container, inheriting all its characteristics (focus, navigation, cascade enabling, etc.)
    • Scrollview uses dynamic layers, creating them over the Scrollview original layer, then moving its contents to the new layer, automatically setting up clipping.
    • Behavior Properties can be set by actions
    • In Process Scrollviews use scrollbars to displace its content. The new scrollbars can be use as sliders, and as scrollbars with value-set buttons

    If anyone there has suggestions over these, I really appreciate them.

    Some Screenshots of the ACE's

  • Unfortunatelly no with current Construct's capabilities, I may need to hack the engine which is what I'm totally avoiding to keep the addons alive for as long as possible. ScrollView will work in the same way than ProUI's did.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I'm working on it testing thoroughly. I'm also planning a closed alpha, thus the community will be part of the testing process too. As I come up with the details I'll post about it. :)

  • Thanks for your support! In the short term, I'm developing the same UI addons and capabilities that ProUI have, that includes the ScrollView. My design, from the technical aspect, is completely different from ProUI, although both solve the same problems. SmartUI is highly integrated with Construct 3 available and documented features, so that should protect us (the devs) from breaking-changes longer than when using undocumented features. It handles zIndex interactions (when components overlap), focus handlers to cycle through components, and more.

    I already have 8 addons running and in testing:

    1. SmartUI Plugin (framework and navigation capabilities)
    2. Buttons Behavior
    3. Checkboxes Behavior
    4. Radio Buttons Behavior
    5. Dialogs Behavior
    6. Progress bars Behavior
    7. Scroll Bars Behavior
    8. Containers Behavior(new addon)

    The ones in process are:

    1. Scrollview Behavior
    2. Gridview Behavior

    Addons will be also fully documented on my website, I'm creating tutorial videos, and testing them thoroughly.

    I'm also planning a closed alpha testing. As soon as I have the details I'll post about it too.

    I don't have the launch date yet, but I'm aiming for this year to publish all the addons.

    You may want to check the vids:

    Subscribe to Construct videos now

    And the thread I started about SmartUI:

    construct.net/en/forum/construct-3/your-construct-creations-9/smart-ui-framework-construct-183210

  • New Tutorial Video for Progress Bars:

    Subscribe to Construct videos now

  • ICYMI, I'm working on this:

    Subscribe to Construct videos now

    For anyone who may be interested.

    construct.net/en/forum/construct-3/your-construct-creations-9/smart-ui-framework-construct-183210

  • great idea not gonna lie

    Working on it! :)

  • Thanks! I actually took all what I would like to have in a UI. I'm also looking for feedback on what components and features people look for more often in a UI, so feel free to leave your thoughts.

  • Some videos of the current state of the addons:

    Push Buttons

    Subscribe to Construct videos now

    Radio Buttons

    Subscribe to Construct videos now

    Dialogs

    Subscribe to Construct videos now

  • mOOnpunk thanks for the report. I updated the blog post. I will also upload some videos of the functionality that's available already. :)

  • Smart UI is a framework and a set of addons developed with the purpose to simplify the UI design and build in the game engine Construct 3. The framework is still in development but has already reach a stage where the addons and the design components are fully usable to create functional UI's.

    The framework came from the need of upgrading the existing tools and addons from Construct's SDK v1 which has evolved into the SDK v2, introducing breaking changes and forbidding backwards compatibility for the tools developed by the community. Therefore, I decided to develop my own framework, highly integrated with the current SDK and aiming to live for long to keep my game projects running for several years. Compatibility with the SDK v2 is a major challenge, considering that the current state of the SDK is still in development, but with a stable version already rolled out.

    As part of this project, I've been reporting multiple bugs that Scirra, who has been resolving them swiftly, allowing me to move on and complete the milestones I've set for these addons, while helping the Construct 3 community to have a more stable SDK in the process.

    youtube.com/playlist

    Subscribe to Construct videos now

    If you have questions or suggestion, feel free to drop a message or leave your comment. I'd like to know how many devs would be interested in these addons.

    Read the full article here: wp.me/parV9i-s0

  • Initialising ProUI stops the game (maybe crashes?) since the new C3 version!

    Today, the latest stable version came out: construct.net/en/animation-software/releases/stable/r397

    When I worked on my game, I noticed that something went wrong, the main menu's code was not executed as it was before although I did not touch it. I quickly found out that the ProUI Initialise function is the problem. When I deactivate it, the rest of the code is executed. When its active, it gets stuck there and is not going to the next line of code.

    The same project runs fine in the last stable build: construct.net/en/make-games/releases/stable/r388-2

    so something must have gone wrong in the communication of this plugin and the latest stable build.

    You must stay on r388.2 to be able to use ProUI, it's part of what scirra decided to break with the new SDK v2.

    • Post link icon

    > if your worry is that you want to keep opening your projects in r388, you will still be able to do that

    And this is what most 'big' developers will do - stay on r388 forever.

    I'm saying forever, but in fact it won't be a long term solution. This means no official support, no bug fixes, no new features. If WebView2 becomes available on Mac and Linux - we won't get it. A new version of NWJS is released (which requires updated Steam plugin) - we won't get it. Scirra adds Switch export (haha, I know) - we won't get it. Google or Apple introduce some breaking change - we won't be able to export for mobile. And so on and so on.

    Exactly! Yet people is still thinking that r388 LTS is the solution. Ashley already stated LTS won't have support forever... eventually, our long term projects that uses undocumented features won't open. With his latest reactions, what's the real guarantee that he won't change his mind later on. This whole SDK v2 thing came from a simple question to access engine internals 2 months ago, which suprinsingly rushed Ashley to launch v2.

    The real solution will be to allow SDK v1 to coexist indefinitely, at the same time rolling out v2, or creating Construct 4 with all the new architecture for further projects, instead of thrashing the existing ones.

    • Post link icon

    No one has ever said anything about older versions ever becoming unaccessible.

    I'd better have Ashley to clarify that, it must be an official pronunciation from Scirra, not from the community devs trying to make conclusions. We must have a guarantee that it will work permanently at r388, and that all our old projects will be able to access the internal features to freeze any updates to the lates c3 stable on our side when this goes live.

    Here's some quotes of the milestones:

    Milestone 4: Construct will remove support for SDK v1 addons. The addons will no longer be loaded in the editor, and projects using them will fail to open and report that the addons are not supported and need updating. This will be at least 6 months after milestone 3 (and so at least 12 months after milestone 2).

    Construct will ultimately drop support for the Addon SDK v1, so addon developers should consider starting updating their plugins and behaviors to use the Addon SDK v2.

    skymen None of the quotes above indicate that what I state won't happen.

    Ashley's comments about LTS.

    It's infeasible to keep supporting one version forever. Eventually we will have to stop supporting it. As far as I'm aware nobody else in the industry supports LTS versions forever - everyone has some schedule of eventually retiring old LTS versions and introducing new LTS versions, sometimes with overlap between them. The question is what schedule is being proposed here

    Ashley please clarify.

    • Post link icon

    What about all the private addons that were made for ambitious productions ?

    This is exactly what Ashley doesn't seem to understand. Theres already games live that had used a private addon to surpass a C3 limitation, those projects may have an income committed, and Scirra is killing them abruptly. I'm sure any addon used by those projects will be kept up to date and won't break "customer's projects", which is the main reason Ashley is giving to deprecatr sdk v1. I have several private addons too that I use in my live games, those games have revenue, killing the sdk v1 will be a catastrophic action because of the simple fact that I can't go to the an older version of construct because sdk v1 will be totally retired. Those projects are expected to live for several years ahead. Using older versions with permanent backwards compatibility is the industry standard, which construct won't provide.

    Ashley you are going against what the industry is doing. Look at Unity Hub, I can still access older versions of the engine and keep my games running. Scirra is deciding to unsupport that compatibility? Even when addons like funky quads, which used unsupported features, paved the way for you to introduce 3d capabilities. Scirra is forcing devs to invest time and money on a tool whose reliability and support to the community is in question because of decisions like this. Even when these addons leveraged the popularity of the engine and Scirra got the benefits of it. It feels like a shot in the back. The good will of the community to expand the engine and help your company is being directly aggravated by this.