Author Archives: bayhoff

Beta 8 of DataOrganizer 1.0 Now Available

The eighth beta of DataOrganizer is now available.

(If you would like to give it a try, please send me an email at beta at bayhoff.com.)

Release notes:

DataOrganizer will now remember which cards are selected for libraries, stacks, and smart stacks. Upon selecting a library, stack, or smart stack, DataOrganizer will automatically show you the card that was last selected. The selections are preserved between launches.

In addition, the selection in the source list is now preserved between launches.

As of Beta 7, DataOrganizer preserves not only the size and position of the window, but the positions of the two vertical dividers. Sadly, the second divider was usually placed in the wrong spot upon relaunch, making the middle pane (the list of cards) too narrow. This has (hopefully) been fixed in beta 8.

Window > DataOrganizer (previously Window > Data) now correctly opens the DataOrganizer window if it was previously closed.

The app icon now appears in the welcome screen and the about box on Macs with retina screens.

Remaining known issues that were not fixed in this beta:

For reasons that I have yet to figure out, a crash appears to occur in the sidebar/source list. (It is also possible that the crash is really occurring in a relationship field’s library/stack chooser, as it uses the same code as the source list.) DataOrganizer tries to insert a stack (into a library) below a stack that does not exist.

DataOrganizer may crash when attempting to drag a a new field out of the field bar. This bug may be related to the source list bug mentioned above.

Advertisements

Beta 7 of DataOrganizer 1.0 Now Available

The seventh beta of DataOrganizer is now available.

(If you would like to give it a try, please send me an email at beta at bayhoff.com.)

Release notes:

Upon relaunch, DataOrganizer now remembers the size and position of the window. It also remembers the positions of the dividers.

Some of the proxy images in the field bar have been replaced by images that better portray the behavior of the fields that they represent.

The appearance of the template sheet has also been altered. Not only has the background color changed, but the generated template images have also been tweaked to better match the the updated proxy images in the field bar.

DataOrganizer is now compiled using Swift 4.2.

Remaining known issues that were not fixed in this beta:

For reasons that I have yet to figure out, a crash appears to occur in the sidebar/source list. (It is also possible that the crash is really occurring in a relationship field’s library/stack chooser, as it uses the same code as the source list.) DataOrganizer tries to insert a stack (into a library) below a stack that does not exist.

DataOrganizer may crash when attempting to drag a a new field out of the field bar. This bug may be related to the source list bug mentioned above.

DataOrganizer 1.0 Beta 6 Now Available: It’s a Dark Mode World

The sixth beta of DataOrganizer is now available.

(If you would like to give it a try, please send me an email at beta at bayhoff.com.)

Release notes:

DataOrganizer now fully supports Mojave’s Dark Mode.

The permissions problem affecting the contacts and events fields has been resolved. (In prior versions, this bug only occurred when run on Mojave.)

The appearance of the choice field has changed. Choice fields now display themselves as a standard pop up button. As such, the behavior of the choice field is more clear. (It also looks better in dark mode.)

Screen Shot 2018-11-01 at 10.41.08 PM

Remaining known issues that were not fixed in this beta:

For reasons that I have yet to figure out, a crash appears to occur in the sidebar/source list. (It is also possible that the crash is really occurring in a relationship field’s library/stack chooser, as it uses the same code as the source list.) DataOrganizer tries to insert a stack (in a library) below a stack that does not exist.

DataOrganizer may crash when attempting to drag a a new field out of the field bar. This bug may be related to (the same?) source list bug mentioned above.

DataOrganizer 1.0 Beta 5 Now Available

The fifth beta of DataOrganizer is now available.

(If you would like to give it a try, please send me an email at beta at bayhoff.com.)

Release notes:

The number of permitted fields for some field types has, once again, increased in this version.

The appearance of the rating field has changed slightly.

Help > DataOrganizer Help now opens the Getting Started Videos page in your chosen browser.

Remaining known issues that were not fixed in this beta:

Although DataOrganizer “supports” Mojave’s dark mode, it looks terrible at the moment.

There seems to be a “permission problem” with contacts and calendar events. Like iOS, macOS will ask you for permission before accessing your contacts and calendar information. This works fine on High Sierra. However, Mojave seemingly denies access without asking, rendering the contacts and events fields useless at the moment.

For reasons that I have yet to figure out, a crash appears to occur in the sidebar/source list. (It is also possible that the crash is really occurring in a relationship field’s library/stack chooser, as it uses the same code as the source list.) DataOrganizer tries to insert a stack (in a library) below a stack that does not exist.

DataOrganizer may crash when attempting to drag a a new field out of the field bar. This bug may be related to (the same?) source list bug mentioned above.

DataOrganizer 1.0 Beta 4 Now Available

The fourth beta of DataOrganizer is now available.

(If you would like to give it a try, please send me an email at beta at bayhoff.com.)

Release notes:

Fixed the following issues:

In prior versions, the Bento importer would crash if there were too many fields of a certain type. The number of permitted fields for some types has increased in this version.

In prior versions, a relationship field would crash the app because it appeared that it did not know what library or stack it had formed a relationship with. It turns out that this bug had nothing to do with the import process, nor did the relationship field somehow forget what library it had previously formed a relationship with. A crash occurred when trying to do the following on a prior beta:

  1. Add a Relationship Field to a library. (However, do not select a library or stack in the field’s chooser.)
  2. Create a new library.

Upon creating a new library, the relationship field’s library and stack chooser would notify the relationship field that a new library needs to be added to the chooser’s list. Sadly, the relationship field would improperly use this information which would ultimately force the field to access the library or stack that it shares a relationship with. Because a library or stack has yet to be selected (the chooser is still present), DataOrganizer would suddenly become very confused and subsequently crash.

Remaining known issues that were not fixed in this beta:

Although DataOrganizer “supports” Mojave’s dark mode, it looks terrible at the moment.

There seems to be a “permission problem” with contacts and calendar events. Like iOS, macOS will ask you for permission before accessing your contacts and calendar information. This works fine on High Sierra. However, Mojave seemingly denies access without asking, rendering the contacts and events fields useless at the moment.

DataOrganizer may crash when attempting to drag a a new field out of the field bar.

Beta 3 of DataOrganizer 1.0 Now Available

DataOrganizer Beta 3 is now available.

(If you would like to give it a try, please send me an email at beta at bayhoff.com.)

Release notes:

DataOrganizer Beta 2 sometimes crashed when attempting to delete a field. This issue has (hopefully) been fixed.

Fixed an issue with CSV import where the import would fail if the last value of a row consisted solely of spaces.

In prior betas, the search field would not edit (Command-Option-F) if the source list/sidebar was hidden (View > Hide Sidebar). This was because the search field is part of the source list and the source list was not visible. As of Beta 3, the source list will now show itself prior to search field editing should the source list be hidden.

In addition, some minor internal changes were made that should not be noticeable.

Remaining known issues that were not fixed in beta 2:

Although DataOrganizer “supports” dark mode, it looks terrible at the moment.

There seems to be a “permission problem” with contacts and calendar events. Like iOS, macOS will ask you for permission before accessing your contacts and calendar information. This works fine on High Sierra. However, Mojave seemingly denies access without asking, rendering the contacts and events fields useless at the moment.

The Bento importer crashes if there are too many fields of a certain type.

For whatever reasons, a relationship field may not know what library it has formed a relationship with. (It is hard to tell at the moment whether or not this is a bug with the import process.)

 

DataOrganizer 1.0 Beta 2 Now Available

DataOrganizer Beta 2 is now available.

(If you would like to give it a try, please send me an email at beta at bayhoff.com.)

Release notes:

Fixed an issue with CSV import where the import would fail if the data contained an empty value.

Fixed an issue with CSV import where all columns would import as a text field even if a different field type was chosen.

Fixed an issue where DataOrganizer would crash if the source list selection changed while a multi-line comment field was editing.

In addition, some minor internal changes were made that should not be noticeable.

Remaining known issues that were not fixed in beta 2:

Although DataOrganizer “supports” dark mode, it looks terrible at the moment.

There seems to be a “permission problem” with contacts and calendar events. Like iOS, macOS will ask you for permission before accessing your contacts and calendar information. This works fine on High Sierra. However, Mojave seemingly denies access without asking, rendering the contacts and events fields useless at the moment.

The Bento importer crashes if there are too many fields of a certain type.

For whatever reasons, a relationship field may not know what library it has formed a relationship with. (It is hard to tell at the moment whether or not this is a bug with the import process.)

DataOrganizer sometimes crashes when attempting to delete a field.