I am trying to initialize an object with 10 parameters and I'm getting "Too Many Arguments Error", Why?

I am trying to initialize an object with 10 parameters and I'm getting "Too Many Arguments Error", Why?

This is only after compiling that I get the "Too Many Arguments Error"

For example:

timeLabelOffset = new TimeLabelOffset(78, 46, 78, 79, 73, 76, 78, 67, 68, 78);

Thanks.

  • I'll also point out that the forum is supposed to be here for the users and not the other way around. (Although in reality, Garmin is actually getting free labor from users.)

    So if there's a usability problem, it should be on Garmin to find ways to nudge people towards the "right" behavior.

    One example is the New button (for creating a new thread) that used to appear on every existing thread -- people would often click on this button when they actually wanted to reply to a post. The effect would be that every few weeks or so, somebody would create a new thread for a CIQ app which was actually supposed to be a reply to an existing thread. The response would always be the same: "Nobody knows which app you're talking about. Please respond to the existing thread in the showcase or press Contact Developer".

    Notice how that behavior has been reduced by a lot now that Garmin has removed "New" from existing threads? (I still see it every now and then, though.) It still seems to sometimes appear if you click on the "latest comment" link on the right of each thread in the forum thread list. That's probably why we still occasionally see accidental new posts which were supposed to be replies every now and then.

  • I have some old threads that still gets valid posts.  Here's one from 6 years ago as an example. The latest post was 3 months ago.

    https://forums.garmin.com/developer/connect-iq/f/discussion/5156/1hz-watch-faces---q-a

    there are lots of old threads that have valid info years later.

  • https://forums.garmin.com/developer/connect-iq/f/discussion/5156/1hz-watch-faces---q-a

    there are lots of old threads that have valid info years later.

    The irony is that Garmin broke all the inbound and outbound forum links when they changed forums platforms a couple of years ago, so:

    - other old threads which refer to that thread have a broken link to that thread

    - A post written by you on Garmin's own blog has a broken link to that thread

    As I said, perhaps a compromise would be to lock old threads based on the age of last activity. Again it's not going to change so it doesn't matter what I think.

  • there are lots of old threads that have valid info years later.

    Yet the fact that they're not locked doesn't prevent people from creating duplicates.

    ¯\_(ツ)_/¯

  • Notice I said to use the magnifying glass at the top.  It's a much better search than "ask a question"

  • Notice I said to use the magnifying glass at the top.  It's a much better search than "ask a question"

    Thanks, I know how to read, and I also vividly remember you carefully explaining how to use the dead-simple forum search functionality multiple times in the past.

    Guess you're missing my point. My point was that you are criticizing people for not actively searching for duplicates.

    My point was that during the process of creating a new post here, the forum will automatically show you posts which may be duplicates.

    If automatically displaying duplicate posts doesn't deter people from creating a new post, it's probably too much to expect every user to actively search for duplicates before posting. In this case, if I start to post about "too many arguments", the forum suggests several duplicates, yet obviously it wasn't a deterrent for this post.

    It should be blindingly obvious that the "suggested duplicate posts" feature was created because people don't usually bother to search for duplicate posts. Nonetheless, it's obviously ineffective. Maybe it's a good idea, but the UX needs to be refined? For example, when the user presses Post, the forum could once again show possible duplicates and ask them to confirm their post. That would probably be too annoying.

  • So it looks like the forum doesn't suggest duplicates on mobile. Maybe that's part of the problem.

  • And speaking of UX, it looks like the "New" button still consistently appears on all existing posts when you click the "latest post" link, on mobile. Another usability failure. Probably explains why we still see "accidental new posts" in the Showcase which were supposed to be replies to an existing thread.

  • So to be 100% clear, my focus is not on "how can we lecture any particular poster on the 'right' way to post?" but "how can Garmin change the forum UX on both mobile and desktop to avoid issues like duplicate posts and accidentally creating new posts instead of replying."

    We can educate existing posters all we want, but that doesn't help if the same problems re-occur with new posters over and over again.

    Same as other kinds of problems re-occur over and over again in the CIQ ecosystem.

  • Not having the official documentation include important information like this is a real bummer. I ran into some error related to this max args issue and also had to go deep searching for why.  It would be saved me a lot of time when I read the documentation tip-to-tail to have known this limit.  Now I use the same strategy you do, with an array for the args.  

    Would be really powerful if devs could suggest modifications to the documentation, much like how open source does it.