Use with caution.
These public beta programs contain new fixes and new features that haven't been fully tested. I need you to tell me if you find any problems with these program or even if the changes listed work as you expect.
joejoe Dec-02-16 8:44 PM UTC
Post Release Plans
As usual, a few days will be reserved to address any important issues that may be discovered in ArsClip. After that time period, there are two new features that will be created.
First, a "More" button will be added to the Clip Menu. This will let me cleap up this menu without sacrificing functionality. Other lesser used Clip Menu items will also be disabled by default, since "More" makes it easy to discover and use.
When testing a fix to Form Mode for v5.10, some issues were discovered. It appears a timing issue can cause the Popup to change to Clipboard Only mode. This will be addressed and more testing will be done to make sure this mode is stable. No features are planned for it.
Second, the "Pinned" Popup feature will be researched. This mode will be limited to mouse-only, but can be used to paste into several programs. By default, the Popup is locked to a single application. This feature was a user suggestion - and a rather good one.
Lastly, the Popup's visual may be updated. The bottom of the Popup may be extended to add some more special controls. Currently, only a "drag" indicator is used. This location would be a good to host the "Pin" button. The "Show More" item seems like it would be more intuitive as a special control than a menu item. The System and Program Options menus also would be more intuitive as special controls.
joejoe Nov-27-16 8:45 PM UTC
Preparing v5.10 for Release
The ArsClip Beta is now in feature freeze. The updates for this version are almost purely bug fixes, so the current Release Candidate 1 is just a precaution. After a few days, RC1 will most likely become the official release.
joejoe Nov-12-16 4:38 PM UTC
The current changes in ArsClip aren't updates, but rather more documentation included directly in the program. My philosophy on help files is that if you need them, you've failed to create the program correctly. There's almost never a reason the information cannot be included in a utility program.
The Configuration window now has a section for explaining how the window is used. A user, long ago, sent in a suggestion to add a tips window when this window is display. Since there's only one tip needed for the window, I thought it would be best for it to just add a section for help.
The purpose of the Configuration Help section is to document things that aren't obvious or are intentionally hidden. For example, there are variables in the ArsClip.ini configuration file that are only used as advanced tweaks. This also is a good location to place information that's too verbose to be placed with the option.
I'll be looking at feedback more closely to grow these sections organically.
joejoe Nov-07-16 4:53 PM UTC
Shared Permanent Groups Redux
This feature needs updating, badly.
First, the program isn't correctly showing that a group is shared on another computer (on the Share window). Clicking the "share" button on a group that is already shared causes duplicates to appear.
Second, the process is very conceptual. It needs better explaining. For example, once a group is shared, there's no indication on what happens next. While the process is automated, the program does not give any directions or visual cues to let you know that no other actions are needed. The share window needs to communicate this better.
Third, the About/Help tab can be used to go into detail on how to use ArsClip in a shared location. Once again, the process is automated, but the program doesn't have any directions or requirements listed. In reality, once the program is placed in a shared location (a Windows Share or a cloud-synced location), everything is automated. For shared groups, the program automatically keeps track of when a group is changed and each instance will update on a timed interval. Offline instances will update when first started.
Lastly, I need more feedback. I use feedback to guide my work, but there's not been very little feedback on this feature. This was a highly requested feature, but most users don't require it. The result is that it's not very likely to get any feedback, even when there are issues or improvements needed.
joejoe Nov-05-16 5:08 PM UTC
It's that time again, as the well has run dry for new new features. The good news is that the programs are feel feature complete. This does mean that I'm in a maintenance mode and only fixing issues.
I'm about 90 percent sure that I misfiled some user feedback for new features, so feel free to resend your requests if they've not been implemented.
The one idea I have for the future is an online library of scripts for ArsClip and Rename Master. Currently, example scripts are hardcoded into the program and require a full update to change. My idea is to have scripts that will do the job or can be used as a base to create custom scripts. The library will be fully integrated into the program
joejoe May-27-16 9:06 PM UTC
Global/Shared Permanent Clips 3
The coding is almost done for this feature and will likely be available as a Public Beta tomorrow.
The "Databases" tab has been updated to include a Shared Permanent Groups link. This will bring up a window that can be used to convert a group to be global.
When a group is converted, all clips and hotkeys of the group are copied to a single database. Each instance will create a copy of the group in it's local database. Instances will be updated either by a timer or when the program is first run. Any changes made to that group's clips will also trigger an update.
A new "shared.ini" file in the "clipdatabase" folder is used to keep track of synchronization. A setting has also been added to this file to not include importing hotkeys for each machine. By default, all machines will import both the clips and their hotkey settings.
joejoe May-26-16 2:09 AM UTC
Global/Shared Permanent Clips 2
The design phase is almost complete. I've found a method that satisfies all the goals, and this was probably the hardest part. This method requires only 3 small changes to the existing database functions and the rest of the program remains unchanged. The only exception is a change to the user interface to set a Permanent Group to "shared".