yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Hello ElfKaa,

Thank you for your message.

You seem to be stating there is no issue with initial delay if a moving finger is placed on the screen and the map moves near instantly as expected, and that the initial delay experienced is introduced by delaying moving the finger initially as previously detailed? Please clarify. (The behaviour of the classic implementation in 4.10 is not directly relevant to the new implementation in 4.11beta1/beta2 as it is a different implementation.)

I cannot determine a clear answer from your response regarding the actual smoothness and fluidity of the map you experience when in motion? Please clarify.

It is apparent from your description as I had thought, there are some obvious differences between your map and mine which probably account for the differing observations. My map with all tiles present at all zoom levels, in the same type and same format as previously detailed works flawlessly as previously detailed. I cannot even fault it despite attempts to do so by slowing the device down and removing tiles deliberately.

Your map with missing tiles at at least some zoom levels and with two different map types and two file formats presents the issues you describe.

It seems to me when the new implementation is fixed to handle missing tiles and two different map types and tile file formats as per the classic implementation, the issues you describe should be resolved.

If you could upload your map (private message the details if you wish), I would be keen to see if I can reproduce issues you report and provide some detailed analysis of what is actually happening. I can also then assess how the HTC HD2 handles maps of this type in terms of smoothness and fluidity. I have no issue with the download size.

I would say as both existing map implementations are already developed, it makes sense to retain them having applied any necessary fixes. The 9x backbuffer implementation can be developed also and incorporated as well if necessary. The end user can then be allowed to select their preference based on which implementation works best for them in their circumstances.

Existing Maps Classic Implementation - as within 4.10

Existing Maps New Implementation 1 - as within 4.11beta2 with fixes to be applied

Proposed Maps New Implenentation 2 - 9x backbuffer awaiting potential development

low.flying.pigs
[Touch Diamond, MDA Compact IV General] ElfKaa:
Hello low.flying.pigs,

Please, wait for the Klaus fix, then we can test what will be done. The beta 2 has a bug in the displaying the map. I guess when the Klaus will fix it I will not have any black screen for my maps at all and the problem for moving the map by finger delay - it will never be as smooth as before until there will exist another type of implementation. The reactions will never be as fast for non existing map that must be rechecked every small move where to move from the one that exists yet in the buffer and then display.

I have not tested it in motion yet. But it will probably behaive simillar to the old one - there were also the slower reactions but this is not what is this topic about. I only tried to move the map using my finger and yet it is very frustrating to me if I could not move continuously. And I have the same result as you (250-500ms).

I don´t think you can have the whole map at all zoom levels - I have it also for a small part of about 5 km from the most far to the nearest zoom level possible combining more map sources for each zoom level together. I have nothing special from you. Everything I have you can do by yourself as I did. I will write you PM to explain you how to create the map the same as I have.

It is not normal behavior, this does not happened in the previous implementation.

Yes, as I understand, it is a bug and it will be fixed by Klaus in near future.

I don´t see any reason why to have three implementations if the backbuffer one should be the best without any compromises. The only option then can be the size of the backbuffer. You should not have 9 times bigger buffer, you can have it only 4 times bigger if you use half the screen size! For the motion it should be sufficient, no one moves as much fast - yes it is depending on the zoom factor as well. Or you can use 1x screen size if you will use the old one style - without backbuffer as it was before. But now we have also to wait for Klaus reaction.
[Touch Diamond, MDA Compact IV General] Cheque:
well guys, I don't see the need of a three pages discussion about how fluent a map move should be; regarding saving resources and battery power the "old way" was just fine for me (tap on screen, moving map, reprint new area on drop).

anything else is just eye-candy fancy stuff;

the program works very fine and usability is good.

btw

I'll try the T2F feature today and give feedback
[Touch Diamond, MDA Compact IV General] ElfKaa:
Yes, now it is too much talk about nothing. I will not continue this discussion until Klaus will do the beta 3. Then we all should test and see what is the best way to do.. Sorry to low.flying.pigs :cyclops:
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Dear profaner667,

I will assume you know basically what to do and are struggling with writing the script itself. Essentially, a mortscript to copy a folder from a source location to a destination location, and then run an .exe inside that destination takes the form of the following example. If you adapt the example to correct the folder names and structure as applicable to you, and run the mortscript in the proper way, in ordinary circumstances it should work (your circumstances appear far from ordinary or normal).

Copy ("\Source\Folder\", "\Destination\Folder\")

Run ("\Destination\Folder\GpsCycleComputer.exe")

EXIT

If you are loosing user data, I cannot at the moment foresee a way to automatically run the script at startup, as either the script itself, or whatever directs to the script stored elsewhere will be lost as well. The mortscript will have to be stored on the memory card and run manually from there. I can see there is still some slight advantage over copying the files manually, but it is only slight. If your really cannot get mortscript to work, I would suggest manual copying and execution if it works for you and is really all that is required.

I would be genuinely interested to know what device you are attempting to use and the applicable OS, and what underlying issue exists that causes the loss of data in the first instance, and to get to the bottom of this.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
That comment following those of Cheque should help ensure some who may have been considering contributing no longer do so, serving only to limit discussion in a discussion forum designed for the sole purpose of discussion, in turn serving only to hasten the demise of GCC as previously detailed. This is a shame.

That is a shame also as having created an approximation of the maps you describe as you will no longer provide your actual maps despite having said you would, I can find no lack of smoothness or fluidity at all in beta 2.

Beta 3 could be hurried along by abandoning the buffer increase implementation. Then there is nothing to test and no new implementations to develop.

Cheque it would appear wants no innovation or discussion at all for maps (and presumably anything else not of personal benefit), and was happy with the classic implementation and will presumably be pleased therefore with it's abandonment and avoidance of further "eye-candy fancy stuff".

ElfKaa is satisfied with the classic implementation experiencing non of the problems they claim to have with the new implementation, and will be similarly pleased with it's abandonment.

It seems a selectable option between the existing classic and new implementations is all that is really necessary at this stage based on contributions received thus far, allowing satisfaction of all and development resources to be directed in to other areas.

What exactly are you apologising to me about? If you wish to apologise, do so to the users and readers who may otherwise, to the detriment of all, be dissuaded from contribution.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] ElfKaa:
Hello low.flying.pigs,

with all the respect, it seems to me you didn´t understand what will happen if the buffersize will be increased.. The main task was about the map can maybe to be displaying continuously. It - maybe - should be superfast as I imagine - when you increase it 9x times - you will have no chance to overmove the buffer on one touch and move (hold, then release). You will see the map moving while you will be holding and moving because the map will be in the buffer. When you release the finger the parts that are yet hidden outside the screen will be redrawn to a buffer, so will be prepared to another move and this is that you will not see any black or redraw, you may move to any direction with NO wait! Not just a small but truly NO delay!

You didn´t told any contra and I just see only pros and NO contra! The only should then be the memory size increase and we must wait for Klaus opinion - I am not a programmer and I am not able to say this! So - I still maintain on that it may be the best you should yet have.

If no - just say why!

If it is not possible as I imagine it - the Klaus will say - no, this will be not like you imagine..

The problem of moving on my device is not caused of any maps - I think it should´t be! If you like - send me your maps and I will test it on my device - and I guess that it will behave the same!

The black is caused of the programming bug as Klaus already said and I will wait for the next beta for further testings!

Lukas
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Hello ElfKaa,

And with equal respect, then you are wrong. The point was the existing new implementation can work with near imperceptable delay. I tried in vain to establish why it does not for you.

And with continuing respect, you are again wrong. A reasonably extensive list has in fact already been provided, as below:

So what does cause it then? You claim it is not your background tasks so you are not struggling for RAM or suffering any conflicts wtith those or TouchWiz UI as you will of course have checked that before making such a statement. Besides the Samsung S3C6410 800MHz CPU, you even have a dedicated hardware graphics accelerator. I am genuinely interested.

Licencing issues prohibit this.

I will ask around to see if anyone has or can get hold a Samsung I8000 Omnia II and test out my maps myself, along with an approximation of the maps you describe as you will no longer provide your actual maps despite having said you would.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] Blaustein:
Hello guys,

I find almost no time for improving GCC because always reading long and needless posts...

The 9-times backbuffer has one important drawback: it needs 9 times the time to fill. If it now takes 200 to 500ms, it will last 2 to almost 5 seconds to initialize the first time (switch from main). Later when shifting it will take about 3 times the time when lifting your finger and you have to wait before you can begin another shift. Maybe you start the second shift and really nothing is happening. And these two things I feel is frustrating. Moreover, if a function is more than 1 sec, there may be missing track points which will not be logged. It makes only sense if filled in a separate background thread - an this is definitely overdone for a eye-candy fancy stuff.

I prefer the new solution (which is indeed less code) and is in my eyes nice and fluent enough (even on my low performant 200MHz device). In the old solution you see a black screen, now you see a slightly lag behind image. In the same time the old image appears (from black), now the new image moves to the intended place (this worked in beta 2 not so good).

I have included a temorary option in popup menue to enable the old implementation, but I intend to remove it instead of implementing full (store in settings).

Further improvements in 4.11 beta3:

- option to hide only text of waypoints

- access to navigation screen by tap on nav arrow in map

- option to use more than 4096 points (up to 256K)

- I have rewritten parts of Graph (Altitude, Speed)

- I have rewritten big parts of navigation feature which should solve some issues (there is a new wave file "TurnOver")

- some minor things

Klaus
[Touch Diamond, MDA Compact IV General] Cheque:
thanks Blaustein. I really appriciate it.:cool:

yesterday I did a tour on bicycle, using T2F for driving directions.

On Map screen, in some situations the T2F line disapeared which made me curious whether to turn somewhere. I didn't really figure out how to get it back, but it appeared again by it's own. (this was experienced with 4.10, I didn't use your 4.11 beta, but I sure will next time)
[Touch Diamond, MDA Compact IV General] ElfKaa:
Hello Klaus,

it sounds good :) Thank you for your explanation, I am also happy with the old one implementation in 4.10. To me it is not much necessary to be all the parts visible during moving my finger.. Any waiting is a complication.. :)

I will test beta 3 new implementation..

And sorry for the long writing before - I only just tried to answer many many questions.. :cowboy:

Lukas

---------- Post added at 12:58 PM ---------- Previous post was at 12:54 PM ----------

It seems to me that it is caused of that both of single points are more far then the screen size - if both of the waypoints are not in the screen at a time, the line will disappear.

Lukas

---------- Post added at 01:22 PM ---------- Previous post was at 12:58 PM ----------

Hello Klaus,

I tested the map view moving by finger..

If I get to where I have not current zoom level map it is correctly shown the first existing under (no black now appears) , but on the border I sometimes have black lines between the current zoom map tiles and the level under tiles.. They didn´t fit as perfect together..

That is the only imperfection I have found yet..

:good:

The map moves relatively ok, it seem like it moves as fast as Google maps yet.

But to me it is better to use the old style even that because - I catch the object, move where I would like to have it and release it and the rest of the map will be redrawn in just a moment..

So please - don´t remove this option - it should still be better in some cases (and it is nothing about anything and doesn´t matter any further options) - and it is perfect that it is quickly accessible just right on the map screen itself. :good:

Lukas
[Touch Diamond, MDA Compact IV General] Blaustein:
Hello Cheque,

T2F dissappeared: this happens when you have only few points in t2f and no one point is within the screen area. Zoom out can bring t2f back. But the navigation arrow should function properly nevertheless. I try to improve this.

Hello ElfKaa,

the black lines between tiles appear sometimes I think due to rounding errors. This also happens in the same zoom level when all tiles are available and this happend also in 4.10.

If you tap your finger on an object and shift it where you want to have it and lift your finger it should move there with the new implementation within the same time as the redraw in the old implementation.

Klaus
[Touch Diamond, MDA Compact IV General] ElfKaa:
It don´t happening to me if I switch to old implementation.. Just the new one do this to me.

No, when I hold the object and move:

In old implementation:

I can move it as my finger is moving - exactly under my finger!

In new implementation:

I move my finger, then the object will follow me after quarter second. Yes - I can move my finger but then I must wait for the object become :)

I will better wait for the rest of the map after I move what I wanted to move as I see the most of the map already then every half second wait for the whole map redraw and the object follow.. I could´t imagine the future look (never mind of that the rest of the map is black) and it is much easier to perfectly set something somewhere immediately then must to wait and then see..

Lukas

---------- Post added at 02:43 AM ---------- Previous post was at 02:11 AM ----------

Oh no,

now the GPS Cycle Computer crashed to me :(

And after reseting my phone I am not able to start it again :(

It gaves me an error ArgumentOutOfRangeException.

And that I should install NETCFv35.Messages.EN.cab to display a message or what..

Error is in:

System.String.Substring(Int32 startIndex, Int32 lenght)

GPSUtils.Utils.DrawClock(Graphics g, Color col, Int32 ... and so long.. :)

The previous version works just fine - I mean 4.11b2

This only do the 4.11b3 now..
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Hello Blaustein / Klaus,

Many thanks for 4.11beta3. Appreciated as always.

Map smoothness and fluidity on the HTC HD2 remains excellent as previously detailed, as it has been since the new implementation was introduced in beta1.

As expected of such a capable device, following testing using a Samsung I8000 Omnia II running betas 1, 2, and 3 using both my own maps and an approximation of the maps ElfKaa describes since ElfKaa will not provide their actual maps having said they would, I can confirm map smoothness and fluidity is excellent on that device also.

I have made extensive efforts with good intentions, yet in vain, if it genuinely did not work similarly for ElfKaa, to establish why, yet could not as their overriding concern appeared not with resolving their claimed issue with the new implementation, but with its definite removal, and instead promoting their own 9x backbuffer implementation, and only retaining the classic implementation if their own proved unworkable.

I consider that to be the end of the matters of map smoothness and fluidity raised by ElfKaa. It seems there is nothing further I can do in that regard having exhausted my best efforts, other than to advocate again as I have throughout selectable options between the existing classic map and default new map implementation, which we now have in beta3. Hopefully this option will be made a retained user setting instead of requiring change on each usage, for the ease of use of those that prefer / require the classic implementation.

With that concluded, I will in due course test thoroughly the new features of beta3 and report findings accordingly. First impressions are very good.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] ElfKaa:
To low.flying.pigs

:laugh:

you are the crazy tester.. ;) You have bought your own I8000 phone just for the testing purpose of the GPS Cycle Computer? WOW!

As I see you are more crazy than I have expected.. :cyclops:

As I wrote you PM my maps has together 4.14GB and if I will try to send it I will be sending it to you about a week..

And it should not be on my maps itself very likely! Don´t you think Klaus is the one who will ask me for them at first if there exist a chance it should?

There can be many other factors which can make problems. It can also be by the version of OS or all of the applications I am running on background.

If you are interested - you can install my czech version of Windows Mobile OS ;)

The version of OS I have is 5.2.23103 build 23103.5.3.3. PDA: I8000NXXJI1, CSC I8000XCSJI1 and phone: I8000XXJF1.

Try this first, on your own risk, then I will send you my registry and applications - then I will send you my maps - but - please - wait - I really have sloooooow upload connection - exactly it is 300kb/s not kB but kb - that is 39 kB per second at maximum! so I will be sending you 4.14 Gigs - how long? - you can count it by yourself if you like.. :)

And - do not worry about your favorite implementation, I see Klaus prefers also this new one instead of the old one. As he has just created it and - surely - it should be in many cases better! But - as you already said - I prefer the old one as I prefer the speed instead of to see the whole map after a while, and I still hope that Klaus will leave the option to choose for some other like me.

The bigger problem - as I see it - is the crash I have noticed and described upper, but it is also necessary to tell that the b3 worked the whole day before it has crashed while starting! But now it don´t start anymore while b2 still works! And to say that I was playing with Track2Follow feature previously when it worked, then I have closed it and I tried to save the T2F track several times without success as I don´t know how can I save my created track to follow.. It just saves me only the track I have yet traveled - to me it is blue line but not the green one..

And it leads me to the question to Klaus or anyone who know. How should I then save my track created using T2F edit tool?

Thanks.

Lukas

underline: At second - I have only unpacked the executable from the package and add to the folder I have yet in my device.. If something more has been changed it may cause that problem I described, I will test it if it is necessary.. But it is freaky that the b3 worked the whole day then after restarting, and charging the phone I tried to execute it again later and it has crashed while starting and till now it doesn´t work..

To low.flying.pigs

I have never told anything about to remove the new implementation instead my proposal of another solution - which was explained me that it shouldn´t be as I imagine it and will not be the solution..
[Touch Diamond, MDA Compact IV General] ElfKaa:
Hello Klaus,

it is very freaky behavior - the error just disappear by itself.. I can not explain how. I had the problem late at night yesterday. Today I didn´t restarted, just removed the SD card and connect to PC using SD card reader to check if the executable hasn´t changed for some inexplicable reasons and it don´t - I have compared it with the one included in the cab - and then return it back to phone while the system is running - no restart.. Then tried it again and voila - it started as before.

Then I restarted the phone and tried it again and it is now running alright without any problem - yesterday I have tried restart the phone few times with no success to start beta 3.

And also it seems to me that I have no black lines between the map tiles - I haven´t seen it for long - this happenings randomly - I could not get the black lines back ;) even I wanted to - so I don´t know how and when it will happen.

You can check it - but I think it is nonsense of something in my system or whatever.. I will recheck it later at night again if the problem is not somehow connected to time.. But it seems to me it is not a mistake in GPS Cycle Computer - but it is freaky that even when the beta 3 didn´t worked the beta 2 has started well yesterday.

Lukas