u-he

Urs · Post by **Urs** » Thu Feb 17, 2005 2:18 am

addendum:

One GOOD thing about VC7 stuff is, it understands ansi... it actually seems to know about variable scope... I don't have to convert my loops anymore... I can stick to this:

for ( int i = 0; i < max; i++ ) { /*do stuff*/ }

instead of having to do

int i; for ( i = 0; i < max; i++ ) { /*do stuff*/ }

(which has cost me quite some trouble in the past... with VC6)

Cheers,

Urs

wrench45us · Post by **wrench45us** » Thu Feb 17, 2005 12:45 pm

i've known developers who were good at finding things in msdn and relied on it. unfortunately i'm not one of them.
i do know it's very important to limit the scope of your search to the current language and such

otherwise it's just like a google search and you find all these articles that seem relevant and helpful till it's clear that it's a previous version and things have changed

Urs · Post by **Urs** » Thu Feb 17, 2005 6:42 pm

D'oh... I had another problem... the graphics library was actually a bit slow. Funnily, after some minutes the gui would even slow down more... some stupid memory allocations going on there...

However, spent 2 days writing some faster blitting routines. Which got it pretty close to CoreGraphics rendering. At least, I can't feel any difference anymore

Cheers,

Urs

danielmm · Post by **danielmm** » Sun Feb 20, 2005 4:30 pm

Hi Urs,
Just curious, with all the problems you are having with Zebra Mac/PC conversion...will the PC users be getting the same instrument exactly, or will it be somewhat different?...kinda sounds like a silly question, but there seems to be more stumbling blocks here that can perhaps not be overcome?..just curious.

dano

Urs · Post by **Urs** » Sun Feb 20, 2005 6:40 pm

Hiya dano,

I'm currently out of town, so I can answer only briefly.

Both Mac and PC versions will be identical.

Some stuff might be different, like Menus, File/Registration dialogs etc., but the core (sound...) will be 100% identical.

Cheers,

Urs

Urs · Post by **Urs** » Sun Feb 27, 2005 3:43 pm

Oki,

I've started compiling stuff on the PC

The last days kept me busy, but I'm down to 8 compilation errors from 700+.

Looks like VisualC++ still has some different ideas on the C standard than the GNU compiler. No big problem, I just had to write a shitload of macros to do it this or that way on either platform.

The remaining errors are tied to file handling, menus and text input. As predicted, these areas have to be written now. That will hopefully go a bit faster than integrating the new rendering engine...

Cheers,

Urs

VitaminD · Post by **VitaminD** » Sun Feb 27, 2005 8:29 pm

Urs wrote:Oki,

I've started compiling stuff on the PC

The last days kept me busy, but I'm down to 8 compilation errors from 700+.

woohoo!

700+ wow..

Urs · Post by **Urs** » Sun Feb 27, 2005 9:02 pm

VitaminD wrote:
Urs wrote:Oki,

I've started compiling stuff on the PC

The last days kept me busy, but I'm down to 8 compilation errors from 700+.
woohoo! 700+ wow..

Yeah... especially all those pointers that I had to explicitely cast to void*. Tons of them. Doesn't concern gcc in any way, but VisualC++ literally freaked out about them...

And I had to define my simple c callbacks differently. VisualC++ has no idea what to do when importing a header containing an extern "C" static void callback definition that is not present in the actual cpp file but in another BWAHAHAHAHAHAHA...

Cheers,

Urs

Beardedone · Post by **Beardedone** » Tue Mar 01, 2005 1:59 am

And I had to define my simple c callbacks differently. VisualC++ has no idea what to do when importing a header containing an extern "C" static void callback definition that is not present in the actual cpp file but in another BWAHAHAHAHAHAHA...

Cheers,

Urs

Gee I thought that everyone knew that.

spaceman · Post by **spaceman** » Tue Mar 01, 2005 12:57 pm

Beardedone wrote:
And I had to define my simple c callbacks differently. VisualC++ has no idea what to do when importing a header containing an extern "C" static void callback definition that is not present in the actual cpp file but in another BWAHAHAHAHAHAHA...

Cheers,

Urs
Gee I thought that everyone knew that.

basic knowledge innit

jens · Post by **jens** » Tue Mar 01, 2005 1:00 pm

spaceman wrote:
Beardedone wrote:
And I had to define my simple c callbacks differently. VisualC++ has no idea what to do when importing a header containing an extern "C" static void callback definition that is not present in the actual cpp file but in another BWAHAHAHAHAHAHA...

Cheers,

Urs
Gee I thought that everyone knew that.
basic knowledge innit

that's part of what they teach here in school during the first hear - probably Urs has just forgotten about it...

Urs · Post by **Urs** » Tue Mar 01, 2005 6:32 pm

Yeah, hehehe... sorry for the tech stuff...

However, I'm down to 2 errors, but the missing pieces are still unimplemented.

I'm desperately trying to figure out what crap this is. It wants some stuff fixed that is definately not an error. Probably some misleading compiler info. Really weird. Took me one day to check several options, but no go. I should send Microsoft a bill for the wasted time (no pun intended)!!!

Cheers,

Urs

Beardedone · Post by **Beardedone** » Tue Mar 01, 2005 6:41 pm

Thanks Urs. I for one really do appreciate your hard work. I can't wait to get Zebra onmy PC.

jens · Post by **jens** » Tue Mar 01, 2005 6:59 pm

jens wrote: that's part of what they teach here in school during the first hear - probably Urs has just forgotten about it...

probably one of the most stupid typos I ever did - it's supposed to be 'year' instead of 'hear' (and 'h' and 'y' aren't even close to each other on the keyboard

):help:

Warmonger · Post by **Warmonger** » Wed Mar 02, 2005 7:09 am

Strangely enough, I didn't even notice the typo until you brought it up yourself.

Anyway, I just thought I'd post so I can finally get reply notifications for this thread

. I'm looking forward to trying this out on PC, even though I doubt I'll actually be able to use it.

u-he

KVR Audio

Zebra PC blog