Let me start with I overthink a lot of things!
I have seen some projects delivered by an integrator that use labels as spacers between components, I have also seen this in use on the ignition template projects.
I took the perspective training class and we used margin/padding for all of our layouts.
Is it best practice to use a label over using margin/padding for perspective layouts or is it project dependent?
What do you use and why?
I use margin/padding and gap.
I use Margin/padding because I don't like having a bunch of un-needed components on the views.
I believe I asked this exact same question before because it's a method I've seen used in early IA-released Ignition projects. It seemed silly to me, so I asked if there was a reason to use them that I'm missing. There was not, as far as I could tell.
Learn padding/margin/gap and you'll be golden.
EDIT: link to my post
My predecessor used that approach a lot, and I clean it up everywhere I find it. If you're using something for a reason other than its intended purpose, then there's always a better way. Use margin/padding/gap, or in some cases I find the best answer is simply picking the right flex layout properties.
I'm using the latest version of ignition 8.1.41 and if you create project using the ignition template they use the labels as spacers. That's what threw me a curve ball as I didn't understand why they didn't use margins/padding.
I have been using margins/padding and wanted to make sure I wasn't missing anything! Thanks
Using padding margin and gap will be more efficient, because when a label is placed, it needs to be rendered by the web browser.
If you have a lot of them your web browser will begin to be slow at each loading.
Margin and padding, just tells to the web browser where to place the component.
And if you use label as spacer, you will have a lot of component in your project tree and the designer will be slower.