# XOD 0.25.1 issues

**URL:** <https://forum.xod.io/t/xod-0-25-1-issues/1287>\
**Category:** Uncategorized\
**Created:** [October 28, 2018, 5:17pm UTC](https://forum.xod.io/t/xod-0-25-1-issues/1287 "2018-10-28T17:17:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![gweimer](https://avatars.discourse-cdn.com/v4/letter/g/a9adbd/32.png) [@gweimer](https://forum.xod.io/u/gweimer)\
**Post date:** [October 28, 2018, 5:17pm UTC](https://forum.xod.io/t/xod-0-25-1-issues/1287/1 "2018-10-28T17:17:04Z")

</div>

This has been a problem for a while: Select File \> Switch Workspace. The window that comes up has an “X” to close it, but it doesn’t work. There is no way to abort switch workspace except to browse to the current workspace and re-select it, or exit XOD.

Shift-left/right labels pin “BYTE”, but it is a number.

There is no automatic casting of byte-\>number or number-\>byte (but there is u8-to-number & number-to-u8 as work-around). Was it a conscious decision not to auto-cast or did it just get over-looked?

---

<div class="post-metadata">

**Author:** ![nkrkv](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.xod.io/nkrkv/32/8_2.png) [@nkrkv](https://forum.xod.io/u/nkrkv)\
**Post date:** [October 29, 2018, 9:15am UTC](https://forum.xod.io/t/xod-0-25-1-issues/1287/2 "2018-10-29T09:15:59Z")

</div>

Hello!

> [@gweimer](#):
>
> There is no automatic casting of byte-\>number or number-\>byte (but there is u8-to-number & number-to-u8 as work-around). Was it a conscious decision not to auto-cast or did it just get over-looked?

It is by design. Byte is a datum for storing/transferring data in general, whereas the number is a _value_. There’s no unambiguous way to convert a byte to a number and back: it might be a signed conversion or unsigned:

- `80h` — is it `128.00` or `-127.00`?

> [@gweimer](#):
>
> Shift-left/right labels pin “BYTE”, but it is a number.

Yeah, that’s a legacy bug. The argument is left with the type `number` for easier handling of multi-byte numbers where bit carrying matters. However, the implementation is still incorrect as of 0.25.1. Will fix it, thank you.

---

<div class="post-metadata">

**Author:** ![nkrkv](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.xod.io/nkrkv/32/8_2.png) [@nkrkv](https://forum.xod.io/u/nkrkv)\
**Post date:** [October 29, 2018, 9:39am UTC](https://forum.xod.io/t/xod-0-25-1-issues/1287/3 "2018-10-29T09:39:46Z")

</div>

Created an issue for the shifts: [https://github.com/xodio/xod/issues/1510](https://github.com/xodio/xod/issues/1510)

---

<div class="post-metadata">

**Author:** ![gweimer](https://avatars.discourse-cdn.com/v4/letter/g/a9adbd/32.png) [@gweimer](https://forum.xod.io/u/gweimer)\
**Post date:** [October 29, 2018, 11:54am UTC](https://forum.xod.io/t/xod-0-25-1-issues/1287/4 "2018-10-29T11:54:20Z")

</div>

Seems it would be reasonable to assume BYTE is unsigned and auto-cast. If that is the wrong answer, programmer can add node to force correct casting. I can also understand design decision to not assume since it might create difficult-to-find bugs.

I only noticed these issues because my byte-to-bit library node is broken because there was only type “number” available when I created it & now bitwise-and BYTE pins are incompatible with “number” pins on bit shift nodes and my output pins.