bevy_independent_transform 0.1.2

Entities with an IndependentTransform have a position relative to their parent, but aren't part of the Bevy Transform hierarchy.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67

# bevy_independent_transform


[![crates.io](https://img.shields.io/crates/v/bevy_independent_transform)](https://crates.io/crates/bevy_independent_transform)
[![MIT/Apache 2.0](https://img.shields.io/badge/license-MIT%2FApache-blue.svg)](https://github.com/ickshonpe/bevy_independent_transform)
[![crates.io](https://img.shields.io/crates/d/bevy_independent_transform)](https://crates.io/crates/bevy_independent_transform)

Entities with an `IndependentTransform` have a position relative to their parent, but aren't part of the Bevy Transform hierarchy.

With `Transform` :

![image](/assets/dependent.png)

With `IndependentTransform`:

![image](/assets/independent_text.png)

Supports Bevy 0.8

## Setup

Add the dependency to your `Cargo.toml`

```toml
bevy_independent_transform = "0.1"
```

and the plugin to your `App`

```rust
fn main() {
  App::new()
    .add_plugins(DefaultPlugins)
    .add_plugin(IndependentTransformPlugin)
    // .. rest of App
    run()
}
```

## Usage

`IndependentTransform` is a newtype wrapping `Transform`.
Like `Transform`, an entity with a `IndependentTransform` should also have a `GlobalTransform`.

You can insert an `IndependentTransform` component directly, or spawn one of the bundles included with this crate:
* ```IndependentSpriteBundle```
* ```IndependentSpriteSheetBundle```
* ```IndependentText2dBundle```
* ```IndependentTransformBundle```

If an entity has both `IndependentTransform` and `Transform` components, the `IndependentTransform` component will be ignored.

## Examples

```
cargo run --example text
cargo run --example sprites
```

## Notes


For an alternative that respects the Bevy transform hierarchy, see my other crate at

https://github.com/ickshonpe/bevy_fixed_sprites

The approach here seems better for text and game icons, and bevy_fixed_sprites is probably better for sprites representing 
game characters and objects.

I'm not sure how to combine both methods. Maybe it's not possible without introducing a lot of complexity and extra components, and/or replacing Bevy's `transform_propagate_system` system
entirely. Haven't really thought about it much though.