[APP] AMeBa: Adapting Menu Bar for WM6.5.x [v0.8 release candidate - 31/Mar/2010]
- Thread starter xtep
- Start date
I don't know about showcase but fdcsoft taskmanager said that AMeBa uses only 1k
I'm afraid that is a problem in CorePlayer because AMeBa closes the apps frendly sending a WM_CLOSE message to the main window. Anyway, I'm going to do some tests with CP.
Of course, this tool is free.
V
vogonj
Guest
same here, the moment I stop AMeba synchronization starts (Diamond 1 build28004 <-> Windows7). No need to uninstall AMeBa, just stopping the process and syncing is fine.
Hope this gets fixed, then this program is a must for every rom
glad to hear it's not just me, yeah w/that one small issue fixed i think it'll be a must for 6.5.xsame here, the moment I stop AMeba synchronization starts (Diamond 1 build28004 <-> Windows7). No need to uninstall AMeBa, just stopping the process and syncing is fine.
Hope this gets fixed, then this program is a must for every rom
Last edited:
You haven't reported that bug before. Could you explain better what the problem is and the steps to reproduce it?
I don't understand you. Could you explain better what the problem is and the steps to reproduce it?
@XTEP
sorry about that msg
When install 0.2 then all apps crash...
now on 0.3.1b all working better but still 1 - 2 apps is not compatible and i still have problems like msn messenger.. i use the latest.. from market place..
MSN does not connected.. after email and pass screen loading all the time...
sorry about that msg
When install 0.2 then all apps crash...
now on 0.3.1b all working better but still 1 - 2 apps is not compatible and i still have problems like msn messenger.. i use the latest.. from market place..
MSN does not connected.. after email and pass screen loading all the time...
Me too................
Moreover, it also causes D-Pad malfunction and modifies my win-key (normal start menu to Quick menu).
Last edited:
n
xtep,
I did some further tests. If I use CorePlayer's exit button, no issue, even using MortScript's close function seems to work correctly.
Then it may be related to the WM build I use (28004)?
I'm planning to change some pieces of software on my BlackStone. I'll let you know.
Anyway, I still think this is what WM was missing...
The_Steph
xtep,
I did some further tests. If I use CorePlayer's exit button, no issue, even using MortScript's close function seems to work correctly.
Then it may be related to the WM build I use (28004)?
I'm planning to change some pieces of software on my BlackStone. I'll let you know.
Anyway, I still think this is what WM was missing...
The_Steph
V
vogonj
Guest
OT: @vogonj: that avatar is um... I mean uh... I just hope that isn't really you
Maybe that's my alter ego ... but hey, I like it *LOL*
@ xtep
i have the following issue
Diamond - WM6.5.3 Build 28005 - AMeBa v. 0.3.1b
I started this as i in the next day my Diamond was OFF and the battery was totaly drained!
wenn i connect my phone to PC (W7) it starts Sync normal. Wenn i tap the Power Off Button (Hardware) the display goes OFF normaly, wenn i tap it again the display goes ON and Sync starts again normaly, BUT wenn i repeat this 2-3 times the display will NOT go ON and i have complete freeze in my phone and have to do a Soft Reset (HW Button).
I UNinstall the AMeBa und tried again as above but no problems every things works fine
Thanx again
WBR
Siemens Lover
i have the following issue
Diamond - WM6.5.3 Build 28005 - AMeBa v. 0.3.1b
I started this as i in the next day my Diamond was OFF and the battery was totaly drained!
wenn i connect my phone to PC (W7) it starts Sync normal. Wenn i tap the Power Off Button (Hardware) the display goes OFF normaly, wenn i tap it again the display goes ON and Sync starts again normaly, BUT wenn i repeat this 2-3 times the display will NOT go ON and i have complete freeze in my phone and have to do a Soft Reset (HW Button).
I UNinstall the AMeBa und tried again as above but no problems every things works fine
Thanx again
WBR
Siemens Lover
Last edited:
This is what i meant in my previous post
But i tried it myself n it seems there's no prob with this anymore
One question though,
How can i configure my HoldStart key to run programs?
I put in \Program Files\TaskFacade\TaskFacade.exe in StartHoldRun but nothing happens
This is what i meant in my previous post
But i tried it myself n it seems there's no prob with this anymore
One question though,
How can i configure my HoldStart key to run programs?
I put in \Program Files\TaskFacade\TaskFacade.exe in StartHoldRun but nothing happens
I also have the same problem, i am trying task facade too, and when I hold the start button, nothing happens
How can i configure my HoldStart key to run programs?
I put in \Program Files\TaskFacade\TaskFacade.exe in StartHoldRun but nothing happens
I'm afraid that it is a bug in my code: both tap and hold actions read the program to run from StartTapAction or CloseTapAction.
I'll solve that on nezt build. Try setting StartTapRun to \Program Files\TaskFacade\TaskFacade.exe until then.
I have tested it myself (coreplayer 1.3.6) and Cp remeber the last play position when I close it with AMeBa.
Last edited:
I'm working on that but it is quite frustrating because I cannot find a cause.
If I don't found a fix, I will create a key with a exclusion list (that is a list of apps that does not work with AMeBa).
I have tested it myself (coreplayer 1.3.6) and Cp remeber the last play position when I close it with AMeBa.
xTep,
My apologies, I messed up my tests. I was not closing CorePlayer using AMeBa but minimising it. When I clicked the second time on CP, a new instance was launched and this time with no movie to view (that made me think CP was losing info). Probably because I did not set up AMeBa as expected.
Sorry for all that mess
Anyway, I think I also suffer the ActiveSync issue
If a debug mode is available I's gladly provide information. Your piece of software is so promising...
The_Steph
Last edited:
Similar threads
