Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

doogiePIM Stability Issues

#17

While doogiePIM has given a bit of a face-list to it's original software (Do-Organizer by GemX) -- it has exactly the same stability issue (i.e., bug) and that is -- when a Selected Event is modified (rather than an entire series), perhaps a different comment or moved to a slightly different time. Or perhaps a Selected Event has been deleted because of a one-off occurrence.

When the application is closed and re-opened the changes are random. Often the deleted Event (one of a series) will reappear; instead of just the new Event -- the User will see BOTH old and new events.

This instability makes your Calendar unreliable. A rather fundamental problem for PIM software. This bug made it's way from the old version of Do-Organizer to the new and improved(?) doogiePIM.

It seems to have something to do with the fact that there's no specific "SAVE" action for changes to the database.

Reported by Carl Porch · January 19th, 2017 @ 02:02 AM

State: resolved
Milestone: 1.0.6
Assigned to: BiteSpire BiteSpire

Activity

  1. BiteSpire
    BiteSpire
    • State changed from new to open

    Status: Bug confirmed. Pending immediate fix.
    Scheduled: 1.1 rc

    Thank you for reporting this. This is the kind of feedback I really like. These old bugs that plagued the doOrganizer base code need to be addressed. Many other problems have been fixed and I can see there will be the odd glitch, as in any software, that exists. Be assured, development continues.

    If you require further assistance or wish to report other anomalies please submit a new ticket.

    Kindest,
    Chris

    January 19th, 2017 @ 08:00 AM

  2. Carl Porch
    Carl Porch

    This is a problem that I lived with for a long time, but gradually turned me off of doOrganizer. Glad to see it's getting attention.

    I always felt that it had to do with the attempts to make doOrganizer memory-resident, as well as constantly saving changes and having no definitive "Save and Exit" process.

    I think that if you did away with allowing the program to be memory-resident and flagged the database as dirty once changes have been made (prompting the User to "Save Changes" upon exit) and then actually exiting. You'd be way ahead of the game.

    January 19th, 2017 @ 04:26 PM

  3. BiteSpire
    BiteSpire
    • State changed from open to resolved

    Status: Possible resolve in version 1.0.7

    Work has been done to the internals of recurring events. Especially on the edit and deletion. These changes came effect in the latest version 1.0.7. Please try this version and let me know if the problem persists.

    The download for version 1.0.7 can be found here: https://bitespire.com/download.php

    January 25th, 2017 @ 05:30 PM

  4. Carl Porch
    Carl Porch

    I agree. Version 1.0.7 is much more stable. Initial testing looks good. Will continue to use and let you know if I see any problems.

    January 25th, 2017 @ 07:05 PM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.