Re: wxAssert problem in the cseditor code on windows

> Hmm, I've searched high and low on the web, but I couldn't find a
> reliable piece of information that could help me make msys prefer the
> Perl installed in windows to its own version.

I'm not sure that it will be enough, but maybe you just need a new call to
'./configure' in order for it to detect the new Perl SDK that you
installed, then 'jam msvcgen'.

> But isn't the
> testing of the modifiable entities going to take place in that editor?

The test application for it shouldn't depend on cseditor, just like the
current varedittest application does.

The GUI generation tool is an independant tool class, therefore the test
application shouldn't need the cseditor framework in order to test it.

> Then again, the bugs won't really stand in our way, and the api will be
> just as easy to use in a re-made editor, so I guess that's not really
> important right now.

Yes, several of the problems you mentioned may not be present in the new
implementation. We'll look at that once it is up and running.

> So from what I've understood, we're not going to tie the work I'll be
> doing to the actual editor program too much, right?

Not for the start, because the cseditor is not ready yet, but we'll try to
do it ASAP so that you can start working inside it.

But once the iModifiable is OK and that the GUI generation tool is ready,
then you would start using the cseditor framework in order to implement
the particle editor as a cseditor plugin.

> And regarding the discussion between you, jorrit and sueastside - this
> is about the shared GL context for multiple 3D views in a single
> application you guys were talking about something like a month ago?

No, we let this problem on the side for now.

The current discussion is about the list of improvements that have to be
made over the current cseditor API that is in the 'loading' branch. You
don't have to care that much about that currently, Sueastside and me
should be able to manage that by ourselves. We'll warn you whenever this
becomes interesting for you.

> Also, what's the word on upgrading to wxWidgets 2.9? Should I
> switch to it for my project?

Yes, we plan to switch to 2.9, therefore you can already start using it.
For your project, the most interesting part of 2.9 is the wxPropertyGrid
library that is now integrated in wxWidgets and that you should use for
the GUI generation tool instead of the one shipped within varedittest.

We are also planning to use several other new features from 2.9 such as
the better Unicode support and the binding of events.



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/