Schlappi has black and silver versions of many modules here: https://www.modulargrid.net/e/modules/browser?SearchName=&SearchVendor=685. The standard for Schlappi in the browser here is silver, with black panels listed separately for most modules.

I added a black panel version earlier today, since my beautiful chrome-on-chrome panel was destroyed by some heartless cretin who decided that not only is black the standard, but that my hard work creating a black panel version should be undone with a "DUPLICATE PLEASE REMOVE". I have of course undone that vandalism.

Nice as it would be for the panel selection functionality to work properly, it doesn't; everyone who's had their manufacturer panel for, say, Pamela's New Workout suddenly and surprisingly replaced by a one-off black panel is aware of this. It would be ideal if the panel selection feature anchored to an official version, perhaps, but it does not. So, we have this solution in lieu of that.

Black/Silver panels are not listed as duplicates across the rest of ModularGrid. Add the black panel version to your rack if it's important to you.

See further discussion:
- https://www.modulargrid.net/e/forum/posts/index/11726
- https://www.modulargrid.net/e/forum/posts/index/8/page:8
- https://www.modulargrid.net/e/forum/posts/index/11176
- https://www.modulargrid.net/e/forum/posts/index/8571 (suggests consolidation 2 years ago, fails to address the panel selection issues since then).

TL;DR: either consolidate all modules or none, forum fights are boring.


great modules btw, praise be to Lord Schlappi. cheers

ℹ︎nformation source | Bandcamp | YouTube


The official modulargrid admin has provided the solution: consolidate modules that are functionally the same but merely have different faceplates, and just use the provided Panel Selector tool to switch between versions.

https://www.modulargrid.net/e/forum/posts/index/11176


The official modulargrid admin has provided the solution: consolidate modules that are functionally the same but merely have different faceplates, and just use the provided Panel Selector tool to switch between versions.

https://www.modulargrid.net/e/forum/posts/index/11176
-- sibilant


You'll note that I linked to that thread above. From that post:

chaos215bar2PM Posted: Jun 8th, 00:30 Quote
It’s a problem when you have multiple racks. See above.


That was not addressed. If the panel selector doesn't work across racks, and it doesn't even work when copying and pasting a module across racks, then it is not a sufficient solution. This would be why many manufacturers continue to add multiple panel options as separate modules.

If panel selection can be made "sticky" per module per user, that would be fine, and duplicate versions of modules could be cleaned up. That would help a lot with database efficiency.

As it is, I've had modules change in existing racks, and as you can see in the other posts I linked as well as the one you linked, so do other users. Manufacturer's submissions get overridden unless locked to the manufacturer... which leads users with alternate faceplates to create duplicate modules. Same problem again.

ℹ︎nformation source | Bandcamp | YouTube


So what you're saying is that even though you recognize that there is a solution (the Panel Selector), because the solution is somewhat inconvenient, you feel entitled to exacerbate the larger problem of adding entries for functionally identical modules that differ only in their panels.

Edit: I guess it's a moot point now; the entry in question has been removed.


So what you're saying is that even though you recognize that there is a solution (the Panel Selector), because the solution is somewhat inconvenient, you feel entitled to exacerbate the larger problem of adding entries for functionally identical modules that differ only in their panels.

Edit: I guess it's a moot point now; the entry in question has been removed.
-- sibilant

A solution that leads to further problems isn't a solution, as has been made abundantly clear. Panels don't persist across racks, and they don't even consistently stay unchanged within racks when new panels are added. The workaround continues to exist because of this, continues to be used for other Schlappi modules, remains standard practice for some manufacturer-locked submissions, and is the sole way to get aftermarket panels on to MG for manufacturer-locked modules.

You yourself have felt entitled to exacerbate what you call a larger problem at least twice yourself, so you're clearly neither unaware of the impacts nor unwilling to implement workarounds when it suits you. Perhaps mentioning it in the Feature Requests thread linked above would be productive, since the issue is ongoing and will continue to affect users every time somebody uploads a new panel for any module.

ℹ︎nformation source | Bandcamp | YouTube