My fear is that all these native implementations will become very hard
to maintain. What happens when Qt 4.2 comes out and the person who
did the original Qt impl is long gone? (this is just for arguments
sake of course). Native tools seem better left to developers creating
their own apps. The t
Hey, glad it might actually be of use to other people. I know I've
been awful about finishing things, as anything that doesn't directly
relate to my thesis has fallen to wayside as of late. When I was
investigating saving it as an XML format, I remember coming across a
problem. If I remembe
Dear Abraham,
I'm sorry it's taken so long to get back to you. I didn't see any other
responses on the list, but I think this is a super idea (although I have
yet to look at the code). In particular I like your idea to save to your
XML format. Then we could plot to an XML file, and replot (later)
Darren -Although I agree with your on some level, the advantage of the current toolbar is that it is easy to incorporate in a GUI, where the user can define his own drop down menu. So I vote for a backend native slider, but keep the button on the toolbar.
I have been thinking about an easier way t
Christopher Barker wrote:
> Darren Dale wrote:
>
>> Travis says that barring the discovery of some issue during the beta period,
>> the C API will not change before numpy-1.1. I think an exe may be necessary
>> as well.
>>
>
> and an OS-X mpkg, if you're set up to do that -- also, we'd ne
> "Charlie" == Charlie Moad <[EMAIL PROTECTED]> writes:
Charlie> Are they any lingering issues that would prevent a
Charlie> Wednesday minor rev bump for the latest numpy? Ideally
Charlie> it would last through the numpy 1.0 release.
Since scipy is next week, we should concentrat
On 8/7/06, Christopher Barker <[EMAIL PROTECTED]> wrote:
> Darren Dale wrote:
> > On Monday 07 August 2006 08:55, Charlie Moad wrote:
> > Pushing a
> >> release now for 1.0 might be pointless, since the C-api could possibly
> >> change and break compatibility again. After all, it still is a beta.
Eric Firing wrote:
> I think the following (now in svn) should be OK; it seems to work on
> Windows, at least in the sense that it doesn't trigger an exception.
>
> nan = struct.unpack('d', struct.pack('Q', 0x7ff8))[0]
It works on OS-X PPC also. I was wondering about endian issues.
I am writing to ask about the subplots adjust widget. I think the gui would be
better implimented by each backend using the native widgets rather than by
the existing set of backend-neutral sliders, which are somewhat unbecoming.
The proposed backend-specific widgets could call the generic subpl
