i think now i understand what you are saying. you mean the order how the values appear in time. i misunderstood completely, sorry.
so a simple [trigger f f f f f f f f] should do at the input, right?
Am Montag, 4. Juli 2016 schrieb Simon Iten :
---------- Weitergeleitete Nachricht ---------- Von: *Simon Iten* <itensimon@gmail.com javascript:_e(%7B%7D,'cvml','itensimon@gmail.com');> Datum: Montag, 4. Juli 2016 Betreff: bytetobit abstraction An: IOhannes m zmölnig <zmoelnig@iem.at javascript:_e(%7B%7D,'cvml','zmoelnig@iem.at');>
Am Sonntag, 3. Juli 2016 schrieb IOhannes m zmölnig :
On 07/03/2016 09:41 PM, Simon Iten wrote:
dear list,
find attached a really simple abstraction to convert a single byte
value into 8 bit outputs.
thanks for sharing.
it handles higher values gracefully (it just outputs the lower 8 bits)
unfortunately it outputs the bits in a really weird order: 1 3 4 5 2 6 7 8
? works here.
with "8" being the MSB (and leftmost outlet) and "1" being the LSB (and right-most outlet). i would have expected the output to be like virtually any multi-outlet object to be from right to left: 1 2 3 4 5 6 7 8
me too
or to cut it short: why aren't you using [trigger]?
i don't know how obviously. can you elaborate?
you may want to put some additional characters after the name when you
create the abstraction to see all outlets :-) (e.g. bytetobit ……..)
or just drag the right-hand edge to whatever width you like: [bytetobit ]
gsdr
IOhannes