Re: [Announce] Power Menu QML for Harmattan [v0.0.4.1]
 

This delay problem comes from double press delay.
I dont use any double press actions.
How I can I delete double press from waiting for second press before locking screen?
I did set that delay to 1ms but it it didint work. Do I need to reboot or use other value?

Re: [Announce] Power Menu QML for Harmattan [v0.0.4.1]
 

this delay not come from double press delay, lol :D

Re: [Announce] Power Menu QML for Harmattan [v0.0.4.1]
 

I still think it does.
Theres no delay when lock from lockscreen because its not possible there.
Could you please upload version before settings.

Re: [Announce] Power Menu QML for Harmattan [v0.0.4.1]
 

You think it does? Maybe you also think user know more how to work application, than it's developer? haha :D
and no, i can't upload this. you can manually perform modification from #95 if you not using Legacy behaviour.

Re: [Announce] Power Menu QML for Harmattan [v0.0.4.1]
 

Changing that line to defaulf did nothing.

Anyone has any other version before 4.0 .deb file because Coderus wont upload one because unknown reason...

Re: [Announce] Power Menu QML for Harmattan [v0.0.4.1]
 

well. obliviously you should do /sbin/initctl restart mce after changing it's config file, or reboot ;)

Re: [Announce] Power Menu QML for Harmattan [v0.0.4.1]
 

Tried rebooting and asked you few times if that is necessary.

Found version 0.0.1 sometimes its good that internet doesnt forget.

Will try fixing tomorrow. If no success I will just use 0.0.1

Re: [Announce] Power Menu QML for Harmattan [v0.0.4.1]
 

Critical? Maybe not, but annoying? Hell yes...! :D

I tried to change things within the ini file, but nothing helped (before you're gonna ask me: yes I did reboot the device ;) )

There must be something that causes this problem...
I hope you can fix this problem

Re: [Announce] Power Menu QML for Harmattan [v0.0.4.1]
 

No, it's not a bug. I can't fix it :)

Re: [Announce] Power Menu QML for Harmattan [v0.0.4.1]
 

It's happening after installing this. So yes, it IS a bug :)

Maybe someone else can fix it. For now, I'll have to pass on this then.