AFAIK almost everything about the way SM has implemented Python is broken. Each and every flavour of GUI has 'issues'... it's a case of pick your problem!

Without doing one program in each GUI and picking which fails less, which I couldn't be bothered doing, I picked Tkinter in 2009 and stuck with it. It works well enough for me so I am not too bothered it's a dead end tech.

I picked Tkinter because I began with P7 and it 'kinda' worked there while wxP was a distant unimplemented upstart.

They all have issues.

If it's not broken Threads, it's a half-*ssed or broken something else that works on PC doesn't on MAC or vice versa.

Not much to choose between them to be honest IMHO.

If something ever manages to work on a multitude of platforms, you can be sure it will be crippled by commercial interests, be bought up and destroyed, be unusable without a degree in Swahili and Urdu or become obsolete pretty soon!

Tkinter is better (if implemented properly in the host program) and compiles to a single file.

Thank you.

I actually had a newer version of the P8 code (1.1.56 rather than the 1.1.55 that's online) to post but since it is now online I cannot update it!

Neve mind.

I wanted to update the previously posted P8 version to the latest 1.1.56.

It was the waiting P9 version (1.1.56) that is the updated version.

Too late now.

Never mind.

Thank you.

I will upload the latest P8 version soonest.

The P9 version can be put online as and when the P8 goes in the queue.

Q. Why two?

A. Simple. No choice.

My software can only be released as two separate versions because of design flaws in Poser9/PoserPro2012 and the way in which it handles standard Python.

Most programmers won't come up against them because they don't write software of sufficient rigour or sophistication to encounter the defects in the two implementations in Poser. After only a weekend's trial, I know the GUI implementation and the way Threading works, as well as the memory usage, are significantly dissimilar between Poser versions but I can do nothing about it. I only write Python. It's not my job to fix Poser itself!

These bugs in P9/PP2012 mean that the P9 version of my software can ONLY work on the PC version.

Whereas the P8/PP2010 version works fine, as testers tell me, on both PC and MAC versions.

Since compliled Python ONLY runs on the system version that compiled it, so a P8 version won't run on P9 and vice versa, so there will always be a separate P8 edition and a P9-PC edition.

To avoid offering P9-MAC users two copies of software, neither of which they can run... two clearly labelled versions are more logical and more legally defensible.

Since nobody wants two copies either, makes more sense to separate the software into two versions.

Also allows me to make a back-compatible P7 version (already tested and working albeit Threadless so less pretty!) if the screaming crowds demand it. Nobody has so far so not a priority at the mo.

IF SM had written P9-MAC edition to use a better version of Python OR Python was back-compatible re. compiled versions of code, this problem wouldn't arise. We always seem to be suffering at the hands of unseen, incompetent others in the computer industry, such is the developer's lot. C'est la vie!

Thank you for your help re. release of DrPoser.

DH

Facebook types... remember to unfriend me, y'all!

I am unable to ascertain the truth of your statement since I do not own a copy of P2012/P9.

Just because some script that uses some of TKinter appears to work means little to me until I see my script working on it.

Since I just finished hand-correcting 180Gb of Poser content for a client to deliver nr zero-defects over a year's casual unpaid work, using my script as a guide, and since my software has been working for 12 months for me without problems, having withheld the script for political reasons re. u.s. conduct, I tend to believe my own hype more than anyone elses.

But then that's just me.

You'll perhaps have it when I feel ready. Not before.

It works for me and I have no pressing need to ever release it.

Personal rep tends to mean little to me. I earn elsewhere and can afford to write for my own pleasure. I tend to get by without peer adulation just fine.

ZERO defects in your Poser Runtime is possible.

The speed boost is phenomenal.

It makes a difference!

Why do you think I wrote DrPoser?

Hi

thanks for the feedback so far.

DrPoser will NOT be available under P9/2012 since I don't own a copy, and is unlikely to be ever compiled under P9/2012,

AND

P9/2012 has major GUI issues regarding TKinter in Python that haven't been and probably won't be resolved.

P9 is, as far as I'm concerned, probably NEVER going to be supported.

My software is nr perfect. The Python implementation in P9/2012 is fucked nr totally bitch-shaped and I have no power to correct that.

As for magic numbers on the .pyc, until I get a copy of P9/2012, I cannot compile DrPoser for the latest version and it serves as a good cut-off point and limitter anyhow.

My script works with P8 and with P7 (albeit more slowly and less multitask-ishly) and may be supported by P10/2014 in 2 years or so, if the past is a guide to the future.

Retail release soon.

DH

I use Firefox. I'd rather kill than use IE.

I have no intention of uninstalling and re-installing anything.

BTW I have actually run a company helpdesk... 'reinstall' is what one tells the annoying customers, the ignorant plebs, to brush them off when one is on the phone. There's always a fix for the registry or a patch that fixes it properly. If the programming team can't be bothered... the policy becomes "you need to uninstall X and reinstall Y and..."

Legally, it makes the problem the user's. G*d forbid it become's the software vendors!

Perhaps it's easier to hand-edit JavaScript to force it to 'return 9' as I originally intended!

So no real fix then.

As I suspected.

Thanks anyway.

DH

We ALL have too much free time!

Isn't THAT the entire purpose of Western civilization... to give free time to the masses?

And while some use that free time to buy stuff, some to make stuff, well some of us use it to wonder about the buying and making!

Happy Christmas...

... one and all!

Not come across wardrobe wizard... I'll check it out.

Brilliant model and texturing.

All we need now are some decent victorian/edwardian underwear (bloomers/chemise/corsetry) for V4 modelled on the real thing (as above)?

Victorian/Edwardian hair styles would be nice too... I do so get fed up with all these short, brutal modern unisex cuts!

Anyone? =8-)

You can, of course, edit the files so that you can put the morphs anywhere you please. They are, after all, only text files and so readable and quite easily understandable once you realize that on a PC you open them with wordpad rather than notepad and save them once so that you can read them back using notepad later.

Get a tool called MorphManager, load up the character however large the file and delete the morphs you don't want from it then save the result (actually a big text file) as a new character. It's out there someplace! However, I haven't used it in ages but I did once make some morphless figures for pose testing and for de-morphing poses. I don't know if it works with the new texture format in P5/P6 but it could handle mutiple figures in a set in the same file.

Sorry.

Thought it was obvious.

Since all you need is the lengths of the bones and the angles returned by the sensors, all the rest of the mocap positional data can be calculated with simple math.

It won't record anyhting like fluid motion but it would make stop motion anim MUCH easier.

Message edited on: 12/27/2004 09:10

Message edited on: 12/27/2004 09:12