poor documentation


Closed Thread
Results 1 to 4 of 4
  1. #1
    Join Date
    Oct 2004
    Location
    Hangover, Germany
    Posts
    289

    Angry poor documentation

    Today, I received my new PBP 2.50 on CD and a new printed manual. Each part cost several Euros.

    But again - the documentation is lousy !
    On melabs website there is the version history with
    "Adds Define to disable/enable interrupts for Write."

    But, where the hell is the documentation to use this feature ?
    You must look inside the *.libs ...

    Next time I will begin a new project - with swordfish !
    PBP 2.50C, MCS+ 3.0.0.5, MPLAB 8, MPASM 5.14, ASIX Presto, PoScope, mE mikroBasic V7.2, PICKIT2

  2. #2
    Join Date
    Mar 2003
    Location
    Commerce Michigan USA
    Posts
    1,166


    Did you find this post helpful? Yes | No

    Default

    BigWumpus , Can't you read? Look at page 204 under DEFINE WRITE_INT 1. All the command does is disable any interrupts when you are writing to eeprom locations. I'm sure
    Swordfish documentation is lacking just as much. That's why there is a forum....

    Dave Purola,
    N8NTA

  3. #3
    Join Date
    Oct 2004
    Location
    Hangover, Germany
    Posts
    289


    Did you find this post helpful? Yes | No

    Angry

    Just look on page 162 - 5.87. WRITE - nothing !

    Use the online-Reference in MCS - nothing !

    Look inside all the README.TXTs - nothing !

    This is not the first time I'm looking for DEFINES - they are documented very poor.

    My english is not so good to write more angry things, I made my decission for me, and one of them is to give swordfish a change, not Proton.


    Next time I may start writing about the CONFIG-trouble (18Fxxxx).
    PBP 2.50C, MCS+ 3.0.0.5, MPLAB 8, MPASM 5.14, ASIX Presto, PoScope, mE mikroBasic V7.2, PICKIT2

  4. #4
    Join Date
    Nov 2003
    Location
    Greece
    Posts
    4,116


    Did you find this post helpful? Yes | No

    Default

    BigWumpus is right at least in part of it.

    If one is going to search the official site of MELABS he won't find the new manual. So if I would like to upgrade my version, should I make it blindly just because I "trust" the good old MELABS? Or should I check at least the new manual before buy?

    I know, the cost of the upgrade is not much for many (or few) but why bother to?

    I still believe it is a good product for what is advertised to do. And the people behind it are just like me I guess, not of the markenting guys! Too bad, if I may say, because there are so many users of the compiler, waiting very anxiously to obtain the new release and the documentation, in general, from the site presentation to the users manual fails short from the expectations.

    Ioannis

Members who have read this thread : 0

You do not have permission to view the list of names.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts