Quote:
Originally Posted by Teranoz
1. What programming language do you use
2. What type of ocr, pixel comparing ?
3. The datafiles are not compatible with anything else, please store as comma seperated files, xml or whatever standard, so I can also import data from neomap
4. Date is mostly bugged, getting 1970 in 90% of the drops, why not just use system time with or without an optional offset for MA time.
5. Split ores and enmatters, maybe use Ctrl+0 for enmatter and 0 for ore or so |
1. Combination of oldfashion C and newer fashion C++.
2. If you would forget all layers used it would be pixel comparing. That was the basis.
3. An Import is possible to make. I have export's for mining as well. All I need is a request like this one. But its not worth the effort if someone doesn't need it
Till now, nobody did. It's not very hard to add. I don't use neomapper so an ready to use example file would be welcome and save me a bit of time downloading and installing. With an example I could strive to add this in the following update.
( edit: to late, next update? )
4. Date bug is known though not mentioned on the site. After saving and reloading it usually shows fine. Thnx for repeating that one, cause I almost forgot it. I'll try to fix this in the next update. Should be somewhere this week.
( edit: now fixed )
5. Splitting ore and enmatter. My question is Why? What goal/purpose would that have? What would you like to see or how do you want to see it split? The answers would hopefully give me an idea to what I should strive towards except for splitting them. Instead of different keys, I could add the knowledge to the app so it could seperate them for you. I personally have done either an Ore or Enmatter run so I never needed the option as it was already split.