2019-10-17 (Th) PillarGame IoTHackDay

The bottomside of the table was never very attractive to anyone who wasn't interested in automation. Covering the whole thing with a table skirt seemed the best option, and I had seen them many times at display tables at conventions and the like. Most of the time, maybe all of the time, table skirts were held in place with a strip of hook-and-loop sewn onto the skirt and adhered to the table. This might work out fine, but if folks are working at the table, and resting their arms and wrists on the edge, it will abraid skin quickly. I opted for snaps that held the fabric and table together at all eight corners.
Snaps installed in tabletop

Snaps installed in the table used a wood screw while the fabric side required a hole to pass a rivet. It might have been fine to make a gap with a nail or an awl, but I had a leather punch that cleanly cored the fabric. My downstairs neighbor probably didn't enjoy the hammering, though.
Leather punch punching holes in the fabric

After making a hole, I used the hammer to form the snaps with the included tools. The first time I tried, the snap was loose, so I bunched up some of the fabric, which looked more professional, added strength, and provided material to grip. I could have bunched up even more skirt.
Snap installed in fabric

When all the snaps were installed on the table, and the skirt, I attached everything and pulled in the slack with magnets. This was a temporary fix, so I could see how it all looked.
Table skirt temporarily held with magnets

Some of the brown tabletop surfaces peeked over the skirt, even with magnets in place, so that border will need to be colored. I was happy with the result.
Desired outcome

First time here?

Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6

Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com

This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.

All information in this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property, or similar, is the responsibility of those involved in the replication.

All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by  Brian McEvoy, cannot be used to claim property or assets.

Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.

This blog, including pictures and text, is copyright to Brian McEvoy.