# Using "Cards" style in URCap installation is bad design?

**URL:** https://forum.universal-robots.com/t/using-cards-style-in-urcap-installation-is-bad-design/23304
**Category:** URCaps SDK
**Created:** [August 17, 2022, 7:24am UTC](https://forum.universal-robots.com/t/using-cards-style-in-urcap-installation-is-bad-design/23304 "2022-08-17T07:24:37Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![ldk](https://avatars.discourse-cdn.com/v4/letter/l/ecc23a/32.png) [@ldk](https://forum.universal-robots.com/u/ldk)
#### Post date: [August 17, 2022, 7:24am UTC](https://forum.universal-robots.com/t/using-cards-style-in-urcap-installation-is-bad-design/23304/1 "2022-08-17T07:24:37Z")

</div>

The [Style Guide](https://plus.universal-robots.com/media/1802558/urcaps_style_guide-v10.pdf) states that you “Don’t use a Card inside of another Card”. I agree that this would be bad design. However I find it hard to adhere to this rule. The reason is that when overriding the buildUI() method, I cannot get rid of the default insets of the JPanel object that is provided as a parameter.  
So since the URCap installation panel itself is a Card, then even the “outermost” Card that I design in my installation view will indeed become a Card within another Card.

Trying this in the `buildUI()` method:

```auto
jPanel.setBorder(BorderFactory.createEmptyBorder(0,0,0,0));

```

throws

```auto
com.ur.swing.AuthorizationException: Method not supported from URCaps

```

Has anyone gotten around this?