Thread: Try my journaling program?

  1. #1
    Unregistered User Yarin's Avatar
    Join Date
    Jul 2007
    Posts
    2,158

  2. #2
    Registered User
    Join Date
    Sep 2008
    Location
    DE
    Posts
    17
    I'm trying it out right now, made a bug submission already too :P

    Ok, how do I rename a journal entry viewing it from the main screen (where all the entries are listed.)

    This is a screenshot of the error I produced.

    http://www.freeimagehosting.net/imag...ccaf99ea5e.jpg

    Also...it seems to save that error dialog. I closed the journal, edited environment fonts and it gave me same wall of lots of text error.

    Will try some more later.
    Last edited by sdemaio; 10-07-2008 at 12:06 PM.

  3. #3
    Unregistered User Yarin's Avatar
    Join Date
    Jul 2007
    Posts
    2,158
    Beta 2 is out now.

  4. #4
    Registered User
    Join Date
    Sep 2008
    Location
    DE
    Posts
    17
    Ok, gonna give Beta 2 a shot.

    Edit 1 : The Changes link gives me a 404 error on webpage.

    Edit 2 : PDX4104 Error still present. Won't report it anymore though, I already submitted that bug.
    That "lots of text" error still present also. :P

    Uh, should I keep submitting using your website? Or post here?
    Last edited by sdemaio; 10-07-2008 at 07:01 PM.

  5. #5
    Registered User
    Join Date
    Sep 2008
    Location
    DE
    Posts
    17
    Oh jesus I just made a gem of a bug. Clicking the Undo-Redo started printing "9" or "s29" on the beginning of the entry screen text.

    Also try this.

    Enter an entry such as:

    Error
    Eror

    Spell check it and "Replace" Eror and it prints.

    errorerrorr


    Could you explain what an Exhibit is so I could test that part?

    That "9" "s29" Error I can't seem to replicate now.

    Just got this s29 error to replicate itself by typing some random text choosing random buttons between Bold, Italics, and then hitting undo/redo a few times. It did it when I hit Redo.




    Edit: I made it crash, generate a windows crash report and then it even crashed DrWatson Postmortem Debugger. Is that part of your software or Windows?
    Last edited by sdemaio; 10-07-2008 at 07:25 PM.

  6. #6
    Registered User
    Join Date
    Sep 2008
    Location
    DE
    Posts
    17
    Woot, saved file corruption after that crash !

    Entry 5 turned into...(listed in the main journal entry viewing window).

    "Entry 5 - 255/65535/65535 243:65535PM - 255 Exhibits"

    Oh and it made Exhibit export now possible. Lists 255 exhibits all in format. Number of each exhibit unique of course.

    "Exhibit 90 - - 0 bytes"

    Exhibit 1 however is...

    "Exhibit 1 - - 45277200 bytes"

    So I closed Perodika and tried opening the exhibit I exported with Perodika through Windows "Open With..." Menu. I got this error message when I tried to launch Perodika on it's own after that.

    "Unable to find Perodika's main window.
    Another process may be using Perodika's mutex name."


    Reopening the journal. I got the corrupted entry 5 as...

    "Entry 5 - 255/0/255"

    Exporting that journal entry resulted in a "*.doc" file which I opened with OpenOffice.

    The contents were as follows.

    "30 Journal Path: C:and Settings-test.bjd
    Entry Number: 5
    Entry Date: 255/0/255
    Entry Time: 0:00AM"



    Keyboard Shortcuts. I'm not sure this is a problem.
    Entry Menu. Remove and Reset Timestamp both use R as their button.
    Edit Menu. Cut and Copy both use C.
    Last edited by sdemaio; 10-07-2008 at 07:29 PM.

  7. #7
    Unregistered User Yarin's Avatar
    Join Date
    Jul 2007
    Posts
    2,158
    >> Uh, should I keep submitting using your website? Or post here?
    Either way is fine.

    >> Could you explain what an Exhibit is so I could test that part?
    An exhibit is any file that you import (add) to a single entry. Almost like an attachment with an email. Each entry has it's own set of exhibits. Though probably, they should be called something else...
    I'm curios, have the Help Messages been showing for you? If so, do you think the one on exhibits needs updated?

    >> Spell check it and "Replace" Eror and it prints.
    Yes I see. That is strange, it works fine with anything else I give.
    I may be spending a minute on that one.

    >> Keyboard Shortcuts. I'm not sure this is a problem.
    No it's not. Even so, you're right I should change those.

    >> Woot, saved file corruption after that crash !
    Yup, the journal document got really corrupted. As you may have noticed, the number 255 (i.e. 0xFF) was everywhere.

    >> Edit: I made it crash, generate a windows crash report and then it even crashed DrWatson Postmortem Debugger. Is that part of your software or Windows?
    Well, when I did trial-and-error debugging of my own, this would always happen too. I honestly have no idea why it crashes watson though.

    >> Clicking the Undo-Redo started printing "9" or "s29" on the beginning of the entry screen text.
    I can't make this happen. Could you give a more in-depth description of what you did? When I repeatedly click undo and redo with text in the edit it works fine...

    Thanks for your persistence.

  8. #8
    Registered User
    Join Date
    Sep 2008
    Location
    DE
    Posts
    17
    >> Clicking the Undo-Redo started printing "9" or "s29" on the beginning of the entry screen text.
    I can't make this happen. Could you give a more in-depth description of what you did? When I repeatedly click undo and redo with text in the edit it works fine...
    * I'm trying to replicate it again, it was quite random both times I made it appear. But I'll see if I can nail down a way to do it.

    I'm curios, have the Help Messages been showing for you? If so, do you think the one on exhibits needs updated?
    * They have been, I took my time reading them this time. I'm unsure the value of attaching something to a journal though if Perodika doesn't open it/preview it/or tie it in (insert image into document type thing). The e-mail attachment description helped a lot.

    * Spelling changes.
    First help message when program loads.
    peticular -> particular
    preform -> perform

    Help message on creation of first journal.
    conveniont -> convenient

    Help msg creating first journal entry. Oddly this msg is white background instead of the parchment kind of others. Hmm not exact white but not strong enough like the others.
    varify -> verify


    * "9"/"s29" now made an "015" appear. I typed the alphabet, highlighted it hit Bold, Italics and Undo/Redo many times in between. It was slightly random when it appeared.

    "s15" changed characters style a bunch then hit Redo a few times followed by an undo and then a redo and I think it was the redo that made it appear.

    "0" after hitting Redo. Sometimes you lose the highlight of text while Undoing / Redoing.
    "5" Select text entry, Hit Bold -> Bold and alternate a bit, hit undo then redo.
    "s15" while hitting Undo after Bold, Italics Underline a lot.

    It's definitely related to the Undo/Redo buttons.

    Bold Bold Bold Bold, Undo Redo Undo produced a "5."

    An interesting thing to note is that I tried copy/paste and other text manipulation things and couldn't get it to bug but it was with the B/I/U that it seemed to do it a lot more easily.


    * Help message for adding first Exhibit miscolored I think, they're either miscolored or my eyes at 2:30AM are playing tricks haha!

    * Opening calendar for the first time help message.
    marriges -> marriages
    enviornment -> environment
    accessable -> accessible
    reletives -> relatives

    * After adding first Event on calendar help message.
    appropriete -> appropriate
    automaticly -> automatically

    * Create new birth the selection of gender should be a drop down or selection option. I didn't even know I could click the box to change it until I did by accident. Grayed background in most peoples heads = unchangeable.

    * Hardcoded event "Eid-al-Fitr" Wiki has listed as being spelled "Eid-ul-Fitr." I was curious about this because the dates were variable each year but that seems to be how this event is.

    * "fs15" I just put blank spaces highlighted them, spammed Bold/Italic/Underline on them spammed redo/undo and it appeared at the start. I wonder if I made a video showing how I do this so you can see it...

    * Oh geez I did it. Crashed it messing with Copy of nothing > Paste > Undo Redos.

    It printed a "15" this time then crashed.

    I'm not sure if this is at all helpful but this is what the error signature said.
    AppName: perodika.exe AppVet 1.0.1.0 ModName: ntdll.dll
    ModVer: 5.1.2600.5512 Offset: 000109f9

    I managed to snag this, it's 1 of 2 files Windows made but I couldn't get the *.dmp file since it was being used.

    <?xml version="1.0" encoding="UTF-16"?>
    <DATABASE>
    <EXE NAME="Perodika.exe" FILTER="GRABMI_FILTER_PRIVACY">
    <MATCHING_FILE NAME="KillPerodika.exe" SIZE="41472" CHECKSUM="0x73B8B4B6" BIN_FILE_VERSION="1.0.1.0" BIN_PRODUCT_VERSION="1.0.1.0" PRODUCT_VERSION="1.0" FILE_DESCRIPTION="Perodika Uninstallation Program" COMPANY_NAME="" PRODUCT_NAME="Perodika Uninstallation" FILE_VERSION="1.0" ORIGINAL_FILENAME="perokill.exe" INTERNAL_NAME="PeroKill" LEGAL_COPYRIGHT="Copyright &#169; Yarin Licht, 2008. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x0" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1803E" LINKER_VERSION="0x10000" UPTO_BIN_FILE_VERSION="1.0.1.0" UPTO_BIN_PRODUCT_VERSION="1.0.1.0" LINK_DATE="10/05/2008 17:57:11" UPTO_LINK_DATE="10/05/2008 17:57:11" VER_LANGUAGE="English (United States) [0x409]" />
    <MATCHING_FILE NAME="Perodika.exe" SIZE="1497088" CHECKSUM="0x60C7EFBF" BIN_FILE_VERSION="1.0.1.0" BIN_PRODUCT_VERSION="1.0.1.0" PRODUCT_VERSION="1.1" FILE_DESCRIPTION="Perodika Journaling Program" COMPANY_NAME="" PRODUCT_NAME="Perodika" FILE_VERSION="1.1" ORIGINAL_FILENAME="Perodika.exe" INTERNAL_NAME="bitjournal" LEGAL_COPYRIGHT="Copyright &#169; Yarin Licht, 2008. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x0" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x173BAF" LINKER_VERSION="0x10000" UPTO_BIN_FILE_VERSION="1.0.1.0" UPTO_BIN_PRODUCT_VERSION="1.0.1.0" LINK_DATE="10/08/2008 02:02:06" UPTO_LINK_DATE="10/08/2008 02:02:06" VER_LANGUAGE="English (United States) [0x409]" />
    </EXE>
    <EXE NAME="ntdll.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="ntdll.dll" SIZE="706048" CHECKSUM="0x864EA42F" BIN_FILE_VERSION="5.1.2600.5512" BIN_PRODUCT_VERSION="5.1.2600.5512" PRODUCT_VERSION="5.1.2600.5512" FILE_DESCRIPTION="NT Layer DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft&#174; Windows&#174; Operating System" FILE_VERSION="5.1.2600.5512 (xpsp.080413-2111)" ORIGINAL_FILENAME="ntdll.dll" INTERNAL_NAME="ntdll.dll" LEGAL_COPYRIGHT="&#169; Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xB62BC" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.5512" UPTO_BIN_PRODUCT_VERSION="5.1.2600.5512" LINK_DATE="04/14/2008 00:11:24" UPTO_LINK_DATE="04/14/2008 00:11:24" VER_LANGUAGE="English (United States) [0x409]" />
    </EXE>
    <EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="kernel32.dll" SIZE="989696" CHECKSUM="0x7D737C09" BIN_FILE_VERSION="5.1.2600.5512" BIN_PRODUCT_VERSION="5.1.2600.5512" PRODUCT_VERSION="5.1.2600.5512" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft&#174; Windows&#174; Operating System" FILE_VERSION="5.1.2600.5512 (xpsp.080413-2111)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="&#169; Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xF44A2" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.5512" UPTO_BIN_PRODUCT_VERSION="5.1.2600.5512" LINK_DATE="04/14/2008 00:11:24" UPTO_LINK_DATE="04/14/2008 00:11:24" VER_LANGUAGE="English (United States) [0x409]" />
    </EXE>
    </DATABASE>
    * Also check journal properties those should display a 0 but I see "NaN." Affected fields are: Avg entry # words, All entry # words, Avg entry # char, All entry # char. On a new journal with nothing done, raw document size, also displays "NaN bytes"

    * Woot crash #2 of the night. On main journal entry selection screen without choosing an entry. I went to environment options changed the font and size of it. Gave a blank error message, same kind where it just copied the journal entry's contents and put that as error. I CANNOT however seem to replicate this now. So I'm not sure what happened.

    * Odd, messing with changing the font again I went into an entry typed "lalalala" changed the font and size got the error message with "lalalala" but "\par" was stuck on the end so it appeared.

    Code:
    Error
    
    lalalala\par
    I don't know where it got \par from at all, but I am having a hard time replicating this too.

    * Before editing a journal (just after opening a journal) Change font and you'll get an error message with "~" This replicates each time you start and do that.

    * Made a "3" appear after highlighting bold/italic/underlining and undo/redoing. There is definitely something there.

    * Series of error messages. Replicates too!
    Have Perodika opened, any point in program seems to make this happen. But make sure you have UNsaved changes. (To an entry for instance.)
    Have an exhibit exported (Might work for any file, ok, Tried a *.txt and got 3/3 of the error messages.)

    Take that Exhibit file *.doc in my case was the exported file. Drag it from desktop (wherever stored) over Perodika shortcut.
    Perodika asks if you'd like to save the journal.
    Hitting Yes will say "Journal was opened in read-only mode, Hence, you are not allowed to save any changes made to it."
    Hit OK.
    Next error message, "Failed to save changes. Closing of journal aborted."
    Next error message, "Failure to allocate required memory. Your computer must be barely running right now."

    I hit NO when Perodika asked me to save my journal and ONCE replicated this to some extent but other times it gave me proper "This doesn't seem like a valid journal file."


    * Hmm, it seems that by opening the journal file by dragging it over Perodika opens it in read only mode. Ok, this seems to stop the above error from replicating. It may be good to have different messages or find out why dragging over to open is read-only mode. Taking the user a different error message way would help a lot in explaining it I think. But if you open and edit a journal normally then try to open the *.doc by dragging it and choosing EITHER yes or no to save or not, you'll get "this is not a valid journal entry. "

    * When you run the uninstall program, it leaves the directory and the uninstall program still present.
    Last edited by sdemaio; 10-08-2008 at 01:21 AM.

  9. #9
    Unregistered User Yarin's Avatar
    Join Date
    Jul 2007
    Posts
    2,158
    Beta 3 is out now.

    The only problem I noticed with b3 is that if you create to many events the program will have a memory overflow. Other than that it's suppose to work perfectly. See if you can duplicate that bug.

    I don't have any printers installed either, but I do have some XLS program that seems to be recognized as a printer. So I can't duplicate that bug. Could you give a more detailed report of what happened?

  10. #10
    Registered User
    Join Date
    Sep 2008
    Location
    DE
    Posts
    17
    * Hm the "s9" bug seems to be gone... but following similar steps I made it put a "\par" at the end of document. Replicating this is just a matter of spamming bold, italic, underline, copy, paste, cut, etc and redo undo.

    * Journal properties is all fixed up except the # of characters for all entries which displayed a "2\g" for me. One entry, with 12 characters.

    * The print bug is a matter of having NO print options installed on system. Try removing the XPS and any printers and then printing from program. It first tells you there is no printer installed and that it failed to load the printer dialog. That happens choosing yes or no. The Error give was PDX4104. I tested it on my other PC with a printer installed and it works just fine without the error.

    * Replicable crash bug.

    Have Perodika opened to view the entry selection screen.
    Have any entry highlighted. Go to Edit -> Find -> Selected Entry -> type anything, search and it crashes everytime.

    I tried having no entry highlighted and using Find but it properly told me to select an entry. I tried Finding over the whole journal but it came back with proper results (text found or not found). Something with Selected Entry it doesn't like.

    Running out of ideas to test! Gonna keep messing around though :P

  11. #11
    Unregistered User Yarin's Avatar
    Join Date
    Jul 2007
    Posts
    2,158
    I have Beta 4 out now. It should run smoother than smooth butter...

    Let me know what you find!

  12. #12
    Registered User
    Join Date
    Aug 2003
    Posts
    13
    * File > Journal Properties is really wacky now.

    http://img390.imageshack.us/img390/6...pertieshg1.jpg

    My journal is one entry, 3 words "A new entry."

    * Divorcing on calendar asks me for birth dates of Person 1 and 2. I think that is irrelevant. Perhaps just a bug. If you hit Edit on Event after making it and hit Okay, it will ask you for the Birth date of one person. If you hit no it will do nothing, if you hit Yes it asks you about person 2.

    * Error where if you are editing event for instance and the event loses focus in the list box and you hit edit again (click calendar to change focus.) It generates an error. Remove also does this. I think the buttons are supposed to Gray out if you lose the focus on the event but they don't.

    *Succeeded in crashing Perodika. But I'm not sure exactly what caused it. Going to work on this one.

    * Journal relocation. A few problems, the confirmation dialog has the 2nd date incorrectly displayed ("0/0/424") or something weird (it changes). Second if you hit no, the dialog closes and that's fine. But if you hit Yes, you get an error "cannot create file" and Perodika crashes.

    *Journal Synchronize creates phantom entry.

    "Entry 1 - 110/118/69 - 56:101PM - 98 Exhibits"

    I had two journals each with two entries. Lol at the :101PM btw :P

    This also had a very bad problem it seems... my base file (journal.bjd) is completely corrupted now and causes Perodika to crash each time I open it. Journal2.bjd (the file I told, journal.bjd to synchronize to) contains all the entries it should + the phantom entry.

    * Reset timestamp does fix the erroneous date and time on phantom entry.

    * Even though entry 1 claims to have 98 exhibits none of the exhibit options are available, I think that's good though since they don't exist. Probably just a display error. I lied. If you open the entry and use the buttons to navigate the exhibits or use the exhibits menu you can work with non-existent exhibits. I exported all and made an empty zip file. :P

    * Exportation of an entry now shows the correct path :P You probably knew this though.

    * Just curious if there is an export entry, there is no import?

    * Not really a problem but when you list today's events, Ok and Cancel accomplish the same thing and may be confusing. I think just Ok is good.
    Last edited by steve_demaio; 10-10-2008 at 06:50 PM.

  13. #13
    Registered User
    Join Date
    Jan 2008
    Posts
    290
    Hey I tried out the app really quick. I didn't do any crazy stress testing or anything (i.e. I didn't try to break it).

    One note though, some of your dialogs get cut off if Windows is set to use a larger font. I'm on Vista with my font DPI set to 120, and this is what one of the help dialogs looks like for me:

    Attachment 8481

    Also, several of the installation dialogs had similar issues where most of the text was cut off.

    Sadly, this seems to be a problem with most applications these days (I seem to be one of the few people who uses a different DPI setting).

  14. #14
    Unregistered User Yarin's Avatar
    Join Date
    Jul 2007
    Posts
    2,158
    Like you said, the font size thing is a common problem.
    This is so because writing a program to adjust window and control size to properly accommodate font sizes, you'll be adding a lot of code, that won't even be necessary 99% of the time.

    Just so you know I haven't given up or anything, I'm still working on B5.

  15. #15
    Unregistered User Yarin's Avatar
    Join Date
    Jul 2007
    Posts
    2,158
    Well, now that I think of it, my next project will probably use dialog units to fix that, it's a habit I need to get...

    Okay, I finished beta 5.
    Please tell me what you find wrong! Or what you think should be added/changed. (Not including that font problem arpsmack pointed out)

Popular pages Recent additions subscribe to a feed

Similar Threads

  1. Issue with program that's calling a function and has a loop
    By tigerfansince84 in forum C++ Programming
    Replies: 9
    Last Post: 11-12-2008, 01:38 PM
  2. Need help with a program, theres something in it for you
    By engstudent363 in forum C Programming
    Replies: 1
    Last Post: 02-29-2008, 01:41 PM
  3. Replies: 4
    Last Post: 02-21-2008, 10:39 AM
  4. My program, anyhelp
    By @licomb in forum C Programming
    Replies: 14
    Last Post: 08-14-2001, 10:04 PM