You can post your examples of Apt usages in specific apps here, and check out the cool ideas that other people came up with. The list will be kept in alphabetical order. Screenshots are not always necessary, but sometimes help.
- This is a fast-item-deletion example. I have this habit of deleting entries from my Calendar app (KsDatebook, even though you can adapt this example to the default Datebook) after they happen - in the afternoon I delete the entries from that morning, etc. Just to get the feeling of throwing things behind my back when they are done… since it is a common movement, requiring several taps, I made a macro in Apt to handle it.
- To trigger it, I used a relative stroke (seen in the image) configured in Apt's Grafitti tab of target "KsDateBook". I draw this stroke as a small downward-right stroke, with the height of about two lines in KsDatebook's day view. Since it's a relative stroke, it doesn't matter where on the screen you do it, all that matters is the direction and length of the stroke. The actions are as follows:
- (-) RStrk- / Pen / CBar D- this invokes the delete command D.
- & / Nav / Up / 2- notice the & trigger, which is the basis for macros: it means "do this as a sequence of the previous line/trigger".
- & / Nav / Cntr /- Double navigation up, then center button. This is the creative part. Since KsDatebook shows two different delete confirmations dialogs, one for repeating and another for non-repeating events, I had to come up with this key combination that works for both (it deletes only the Current instance of repeating events). To understand it, just try it manually.
- To use this, I just have to tap an item in Day View and stroke downwards to the line below it. The beauty of this is that since I defined a relative stroke in Apt, it works in any part of the screen, for any item. Since the start of the stroke selects the item I want to delete, the delete command goes to the correct item (but use with care until you feel confident that it works!).
- this is the kind of example that can be applied in many different apps with a bit of adaptation: a relative stroke to give a certain command on a given item.
- This is just to mention that eReader handles it's own screen orientation (portrait/landscape) so you're better off setting this to your liking inside eReader, instead of in Apt.
- Some people like using Apt to tweak with the Brightness settings in eReader, either to bring it down for night reading or to bring it up if it helps their eyes… but you can also consider eReader's built in "Color Themes" and "Invert Screen" options.
- Another great idea is enhancing your page indicator on the scrollbar with extra functionality. By default, you can only click on it to open the "Go to Page" form. But you can add two strokes in Apt's grafitti tab, one crossing eReader's page indicator from left to right and another from right to left, with these definitions:
- (-) / Strk / Pen / CBar E- this one is the left to right stroke, it should take you to the end of the eBook.
- (-) / Strk / Pen / CBar V- this one is the right to left stroke, it should take you to the beginning of the eBook.
- (-) / Strk / Pen / CBar L- while we're at it, why not add a third stroke - this time from the page indicator moving down just a bit - this is defined as a "Find Next" command, very useful when finding a word throughout a text.
- A nice way to make a button in ScrBtn launcher do not just one but two things, is to assign a stroke over the button. In this example, I have OffFlush assigned to a button on ScrBtn. Then I use Apt grafitti settings to add a stroke as seen on this partial screen image. It's a short stroke from left to right over the OffFlush button (you can't see this button here, it's the one under the green stroke-definition lines).
In Apt, I assign that stroke in the Grafitti tab like this:
(-) / Strk / DA / FlushDA
So, if I want to go into OffFlush, I tap it; but if I just want to quickly flush the memory, I do the stroke (usually with my finger…) and Apt executes FlushDA for me.
If you want to get really complex, you can think of assigning strokes in the four directions over a button.
Warning: since Apt is just recognizing strokes on screen, it is not sensitive to which ScrBtn screen you are on; your stroke will do the same in every category. This can be thought of as a limitation (you can't define different strokes for two buttons with the same position on different screens) or as an advantage (you can do the stroke without having to switch categories)…