Bradley Korth

When I set a new random seed for [decide], the first result is always 0. This does not happen if I use [random 2] instead. I've provided an example to prove it.

button

number

counter

message

random

decide

Several times, if I'm using Max in Windows 10, when I open a subpatcher in the [p] object, occasionally there's an extra margin to the right of what I'm doing. It also makes it such that if I create a new object, the suggested list covers what I'm typing. The cables also seem to have a little glitch in connecting, but they do work. The fix I've found is to open the Inspector Window, resize the top of the subpatcher window, and close the Inspector window. That seems to always fix the issue. I do not think I've ever had to deal with this issue on the Mac version.

When I set a new random seed for [decide], the first result is always 0. This does not happen if I use [random 2] instead. I've provided an 

two-bugs-i'd-like-to-report-decide-and-subpatcher-window-problems

fun fact: in older versions of [decide] under windows any default (system time) seed starts with 1. :)

i forgot to mention that it is 20:01 AM here.


i forgot to mention that it is 20:01 AM here.

:)


Two bugs I'd like to report: [decide] and subpatcher window problems