Moving Files Bug

[seb5594]

Found another Bug :)
If you try to move a file in a project to the same folder you just get as response i can't move a file to the same folder but i can't abort the folderdialog

[lufinkey]

I'm not updating miniCode for that. I'm sorry but this project has an
absurd amount of bugs, which is why I'm dropping it and making something
better
On Jul 28, 2015 5:23 AM, "seb5594" notifications@github.com wrote:

Found another Bug :)
If you try to move a file in a project to the same folder you just get as
response i can't move a file to the same folder but i can't abort the
folderdialog

—
Reply to this email directly or view it on GitHub
#11.

[seb5594]

Okay i can understand your point.
Is there any way to try a pre-release or beeing tester of your new app 'iCode'?

[lufinkey]

I'm not in a beta stage. The source code is available for people to
contribute to, however
On Jul 28, 2015 9:28 AM, "seb5594" notifications@github.com wrote:

Okay i can understand your point.
Is there any way to try a pre-release or beeing tester of your new app
'iCode'?

—
Reply to this email directly or view it on GitHub
#11 (comment).

[seb5594]

Thanks for your fast response!
Could you link me to the source?
Thanks in advance

[seb5594]

nvm found it.
If you want you can close this issue, your choice.
Have a nice day :)

[iloving]

Any news on this "something better"? I'm trying to make it work under iOS 9.0.2, but when I try to build the template blank console application, I get "minimal/mapping.h(54): _assert(false); errno=2"

[lufinkey]

Progress on "something new" is coming along, but slowly. You can check out
progress at http://github.com/lufinkey/iCode

As for the bug, I'm aware of it, but I'm not going to be maintaining
miniCode anymore.
On Oct 16, 2015 5:23 PM, "iloving" notifications@github.com wrote:

Any news on this "something better"? I'm trying to make it work under iOS
9.0.2, but when I try to build the template blank console application, I
get "minimal/mapping.h(54): _assert(false); errno=2"

—
Reply to this email directly or view it on GitHub
#11 (comment).