Upgrade Designer user interface

I know this sounds silly but Is there any

plan to make the Designer more modern?

a lot of real state not being used.

This is a fascinating question to me, because a lot of the feedback we get on our user interface is exactly the opposite - that it's too dense/hard to parse.

Can you give any specific examples of areas where you feel real estate is not being used?

On the general question of "are you improving the designer", the answer is, yes, all the time, but it's a real ship of theseus - there will almost certainly never be a single massive rewrite that touches every single part of the designer in one fell swoop, because even with an unlimited AI budget there would be untold numbers of regressions. What we do instead is continuously revamp older workspaces and "touch points" in the Designer; for instance one thing a lot of people will appreciate a whole lot is that transaction groups are now a "proper" tabbed workspace in 2027, which was a massive change under the hood.

4 Likes

I work in MANY development environments for SCADA systems. Ignition is by far the best in my opinion.

If I were to give feedback on an Ignition UI that could be improved it would be the Reports Module. Yesterday I had to migrate a report with 22 columns to that and it was a bit of an adventure.

With the advent of AI, it might be cool to have an in-house tag import tool that imports tags from any SCADA into Ignition. This can already be done with external AI so it would probably be easy to accomplish in house.

2 Likes

Personally I'm fine with the conceptual layout of designer but I really dislike that every module has its own layout, like how much designer jumps around when you switch between modules. Simple example is if I expand the named query field and go to open one there's a 0% chance I can just double click on it because everything jumps as soon as I move from one module to that module with the first click.

It would be nice if all the property editors, pipeline block editor, etc would all get merged into using the same window so the layout can stay more consistent when moving around the project.

Also small things like why tools restricts launch project for vision / perspective unless you have those modules selected. If the modules are active what is the downside to having both options available anywhere in the project?

7 Likes

The per-workspace split definitely made more sense before we essentially standardized on the tabbed resource concept (also, there used to be a lot more "exclusivity" around resource locking.

I'm sympathetic to the idea, though it would be a pretty significant refactor of the designer. Maybe someday...

And some of us 3rd parties would suffer....

even if the modules maintain different layouts, I think what he said about double clicking is an issue a lot of people deal with.

just making it so that the project browser sizing applies to all modules would be a huge win IMO. I feel it makes much more sense to have the project browser size be fixed to what the user sizes it to and have all other module specific things like tag browser, vision property editor, property Inspector etc. share the rest of the area

@paul-griffith maybe something inspired by this so that everything is available all the time.

I'm joking if course.

18 Likes

Yeah that'd alleviate a lot. If I pull up the project tree a bit to enlarge it then click off it shrinks back to its size in the other module.

Perhaps they could add a view -> sync window sizes across modules options where if I resize the project tree then it resizes its height across all of the modules? Then they can stay separate behind the scenes but at least it adjusts all of them together.

That is annoying, but even more so is how the tree itself jumps around and collapses when switching between views/queries.

1 Like

that's what we are talking about the project browser is the tree, each module remembers the tree layout so the tree resizes to the saved size of whatever module you are in. you could technically stop it by opening every module and sizing the tree to the same size on each. IMO the modules should share tree height

edit - I'm wrong I see you are talking about something different with the video you uploaded on the attached link

Yeah, it's buggy within a module, not just across them.

I never knew Bing's previous name, Dogpile. You learn something new every day! It concerns me that Bing is at the top in this though. You're never going to find anything

2 Likes