If need ;) I attach files for FileManager Plugin wx3.1.x (64 bit) with my upgrade:
- fix if drag items is null
- fix event on key Del press
- add checks when drag files: move or copy with prevent replace
- add checks when click move or copy from context menu with prevent replace
I know you don't want to read much or cooperate with us, but if you decide to change your mind sometime in the future you could check this link: http://wiki.codeblocks.org/index.php/Creating_a_patch_to_submit_(Patch_Tracker)
hot fix FileManager_rev0.2.zip (http://forums.next.codeblocks.org/index.php?action=dlattach;topic=24294.0;attach=10601)
Quote from: oBFusCATed on December 23, 2020, 12:01:54 PM
I know you don't want to read much or cooperate with us, but if you decide to change your mind sometime in the future you could check this link: http://wiki.codeblocks.org/index.php/Creating_a_patch_to_submit_(Patch_Tracker (http://wiki.codeblocks.org/index.php/Creating_a_patch_to_submit_(Patch_Tracker))
Okay, I'll read how to make patches. :)
FileManager Plugin wx3.1.x (64 bit) with my upgrade: svn 12295
- Add: fast button clear masks
- Fixed: collapse and expand items, cursor icons
- More: many fixes and edits to improve the code and performance of the plugin
You should post a proper patch, not the whole folder content. In fact, File Manager has changed since 12295 (see commits 12312, 12318 and 12319), so replacing the files is not possible.
Quote from: Miguel Gimenez on May 05, 2021, 05:00:55 PM
You should post a proper patch, not the whole folder content. In fact, File Manager has changed since 12295 (see commits 12312, 12318 and 12319), so replacing the files is not possible.
I svn up to 12295(with merge) and many more edits in codeblocks project, so I don't know how to make a patch for one plugin folder, if someone gives an example of how to do it, then I'll try and where to send this patch?
If I could create a new svn brunch for omlk repository, I would post changes there, but I don't have access.
Also I think my code is much better than edits in commit: 12312, 12318 and 12319
Here is an explanation how to make patches from svn: https://wiki.codeblocks.org/index.php/Creating_a_patch_to_submit_(Patch_Tracker)
You cannot make branches in svn, because you're not developer and branches in svn are heavy.
You can use git to do it (if you're more familiar with git) and base your branch on the master branch in https://github.com/obfuscated/codeblocks_sf
Edit: Just a hint for better success: If you can post a patch per fix it will ease the review process.
Quote from: oBFusCATed on May 05, 2021, 10:07:54 PM
Here is an explanation how to make patches from svn: https://wiki.codeblocks.org/index.php/Creating_a_patch_to_submit_(Patch_Tracker (https://wiki.codeblocks.org/index.php/Creating_a_patch_to_submit_(Patch_Tracker))
You cannot make branches in svn, because you're not developer and branches in svn are heavy.
You can use git to do it (if you're more familiar with git) and base your branch on the master branch in https://github.com/obfuscated/codeblocks_sf (https://github.com/obfuscated/codeblocks_sf)
Edit: Just a hint for better success: If you can post a patch per fix it will ease the review process.
- Any ideas on how to fix this for a large number of files?
- https://lookfirst.com/2008/11/subversion-inconsistent-line-ending.html
- dos2unix or unix2dos or another ways
$ svn diff -r PREV --summarize > omlk_12295.path
svn: E135000: File '/h/i/CB_src/s_merge - my12295/trunk/src/plugins/codecompletion/parser/cclogger.h' has inconsistent newlines
svn: E135000: Inconsistent line ending style
svn: E200042: Additional errors:
svn: E135000: Inconsistent line ending style
$ svn diff -x '-b --ignore-eol-style' -r PREV --summarize > omlk_12295.path
svn: E135000: File '/h/i/CB_src/s_merge - my12295/trunk/src/plugins/codecompletion/parser/cclogger.h' has inconsistent newlines
svn: E135000: Inconsistent line ending style
svn: E200042: Additional errors:
svn: E135000: Inconsistent line ending style
QuoteAny ideas on how to fix this for a large number of files?
unix2dos * will do it in the current folder, if you need to change subfolders use
find . -type f -print0 | xargs -0 unix2dos. Be careful, some files use Unix EOL.
You can generate a patch just using
svn diff > omlk_12295.patchunless you really need the reverse patch
$ svn diff -x '-b --ignore-eol-style' ./src/plugins/contrib/FileManager/ > omlk_12295_FileManager_rev0.3.path
File attached to this post.
Interesting:
1. wild reformatting changes for no apparent reason, uses tabs instead of spaces
2. switches to c++20, but still uses goto
3. fails to apply cleanly on latest trunk/master:
> patch -p0 < /tmp/omlk_12295_FileManager_rev0.3.path
patching file src/plugins/contrib/FileManager/FileExplorer.cpp
Hunk #34 FAILED at 762.
Hunk #52 succeeded at 1295 with fuzz 2.
Hunk #53 succeeded at 1305 (offset 1 line).
Hunk #54 FAILED at 1329.
Hunk #55 succeeded at 1366 (offset 3 lines).
Hunk #56 succeeded at 1385 (offset 3 lines).
Hunk #57 FAILED at 1395.
Hunk #58 FAILED at 1512.
4 out of 58 hunks FAILED -- saving rejects to file src/plugins/contrib/FileManager/FileExplorer.cpp.rej
patching file src/plugins/contrib/FileManager/FileExplorer.h
patching file src/plugins/contrib/FileManager/FileManager_wx31_64.cbp
patching file src/plugins/contrib/FileManager/se_globals.cpp
patching file src/plugins/contrib/FileManager/se_globals.h
This would be rough...
- I don't understand what's wrong with the patch yet? The patch should be set to r12295.
- What's wrong with goto?
I attached new patch include fixes from r12319, r12318
Quote from: omlk on May 07, 2021, 01:21:52 PM
I don't understand what's wrong with the patch yet? The patch should be set to r12295.
What do you mean by "set to r12295". The idea is to update to the latest trunk commit, make your changes and then create the patch.
If you're more comfortable with git you can use https://github.com/obfuscated/codeblocks_sf
Quote from: omlk on May 07, 2021, 01:21:52 PM
What's wrong with goto?
https://homepages.cwi.nl/~storm/teaching/reader/Dijkstra68.pdf
(Offtopic) Also it's patch, not path: https://en.wikipedia.org/wiki/Patch_(computing)
https://gofile.io/d/aDYz3n (https://gofile.io/d/aDYz3n)
File attached to this post. (https://forums.next.codeblocks.org/Themes/default/images/icons/clip.gif) FileManager_rev0.4.zip
@omlk if you do not follow the correct process then your changes will go into the bit bucket.
As you seem to not want to follow the correct process here it is AGAIN:
1) Make sure your changes are against the truck SVN or github sources. OR in other words get the latest source code before you post any patches the same day you are going to submit the patch(s) and if there are any updated merge your changes into the latest code and test the changes are still working and okay.
2) Create a proper patch file, not a zip file containing files usign one of the following :
a) Read http://wiki.codeblocks.org/index.php/Creating_a_patch_to_submit_(Patch_Tracker) to follow the CB process
or
b) Google "gnu create a patch file" and read how to create a patch file using the standard GNU diff utility if you have a GNU diff installed.
or
c) Use Github to create a pull request against. See previous past that has GIT repo to fork from in it (https://github.com/obfuscated/codeblocks_sf)
3) Create a ticket on SourceForge (https://sourceforge.net/p/codeblocks/tickets/)
4) Attach the patch to the ticket from 3) or include the Github PR URL in the ticket if you used GitHUB.
If you still want to ignore this and submit a zip file containing the files you have changed then you are wasting real CB developers time.