@Alger Is this close to what you want?

Download polnew.mw

It works OK for me, without any workaround needed, in the 64bit verion of Maple 2015.0 on Windows 7 Pro.

It would be interesting to know whether it's specific to Win8.1, or 32bit Maple, or other.

acer

@Alger Please explain in more detail what you mean.

@Alger I don't see why what I gave does not do what you've asked.

Here below the colors red and blue are switched, as you have them.

You write cos(theta) but perhaps you intend cos(freq*theta), for some freq. You write you want the axis to be at radius R, but your image shows a curve entirely within the circle. That's obtained by just adjusting my code by 1, in the axial direction.

Please explain more, if it wasn't actually what you wanted.

Download algerplot.mw

@Christopher2222 Yes, that was the first of the three plots I showed by example.

@Kitonum I could be misunderstanding of course, but where the OP wrote ".mw" I interpreted it as meaning a query about behaviour in the Standard GUI (as opposed to .mws which I might interpret as a query about behaviour in the Classic GUI, or both).

Which style: detached, grouped, or stacked?

acer

@mapleatha it worked fine for me, using the Java GUI of Maple 13. Why don't you describe exactly what you're doing, and in which interface and input and output mode, instead of just wasting time?

Here's a screenshot of it working for me in 64bit Maple 13.02 on Windows 7. Earlier in the day it worked for me using 64bit Maple 13.01 for Linux.

@nm Using a DOS window under Windows 7: (This is one long command, of course. I split it across two lines of text here just so that it displays nicely in this post.)

c:\TEMP>"C:\Program Files\Maple 18\bin.X86_64_WINDOWS/cmaple.exe"
         -q -c "print(int(sin(x),x));" -c "quit"

                                    -cos(x)
c:\TEMP>

Using cygwin (and this one also worked using /cygdrive/c/ instead of c: in the fully qualified location of cmaple.exe): (Again, this is just a one-line command.)

$ "c:\Program Files\Maple 18\bin.X86_64_WINDOWS/cmaple.exe"
  -b "c:/Program Files/Maple 18/lib/" -q -c "print(int(sin(x),x));" -c "quit"

                                    -cos(x)

Those worked for me with Maple 2015 as well.

@mapleatha Why are you not updating to the 13.02 point-release?

There is an item "Startup Code" in the "Edit" dropmenu off the main menubar of my 64bit Maple 13.02 running on Windows 7.

What operating system and particular point-release Maple version are you using?

acer

@jockoflocko Ok. So did you configure Maple to find the vcvars64.bat file from the MSVC++ compiler when you installed Maple 17. Or did you instead configure it afterwards, by running the Compiler:-Setup command? Which MSVC++ version did you install, and which Visual Studio version?

It may not be related to your problem, but are you still running Maple 17.00? And if so then have you considered getting the 17.02 update?

By the way in Maple 18 and 2015 the LLVM C compiler comes bundled with the 64bit Maple product itself, on each of the MS-Windows, Linux, and OS X platforms. Hence Compiler:-Compile is ready to go, with no downloads or configuration necessary.

What version are you using? Is it Maple 17?

What operating system? MS-Windows or Linux or OS X? And 32bit or 64bit Maple?

acer

@Carl Love Some years ago I wrapped up something very similar into a procedure which I called findroots. I mention it because, for a requested range a..b, it invoked NextZero with an option like maxdistance=b-start rather than just maxdistance=b say.

It looks to me as if your code is intended to restrict further searching if any root is found above bound 10000, because of the while condition on the loop. It doesn't make a huge difference for this example, but it might be that there is some benefit (speed or robustness) by using an option maxdistance= 10000 - R[k-1] rather than maxdistance= 10000 in the NextZero call. The endpoint 10000.0 might need it's own examination, but that's relatively very cheap.

Just an idea.

I think that NextZero has improved over the years. I don't see why fsolve couldn't be amended to call it as a method, possibly while offering the maxsols option for input other than just univariate polynomials. The whole business of repeatedly calling fsolve & its avoid option, as used by Student:-Calculus1:-Roots, is a bit sad.

@Alejandro Jakubi Of course customization is possible, but in my experience there are very many users who want and expect their own favored functionality model to be the default.

When I wrote "thorny dichotomy" I was thinking of the problem that users can and often do want greatly differing and opposing defaults from each other.