Bug #1309

externals.loading.test cause a number of warnings

Added by Trond Lossius over 6 years ago. Updated over 6 years ago.

Status:RejectedStart date:2013-01-27
Priority:NormalDue date:
Assignee:Théo de la Hogue% Done:

0%

Category:-Spent time:-
Target version:MVC for 0.6
Branch:0.6-alpha OS:

Description

Hi Theo,

If I open Modular/Tests/integration/externals.loading.test.maxpat with CMD + SHIFT down (in order to prevent loadbang from firing), I see a few warnings in the Max window:

jcom.return: needs a name as first argument
jcom.parameter: "view/freeze" is not a valid attribute argument
Jitter initialized
jcom.out: Jamoma cannot registers multiple object with the same OSC identifier (out).  Using out.1 instead.
jcom.in: Jamoma cannot registers multiple object with the same OSC identifier (in).  Using in.1 instead.

I suppose some of the objects need arguments to avoid these warnings, right? Am I right that the node-related objects really need an additional argument (name of the node), and that jcom.out and jcom.in are also nodes? If so I'll add arguments as required to them. However it might be ab idea that we do a merge of master into this branch first to make sure that we do not end up with any conflicts.


Related issues

Copied to Max - Bug #1552: externals.loading.test cause a number of warnings Closed 2013-01-27

History

#1 Updated by Théo de la Hogue over 6 years ago

  • Status changed from New to Resolved
  • Assignee changed from Théo de la Hogue to Trond Lossius

yes it was due to a lack of arguments and a problem inside the jcom.paramui (no more view/freeze attribute for internal jcom.parameter so this freeze feature needs to be fixed, if the jcom.paramui remains a useful external in 0.6 (?))

I've made a commit to remove the errors/warnings. Is it good for you ?

#2 Updated by Trond Lossius over 6 years ago

  • Assignee changed from Trond Lossius to Théo de la Hogue

I've made a note of discussing jcom.paramui at the next BOD.

I couldn't find the changes you did, are you sure that they have been pushed? I'm at the 0.6-alpha branch.

Cheers,
Trond

#3 Updated by Trond Lossius over 6 years ago

  • Status changed from Resolved to Rejected

Also available in: Atom PDF