You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I tried out splitting, it wasn't quite clear to me that after running the "Split Files" tool that I then had to Export again, which caused some confusion on my end.
I know the directions say the right things, but my brain ignored them as they were regular text under the image. To me, if the "Easy Button" doesn't do all the steps, the user's following actions need to be more obvious/bold, or you'll get a bonehead like me wondering what happened.
If we're not providing the first commit / export as part of the split merge, it would be nice to on both on the Form_Close event and the help docs to make it clear the developer needs to go and export again.
Ideally, to me, the tool would export the split commit as part of the split files button action so the next export would be compared against the split, and no changes "should" occur (unless they changed something).
The text was updated successfully, but these errors were encountered:
When I tried out splitting, it wasn't quite clear to me that after running the "Split Files" tool that I then had to Export again, which caused some confusion on my end.
I know the directions say the right things, but my brain ignored them as they were regular text under the image. To me, if the "Easy Button" doesn't do all the steps, the user's following actions need to be more obvious/bold, or you'll get a bonehead like me wondering what happened.
If we're not providing the first commit / export as part of the split merge, it would be nice to on both on the
Form_Close
event and the help docs to make it clear the developer needs to go and export again.Ideally, to me, the tool would export the split commit as part of the split files button action so the next export would be compared against the split, and no changes "should" occur (unless they changed something).
The text was updated successfully, but these errors were encountered: