Hi...
I just talked to Almindor and he arrived to the conclusion that there's something unfinished on WinCe LCL hooks.

There are two roads to make his lnet libs working:
1) make the hooks he normally use work, actually they seems to exist but they do nothing or make the application crash when called
2) make the ttimer work on wince, so he can call the CallAction function that manages the connection "sometime" indipendently from the application. That would be a workaround (so useful for me) but not the definitive solution for lnet.

I found that recent mail:

in wich Roozbeh talks about ttimer and it seems that he's working on it.

I just want to know if there are any news in that direction, due to the need to have lnet finished to avoid my cross-compile problems and get my application done.

Thanks in advance for any answer.

p.s. i'm trying to understand who works on wince, i got some minor bugs to report too, like a combobox-onclear()-width-odd-auto-shortening and something else.

From:

Please separate wince support in compiler and RTL/FCL and Lazarus and LCL. I work on wince support in compiler and RTL parts. You can report any issues in this area.

Yury Sidorov.

2) make the ttimer work on wince, so he can call the CallAction function that manages the connection "sometime" indipendently from the application. That would be a workaround (so useful for me) but not the definitive solution for lnet.

TTimer does not work on WINCE ?!?!?

If this is the case, you can't create anything but command-line tools that just block until their work is completely done. This is OK for pure FPC programs, but anything "Lazarus-Like" (using the LCL) will need such a thing.

-Michael

No... the LCL works and a lot of things can be currently done, but the TTimer component is not implemented due to differences between win32 and wince api(s).

Reading this: http://www.rainer-keuchel.de/wince/wince-api-diffs.txt

You can read:

GetSystemTime()

The milli member might be zero. This is strange as GetTickCount() returns millis (but since start of system).

That is (MAYBE) one of the differences that caused the fact that ttimer is still not working in wince.

There is a Roozbeh's mail in wich he says that he's working on it there:

Time is absolutely irrelevant to Timer.

Vincent

Yury Sidorov ha scritto:

Ok, so:

When i Clear a TComboBox, if it's width was 100, it shorten automatically becoming a 90 TComboBox. (I didn't tested the effective shorten difference, it's of course the "scroll box arrow's" width.

Another one is the PATH function that is still not implemented... in Windows Ce there seem to be a Linux (LOL!) paths using cause all is under a / root.

I know that Roozbeh was working on the ttimage component, that still cause a segmentation fault if used (like the Tbitbtn).

Just cause i'm there... I pick the occasion to signal this website: http://ccrdu.de/index.html
In wich the blogger shows (last post at the end of the page) a wince application that he did with lazarus and i don't know which framwork he did by himself, in the image is possible to see some components that we still can't use, like the image, and there's a file scrollbox too. (the appeareance looks good too).

I saw that roozbeh already tryed to contact him:
http://www.blogger.com/comment.g?blogID=30486030&postID=116454440043529173 and mee too, and he seems to be interested to collaborate.

Hope i was useful ;)

Vincent Snijders ha scritto:

I'm really a newbye in that things, i was just guessing :D

I just hope that one of that two issues will be resolved soon :D

Bye

Huh? Just look at Spybot S&D, the WinCE version is written with FPC and it's definitively more than a console program.

Last week I used the crosssnapshots from Vincent to crosscompile a simple forms using app (one form, several widgets).

The application worked fine, and the "complicated" manual to this looked as follows:

1 install laz 2.1.1 snapshot
2 install laz 2.1.1 wince cross supplement
3 create app
4 set widgetset to CE, cpu to arm, target to CE ( so three in total!) 5 compile
6 copy to pda
7 run.

Marco van de Voort ha scritto:

Yes... i'm doing that from more than a month, the problem is that some components are missing, like lnet, for the problem i told in the previous emails...

p.s. i didn't knew that he was usin lazarus to make a spybot search and destroy for wince, that's good, but how did he managed to use networking without working components? he's doing it all alone?

I got reports that several Indy components were working. I'd have checked this by now if I wouldn't have had some machine trouble (and access to Indy Starteam with that). I'm going to try to get starteam working this weekend.

p.s. i didn't knew that he was usin lazarus to make a spybot search and destroy for wince, that's good, but how did he managed to use networking without working components? he's doing it all alone?

Maybe he is not using lnet?

From:

Another one is the PATH function that is still not implemented... in Windows Ce there seem to be a Linux (LOL!) paths using cause all is under a / root.

What do you mean PATH function?
WinCE does not have current directory. All path must be absolute "\Myfolder\file.txt".

Yury Sidorov.

p.s. i didn't knew that he was usin lazarus to make a spybot search and

It was about FPC, not lazarus. Afaik Spybot uses an own gui library for wince.

destroy for wince, that's good, but how did he managed to use networking without working components? he's doing it all alone?

Probably to get a efficient and as small as possible application of it has network support.