Heated Debate... Features and Updates and Things...

[mister_e]

Mike you can still save few bytes if you remove the FOR NEXT and replace it with a variable increment and a IF THEN to check the value... i guess 4-6 bytes will be saved.

Depending of your sourounded code, you can also use some PBP macro too.

Nothing is mpossible... but only with a few lines snip...

I have to say after reading these posts for some time now I can only conclude you all must have more time than money.

That's one of the most dangerous thing i never see here. I think that

I have to say after reading these posts for some time now I can only conclude you all have a great knowledge because you can built and share all your stuff yourself with a minimum of code space and you don't need anything else to do it. Meant Math-processor, other compiler and such. Nice job guys!!!

is more appopriate .. just an idea

[mytekcontrols]

Mike you can still save few bytes if you remove the FOR NEXT and replace it with a variable increment and a IF THEN to check the value... i guess 4-6 bytes will be saved.

Mister_E thanks for the info, unfortunately I decided to scrap the whole approach for what I was doing and implemented it in an entirely different way, which saved gobs of bytes (counting changes in surrounding code) and made my life much easier (this is always appreciatted). When I get it into a more final form I'll post it.

Thanks again,

P.S. I like your version of what that guy probably really meant to say :-)

[OXIMBIT]

In case you did not realise I was being sarcastic. For a company to sell this product for so much that offers so little when there are cheaper products that do more for less I think is ......... But If your prepared to pay the price and jump through all those loops trying to implement features that should have been there in the first place is up to you, it's your money.

By "more time than money" means your you prepared to spend all that extra time doing workarounds than spending the money on better product.

[Darrel Taylor]

<img src="http://www.pbpgroup.com/files/dejected.gif"><br>Added 7/2/05: See, I just knew this was going to happen.

[Acetronics2]

By "more time than money" means your you prepared to spend all that extra time doing workarounds than spending the money on better product.[/QUOTE]

The only probem is to sell ...

What ??? that's not a problem ... shiny adds and whatever the "thing" makes : that's in the pocket.

Nowadays, selling a sparkling project is easier than selling a well engineered product ...

doesn't make me laugh at all ...in the end

Alain

[Melanie]

In case you did not realise I was being sarcastic. For a company to sell this product for so much that offers so little when there are cheaper products that do more for less I think is ......... But If your prepared to pay the price and jump through all those loops trying to implement features that should have been there in the first place is up to you, it's your money.

By "more time than money" means your you prepared to spend all that extra time doing workarounds than spending the money on better product.

Firstly, it's only a problem for those who don't know how (and here you have a simple choice, learn, or move-on elsewhere). Secondly, once you have those routines, you don't need to reinvent the wheel the next time you need them. But most importantly - and this counts for more than price-point or frills and features, is that the MeLabs offering is a well designed, RELIABLE, STABLE and MATURE product. You can design your project safe in the knowledge that it will do what you intend and expect it to do. Some competitors products go through more bug fixes and revisions in a single year than the MeLabs product has in it's entire history - that's kinda worrying and not something to be proud of. On an occasion when I used a different compiler, my MD refused to release the product until I had rewritten the software excluding it. His argument centred on RELIABILITY and TRUST which was worth far more than any other adjective you could apply in favour of the competitors compiler.

If I was a hobbyist, especially one with limited skills, I'd have a completely different set of criteria. I would want a product that has every bell and whistle built-in, and costs next to nothing. Reliability would not even enter into my thoughts. There are a lot of products out there that meet that criteria. More "time and money" as you mention is then spent chasing your tail wondering if the reason that your project doesn't work as expected is down to your code, or is it due to a bug in that all singing and dancing compiler?

[Acetronics2]

Hi, Mel

I'm a pure Hobbyist ... who flies models.

You will surely agree reliability is the first thing I'm waiting from PBP ...

I can say, I never had bad surprises ( exept my own beginner's errors ...) with PBP.
It's really a great tool ... and I can enhance or modify it myself !!!

But I agree it needs a little (really little ! ) learning time, that's a good thing nowadays to learn, instead of stupidly paste already done work ...

No other compiler offers that ...

Alain

[bot402]

When you have a product that hasn't actually changed in 5 years its easy to make it stable, especially if it doesn't actually do a great deal in the first place, and even then what it does is bloated, outdated, and inefficient. But where would we be if everything was like that. We'd still be driving Model T fords, and forget Television, the Internet and all the other offerings that have had to briefly go through the "not so stable" stage.

I'm just glad that everyone doesn't have that blinkered approach to things, or progress would come to a grinding halt!!!!!