yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I did check my code, but I am confused. Which BattClock settings are reset?

I know it is sometimes hard to press the BattClock area, you can easily press too far to the right. But I cannot due much about it. You can make the clock wider, but that is normally also not an option. You can also make a shortcut to TouchLockAction in the start menu.

I did change this. I tried to center as much as possible. That is also the reason why I sticked to the resx approach, with this it is possible to change the sizes/layout per language. I know it is more convenient to have a text file, but then you have the problem it may not fit for every language. I will think about it, to provide both possibilities. Anyway, the next step would be to translate the other settings screens, so I have to think about it, because integrating everything myself in 32 languages and with all the settings screens is a tedious task. I fixed the problems mentioned above. So they will be part of the next bugfix release.

On my phone I still see 0.1 to 0.15 %. Maybe it consumes a little bit more CPU, but that does not mean it consumes more battery. Also the CPU usage is zero when the screen is off/suspended. And when the screen is on, the major battery usage is the phone itself, the LCD and backlight. But I will have a look where the extra CPU is spent now and if I can improve it a bit.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I did try to reproduce, but on my phone it is working correctly. When it is locked, it is shown red, when it unlocks the stripe is away. So this is according to the intention. So I am not sure what is your problem :confused: Can you be more precise what the problem is?

The white led is not controlled by TouchLockPro, so this is more a (mal)function of HTC, I think. But maybe others have ideas?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Can you enable debug logging (LogDebug=1 in Other Settings), reproduce the problem and post the debug log file \TouchLockPro.log.txt. Maybe that gives me a clue.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Can you be more precise what the exact problem is with the BattClock settings. Because I could not reproduce.

The other one is a more serious problem, because when it awakes in your pocket, it consumes too long battery. I will post a fix ASAP.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockAction.exe has been moved from the \Windows folder to the place where TouchLockPro is installed. The directory is dependent on your language and if you installed it on your phone memory or SD card. Mine is stored in \Programmabestanden\TouchLockPro\TouchLockAction.exe

If you have an English one, it will be beneath \Program Files\TouchLockPro.

Also in this same directory are the TouchLockAction png icons (64x64) stored, so you can replace them with your own ones, if you want better ones or more consistent with your own theme. And the language resource files are initially stored there too. After the first use of TouchLockAction the not needed languages are removed, so they take no disk space/phone memory.

Did you make a shortcut to TouchLockAction? You should prepend now the full path. You know that you can also configure !UNLOCK in the TAPI settings screen? This is faster.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I had to search back to find it was the russian translation ;)

I tried to fit the new translations in the boxes.

I made the SuspendTimeOutPowerOn edit box a bit larger.

Will be part of the next bugfix release.
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
No2chem had a fix

I asked no2chem at www.nuerom.com

As expected he had an answer! It involves queying the gpio 0x25. Do you know how to do that? I don't but he said I could use his nueGPIO.dll which should work. You could probably include his dll in your project if he is ok with that.

Alternatively, one could just install his nueSIPStylus program which already does the gpio query on boot and sets the registry value to what it should be thus fixing the issue.
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Hi,

!UNLOCK doesn't work either :(

BR
[Touch Diamond, MDA Compact IV Themes and Apps] peterbonge:
As far as I can see it just "X" and "Width" are getting reset.

But it seems that with the latest version it is harder. And I already have an big area (64x48 pixels).
[Touch Diamond, MDA Compact IV Themes and Apps] varden:
Nor does !LOCKSUSPEND
[Touch Diamond, MDA Compact IV Themes and Apps] bugeyes:
nice one ! turning off bluetooth support has fixed this ! well happy now thanks
[Touch Diamond, MDA Compact IV Themes and Apps] vadim_bogaiskov:
Version 2.5: full russian translation (but I can't open TouchLockAction.TAPIForm.resources :confused:)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Good to see that people are going to translate also the other settings screens :)

The problem with the TAPI form is that I did forget to set Localizable to true for this form. In the next bug fix release it is set to true, so this one can also be translated.

I am curious which tools you did use for the translations. Did you grab the source code and just used Visual Studio for translation? Or did you use other tools? And did you do that on the resx files? Or directly on the resources.dll?
[Touch Diamond, MDA Compact IV Themes and Apps] Aizek!:
don't need to translate all text, especially name of parameters in the registry!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I did check myself, it worked with me.

But be aware, that when bluetooth radio is on and DetectBluetooth is checked, the TAPI commands are not executed anymore. This is added in Version 2.5.

Maybe I should make the default NOT to detect bluetooth, so people are not confused and I do not get problem reports about this.

Is the problem away when you uncheck the DetectBluetooth?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I see indeed that he fixed the problem in nueSIPStylus:

It also supports querying the position of the stylus (CDMA only) at boot, fixing a “bug” in the keyboard driver where the position of the stylus is not updated on restart until you take the stylus in or out.

I did find some information about gpio programming here.

I also found the response of your question:

Checking-for-stylus-position-change

It appears that this only works for CDMA devices? I myself have a GSM type Diamond, I think. So this would only half remedy the problem.

I will think about it.....

Maybe an interesting project for yourself, because you wanted to learn programming Windows Mobile ;)
[Touch Diamond, MDA Compact IV Themes and Apps] vadim_bogaiskov:
I used the special tool for localisation http://www.radialix.com/index.php?lang=en I grab source from TouchLockAction.exe

But when it is used there is a danger to translate the superfluous. It will be good, if you create full English resources.dll which it is possible to use as a source for translation.

See also:

TouchLockAction.ClockSettingsForm.resources

TouchLockAction.OtherSettingsForm.resources

TouchLockAction.SIPForm.resources

there are some problems...
[Touch Diamond, MDA Compact IV Themes and Apps] vadim_bogaiskov:
You are right! Thank you. I will try to untranslate registry parameters. I hope ZuinigeRijder make up resources.dll without this.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I am busy with a free resource editor, which operates on the resx file (the source). People can run that tool on Windows and translate the different forms. If they provide the resx files back, I can add them to TouchLockPro.

The only problem is that not immediately is clear if the text fits in the boxes. And they have to wait till the result is integrated. So maybe I also have to provide a fallback to a text file with the translations.....because then it is immediately clear if it fits and they can just start using the translations by putting the text on the right place in their phone.
[Touch Diamond, MDA Compact IV Themes and Apps] vadim_bogaiskov:
It is good idea!

Please, make all box fields more long as far as possible. For example, usually Russian text is longer than English on 50 %...
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Hi,

Yes, with !UNLOCK it work when detect BT is disabled.

So it's DetectBT that doesn't work as it should.

To me TAPI musn't execute when there is something connected to BT, not when BT is simply turned ON.

My BT is always turned ON to detect my car phone, and I only want the phone not to unlock when I've a call on my car.

Icon is different when something is connected, so there must be a different BT status.

BR
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Translation

I did it for the Dutch language. It worked fine. I did make the boxes as large as possible already. The BattClock settings are a bit crowded.

See the attachment for the resx files, including the ResEditor.exe. With the ResEditor you can open/save the resx files. You need the .NET 2.0 framework runtime for ResEdit.exe. If not installed on your Windows machine, you can get it from Microsoft (for free).

Steps to do:

1. Start ResEditor and open a resx file to translate (File -> Open)

2. Scroll down to the bottom and only translate the String entries ending with .Text (the right part of the screen). Do not translate Strings starting with >> and do not add/rename entries.

3. Save the resx file

4. Do all the resx files

5. Post the translation in this support group and also mention the language!

I will then update this in the next version (or when a batch of translations have been delivered)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
For now, the DetectBluetooth only detects if the bluetooth radio is on. Sorry for that, this was my spec ;) I had the perception, no one would keep Bluetooth on when not needed, because of battery drain. I will also change the default not to detect bluetooth.

I will think about a more sophisticated mechanism, but for now this is what is implemented.
[Touch Diamond, MDA Compact IV Themes and Apps] vadim_bogaiskov:
Russian translation - resx files.

TouchLockAction.resources - dll file. (register values translation is deleted).
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
I have already implemented it in my project and it works great. I started a new project from scratch and have been reading your code while writing my own version of it, implementing some alternate practices, leaving out stuff I don't use, and rearranging some things in an attempt to optimize and simplify.

I am very curious to know how the GPIO query affects a GSM device. Does it blow up? Does it just return an incorrect value? I just got a CDMA Verizon Touch Diamond (just to play around with - company phone - not activated and not really mine) and a CDMA Sprint Touch Pro (which is my personal one), but no GSM devices.

I got the nueGPIO.dll from no2chem's nueSIPStylus cab and implemented as below. I could probably add some checking to see if the phone is CDMA before executing this if it causes problems on GSM devices...

By the way - I learned the typedef and LoadLibrary stuff from your source code - it has been a tremendous learning tool for me!

// 0 = In, 1 = Out
DWORD GPIOStylusFlag() {
HMODULE	nueGPIO = LoadLibrary(L"nueGPIO.dll");

typedef BOOL (*nueGPIO_StylusCheck)(DWORD dwPin, PDWORD dwResult);
nueGPIO_StylusCheck GetGPIO;

GetGPIO = (nueGPIO_StylusCheck)GetProcAddress(nueGPIO, _T("GetGPIO"));

DWORD dwPin = 0x25;
DWORD dwResult = NULL;

GetGPIO(dwPin, &dwResult);

GetGPIO = NULL;

FreeLibrary(nueGPIO);

nueGPIO = NULL;

return dwResult;
}
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks, I will upload version 2.5.1 in a few moments.....with the russian translation.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
[APP][Updated 01-05-2009] TouchLockPro version 2.5.1 bug fix release

Just uploaded a new version with the reported bugs fixed.

Although I try to test thoroughly myself before release, I am glad people are helping in finding and provide input for solving the found bugs :)

Thanks!
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
Does not unlock on light sensor anymore :)

It does not want to unlock on light sensor anymore :(

See attached logs
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
I found the problem :D

It has to do with the TAPI-Bluetooth setting ! I unticked the Bluetooth detect and it`s now OK. Your tools is too powerful :)
[Touch Diamond, MDA Compact IV Themes and Apps] vadim_bogaiskov:
ZuinigeRijder, change pls, in the next version:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
That is also why I switched the default of DetectBlueTooth in version 2.5.1 to disabled. But people which installed 2.5 have still the old default, till they change it by hand or reset the defaults in the About screen.

I have to think about detecting if their is a real connection instead of radio on.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I will do that. I also thought the SIP texts did not fit, but I am not sure. Thanks for the translation effort :)

Hope people supply translations of other languages too. So it becomes a joined effort.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
Screen Problem

Check this screen shot, a big white bar on the top. Since 2.5, I got this twice today. It hides 1/4 of the screen in all application, you cannot select the top bar. The only way to remove it is to disable TPL :( But once you re-anable TLP, your back to normal, until... Dont know :)

Also attached the image without the white bar :)

Thanks

Eric
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Great !

You know, I personally enter/exit my car around 50 times a day, so it's not really possible to always have to enable/disable BT, that's why I let BT always on ;)

Is there a way to unlock only the screen on incoming call ?

Actually I hang the call 1/2 when I take the phone in my pocket because my Touch HD bottom buttons are active. :(

BR
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Strange, I never had this. I do not know if this is the fault of TouchLockPro.

If you say reenable, you mean stopping and starting TLP, and then the problem disappears (without soft reset)? Anyone else experience the same weird behaviour?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I understand it is not practical to switch bluetooth on/off for you. Detecting Bluetooth was the easiest thing to do and also the fastests. If I have to check if also a bluetooth connection is active, unlocking will take longer. But I will try out if this is possible without a performance penalty.

Unfortunately, the HTC API for locking the hardware buttons also locks the touchpanel, so that is a no-go.

I advise to lock the hardware keys and let the light sensor unlock, and if there is not enough light, use the GSensor (the default unlocking GSensor gesture is difficult, maybe change into 43) or take out the Stylus. So you do not miss calls. When you have bluetooth enabled, you can still take the call via bluetooth, although the hardware keys are locked.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
Yes, this is what I mean.

Looks like it happens when I switch back to portrait after I close my keyboard.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
I can now confirm that it happens when I get back to portait from landscape, after I reinsert my keyboard.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I will have a look at the source code.

I assume you have the same settings as posted in this log file?.

LockIndicator = 0

Stripe

You did not have this with earlier versions?

Is it easy to reproduce? If so, a debug log file when this problem occurs may also help.

Anyway, I will have a look at the source code differences with a previous version.....
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
Same settings... I never changed them since the last version. I will turn the debug on, and forward you the file once it re-occur.
[Touch Diamond, MDA Compact IV Themes and Apps] markjhvt:
Another odd thing I've noticed (at least with version 2.5 - just installed 2.5.1, so we'll see if it's still a problem) is that TouchLockPro seems to crash the version of Opera included with Sprint's latest ROM update. It's Opera 9.5 build 15954.

Opera likes to keep some of itself in memory, even after you exit, in order to start up faster next time. But often when unlocking with TLP, the pieces left in memory will crash.

Not really that big a deal - somewhere hidden in the registry is an option to force Opera to actually exit when you tell it to. I could just turn that on and wait the extra two seconds for it to fully start up each time.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
I'm now able to reproduce the problem :)

I don't know if you remember, one of my first post for 2.5, I reported a white stripe after a unlock when receiving a call. When I get that stripe, then go to landscape, and back to portrait (keyboard out / in), bam!! The big white bar/stripe is back. So, here the steps:

1 - Did a soft-reset, just to make sure :)

2 - Once it's locked, and screen off, call my phone.

3 - TLP unlocks on incoming call (this is where the red stripe changes into a white stripe)

4 - I answer the call

5 - I end the call

6 - the white stripe still visible

7 - slide the keyboard out, the thin white stripe is still visible

8 - slide the keyboard back in, the thin white stripe get fat :)

I hope you can reproduce it on your side :)

See attached log file. Oh yes, it only produced 1 log file !?
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
My bad... sort of

Zuinige Rijder,

This line issue started happening in my altered 2.3.1 version after implementing the SPB scrolling fix. I did fix it in my version but I can't remember exactly what I did. I am pretty sure it was something to do with the InvalidateWindow function. I either added it somewhere or removed it or moved it. Unfortunately I no longer have that code as I have since altered it so much that I am never even calling InvalidateWindow anymore since my version doesn't use the clock, or the line, but rather just shows a blue lock icon in the top right corner and never needs to be invalidated.

If you need help let me know, I feel somewhat responsible, although I do remember my disclaimer that it was working fine for me at the time but wasn't sure if it would mess something else up somewhere.

I use MyMobiler a lot when I'm at my pc (freeware that lets you see and control your Windows Mobile Device from your desktop pc). It has a portrait/landscape toggle that should reveal the problem since you don't have the keyboard to slide out to control the toggle (you have a diamond right?).
[Touch Diamond, MDA Compact IV Themes and Apps] k000:
Can I keep the hardware keys enabled hwile only the touch screen is disabled ?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, see other settings screen, LockTouchPanelOnly.

Off topic:

There are a lot of questions asked about locking the hardware keys only. I must admit, this would be a great enhancement to TouchLockPro, in combination with a Slide 2 Answer with incoming calls.

The HTC API I use, locks the hardware keys AND touchpanel and for extra safety I have another touchpanel locking method on top of that. The latter is already activated at suspend, the hardware keys are immediately locked at wake up (cannot be done at suspend, because then also the power button is locked :rolleyes:)

Because I do not have a foreground window, locking the hardware keys in a normal winodws mobile way is not possible. But by subclassing foreground windows, there is a possibility, which is used by DredSensor. I did have bad experience with subclassing, maybe I will give it a try again as option.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I see 2 logfiles in the zip.

In the logfile I see the slider getting out:

18:09:32 747575250 SetSliderOut(true)

What I see, however, is that the following method is not called:

ClockOrientationChanged

This method is responsible for detecting portrait or landscape, so it looks like the portrait/landscape mode is not detected and the stripe is just drawn like it is portrait. Looks like this is not executed with your settings.

This does not yet explain while there is a white stripe shown, because it should be red. I will look into that too. Probably I will post a test version, to see if the problem disappears after some changes.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Do not worry, I doubt it is because of the changes you helped me with. But of course, you never know. I use myself MyMobiler too, so I will test with that. But I suspect it is a problem with stripe mode settings in combination with not detecting portrait/landscape (see previous post).
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
I'm confused. Hasn't this been an option for quite a while? LockTouchScreenOnly? I've always used this. I've never had any issues with it. It "disables" the screen and leaves the buttons enabled....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
replied on the wrong message
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You are right I misunderstood the question. Other people are asking for a possibility to only lock the hardware keys and not the touchpanel. The latter is not possible.
[Touch Diamond, MDA Compact IV Themes and Apps] Whistle_Master:
Padlock icon ?

First, thank you very much ZuinigeRijder for this application!

Then, I tried to find in the last 197 pages of this thread the answer but unsuccessfully, so I apologize if it was already asked :)

I'd like to know if it's possible to have, like it was in (the late) Sensor Lock, a notification icon (padlock) displayed in the task bar when the phone is locked instead of the BattClock or the Strike ?

Thanks in advance !
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
This should not be so difficult to add. I will put it on the wish list.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, let me know the outcome.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Version 2.5.2

I uploaded version 2.5.2 wich should fix your problems.

Cross my fingers :rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I assume you only want an icon when locked and not when unlocked?

The default size of the BattClock is 64x48, but normally the icons are 32x32. I assume you want also a 32x32 size icon? Do you have a good icon you want to show when locked?

I had an icon in StylusLock. Maybe not so nice......
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
Sorry :( The problem is still present.

The white stripe was gone in landscape mode, but I slide the keyboard back in, :( , the large stripe was back in portrait :(

See attached log files. Also note that my Stylus sensor is defective, this is why you see it as out, but I disabled it.

Thanks,

Eric
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmm, I cannot reproduce with MyMobiler. Looking at the logging, I did have another small change which could work. But I am not sure, because I could not reproduce. See attachment for the new test version.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
I guess your last code change did the job !!! I cannot reproduce the problem :D I also tried after a soft-reset to be sure, and it's fine :)

Thanks for the great support!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Great :) Let me know if no problems occur during the whole day (I am using it also with the default settings). Then I can upload this trial version as official 2.5.3 version.....
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
Sure, I will keep testing during the day, and will let you know how it went.

Thanks