You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 18, 2023. It is now read-only.
now i'm a big fan of showing boilerplates and use them extensively in my own libraries.
however, i also see the concerns of those who feel like being drowned in unsolicited noise.
therefore, I'd like to suggest to not display the boilerplate whenever a new object ins instantiated, but instead reduce the number of shows to a single one.
this can most easily be achieved by moving the call to purest_json_lib_info() from the object constructor (e.g. rest_new()) to the setup function (e.g. rest_setup()).
an alternative is to use a static int firsttime=1; flag, but i don't see much benefits to do that.
The text was updated successfully, but these errors were encountered:
since you talked about doing a new release i thought it time to report this minor issue:
whenever an object from the library is instantiated, a nice boilerplate is displayed in the Pd-console:
now i'm a big fan of showing boilerplates and use them extensively in my own libraries.
however, i also see the concerns of those who feel like being drowned in unsolicited noise.
therefore, I'd like to suggest to not display the boilerplate whenever a new object ins instantiated, but instead reduce the number of shows to a single one.
this can most easily be achieved by moving the call to
purest_json_lib_info()
from the object constructor (e.g.rest_new()
) to the setup function (e.g.rest_setup()
).an alternative is to use a
static int firsttime=1;
flag, but i don't see much benefits to do that.The text was updated successfully, but these errors were encountered: