Perhaps you could try the +Form trigger - you would have to find out the ID of the main form on A5. I don't know if this makes any difference when compared to launch+, but it's worth a try…

Another idea: how is A5 launched? If it's from Apt, you could try doing these actions on the launching script of the previous app (or *default*), not on the A5 launch+ script. Maybe it could work that way…

At the moment i want to set an variable and the auto off timer.

The things with the dia I know. Its really down also the palmos intern state. So what apt should do is just to show it. So this random doesn't have something to do with the palm os intern state, because its every time the same (down).
I use it for my dictionary when I want to look up something and I'm a impatient person, so maybe the idle thing will solve the problem, but I'm sure I will do my input before this 1 second.

cu
Stefan

I don't know the answer to your problem, but I have a couple of things worth mentioning:

- there is a known problem with Apt bringing the DIA up or down: it works for the moment, but sometimes fails to stick because somewhere in the depths of Palm OS there is a memory of the DIA state that does not get changed by the Apt action of DIA up or down. Perhaps this could explain your "random" behaviour: maybe the DIA is just going back to the state of the last time you changed the DIA manually by tapping the status bar.

- perhaps you can try a different trigger to see if it works, instead of launch+. You can try Idle(1) which will trigger one second after launch if you don't touch anything.

If you care to share what actions you have in your launch+ trigger, that might also shed some light on the issue…

Good luck!

I have found a new or old bug ;)
In the default settings under pref I have set, that the DIA should be down and only the Statusbar is visable:
DIA: not checked
STBar: checked
So far so good.

If I now have a program where I want to have the DIA. I set for this program in pref
DIA: checked
STBar: checked
so far so good

Now I additionaly add an action for the Luch+ in events (for the program only or in default this doesn' matter, For my research its was for the program A5)

Now there are 2 different things which can happen:
1st: The DIA comes up in the program (A5) but the lunch+ macro is NOT executed
2nd: The DIA comes up, the lunch+ macro is executed, the DIA goes down.

Both are wrong in my eyes. And also its somehow random, when what happens. Its nearly 50/50

cu
Stefan

I hope to address some of the problems with 1.3b and get it published sometime (as well as answering forum posts!)

Pent

I dont like third pary launchers because most of them is slowing down my TX markedly. But one thing I misses in the built in launcher is the option to switch between views, more than just the list view and 3 x 5 icons. Now, I just found out that by hiding the SBar in Applications gives you one more row for the icons and that is kind of useful. You probobly seen this before but for you that havnt, here you go! :-)

You can find tutorials of 'how to' along the left side of the main screen here. Sorry, my Centro is busy backing up, so I can't test it for you…

Also, I'm hoping that you put in the " & " sign in the 2nd line of your macro as quoted above:
-Lnch App TomTom
+Lnch Panel BT

seems like you only put the " & " into the 3rd line that gives you the control tap…

Also in tutorials section there should be a piece of advice on when to use controls, or taps or other types, sorry- I'm in a bit of a rush, so I can't get into details… Besides, you'll learn some good stuff either way, let me know. HTH, technical1

Can someone tell me how to do it? Wake only detects the power on.

-Lnch/App/TomTom (If that is the app name)
+Lnch Panel Bluetooth
&/Ctrl/Tap/20133

To turn it off on exit

Exit/App/TomTom
&/Panel/Bluetooth
&/Ctrl/Tap/20132

and I'm getting nowhere. Even the turning on part, it gets to the bluetooth panel and highlights the 'on' button but doesnt activate it. Do I need a control to active 'done' in this screen too? Thx for any further help, if I can get this to work I will buy the full version because there are other tasks I want to acheive too.

+Lnch Panel Bluetooth ….. HTH, technical1

Any advice here?

Launched the Bluetooth Panel with Apt
Launched the Apt Menu with HB4
Tap List Ctrls or List Flds = Crash

Did not try any of the other menu items.

Thanks,
Don

-Lnch/App/TomTom (If that is the app name)
&/Panel//Bluetooth
&/Ctrl/Tap/20133

To turn it off on exit

Exit/App/TomTom
&/Panel/Bluetooth
&/Ctrl/Tap/20132

HTH,
Don

Im new at this but finding it v. interesting. I dont usually leave blue tooth on - I have a treo 680 and it kills the battery!
I do however, need it when using navigator TomTom. When the Navigator starts it asks if I want to turn on bluetooth each time. I was thinking it would be cool if when you start Navigator, Apt could make blue tooth start before going to the Navigator therefore negating the need for it to ask if I want to turn blue tooth on.

does this make sense? I hope so. Is it possible to do this?
Thanks for any replies.

I don't have a 680, but it should be possible to try this: go into native PalmOS Preferences app- there is a Buttons setup screen there. Make an assignment, or in this case, maybe, make a change & then soft reset & then change back to what you want Hrd1 to be… & be sure that Apt doesn't have any setting to reflect this choice & see if going back to native Prefs & making change-soft reset & change back helps…

Did you try posting on MyTreoDotNet forums, there is a Star Developer's specific forum & Hobbyist has a section there… in case it doesn't turn out to be an Apt oriented thing… I don't get what you seem to be presenting as an overlap between Apt, & Butler, which I use - of course, this could be a 680 specific behavior w/Apt thing…

There are set buttons which Butler can affect & then you have the chance to set the s/w you wish to be associated to those set buttons, or those buttons plus the Option key; but nothing there about Hrd 1…..

Good luck, technical1

Thanks

I have a Treo 680, Apt most recent beta.