gnustep / apps-projectcenter Goto Github PK

Procedure to reproduce:

1. Create a new project
2. Go to the command line and create a directory and a new file to add to the project
3. Go to ProjectCenter and add the file to the subdirectory
4. ProjectCenter will copy the file to the root of the project instead of referencing it where it is.

Expected:

PC should be able to get the file from its existing location.

Workaround: Create the file in the existing directory.

Why this workaround is unacceptable: For larger projects it might be necessary to incorporate code like this without creating a sub-project.

The release file ProjectCenter-0.7.0.tar.gz.sig doesn't appear to be signed correctly and causes issues with AUR build process.

Here is the output of gpg --verify:

gpg --verify ProjectCenter-0.7.0.tar.gz.sig 
gpg: assuming signed data in 'ProjectCenter-0.7.0.tar.gz'
gpg: Signature made Fri 03 Feb 2023 06:00:33 AM EST
gpg:                using DSA key BA075B9FA4C0EA04C96F9FD25023D366016912D0
gpg: Can't check signature: No public key

compare to gnustep-gui's signature which is correctly signed:

$ gpg --verify gnustep-gui-0.30.0.tar.gz.sig 
gpg: assuming signed data in 'gnustep-gui-0.30.0.tar.gz'
gpg: Signature made Thu Dec 29 04:10:15 2022 EST
gpg:                using DSA key 83AAE47CE829A4146EF83420CA868D4C99149679
gpg:                issuer "[email protected]"
gpg: Good signature from "GNUstep Maintainer <[email protected]>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 83AA E47C E829 A414 6EF8  3420 CA86 8D4C 9914 9679

ProjectCenter has an issue with running from the dock on versions of WindowMaker 0.95.8 and below.  This is because the wmaker executable sets the GNUSTEP_USER_ROOT variable in its environment which prevents make from running properly.

This doesn't present a problem with any other application except those which might run make.  One of them is, of course, Terminal (which can be fixed by putting unset GNUSTEP_USER_ROOT in your .zshrc/.profile/etc file) and the other is ProjectCenter.

This cannot be removed in any other way other than to fix the environment within PC somehow. The workaround is to start the application from the command line or some other environment which doesn't have the variable forcibly set.

This is a blocking issue and should prevent a release of PC.

Renaming of a gorm file during another file' editor being active leads to exception:

2021-02-06 11:26:46.021 ProjectCenter[429404:429404] Problem posting <GSNotification: 0x55f803c39df0> Name: NSTextDidEndEditingNotification Object: h=-&- v=-&- <NSTextView: 0x55f8040387c0> f={x = 4; y = 2; width = 226; height = 22} b={x = 0; y = 0; width = 226; height = 22} Info: {NSTextMovement = 16; }: <NSException: 0x55f803f5a500> NAME:NSRangeException REASON:in replaceCharactersInRange:withString:, range { 9223372036854775807, 0 } extends beyond size (33) INFO:(null)

The case is because PC doesn't have editors for gorm files so the last viewed file,
not the renamed .gorm, is present currently to the user. The precise cause is
not checking NSRange on NSNotFound in the -[renameFile:toFile:] after
the line 1465:

range = [_editorCategory rangeOfString:fromFile];
[_editorCategory replaceCharactersInRange:range withString:toFile];

the active editor's path can have nothing common with the renamed path.
I added the following check to get rid of the exception:

range = [_editorCategory rangeOfString:fromFile];
if (range.location != NSNotFound)
{
[_editorCategory replaceCharactersInRange:range withString:toFile];

Also may be worth to deactivate any editor when a gorm file is selected.

Project Center should copy the help file that is specified into the bundle and generate the entry in the GNUmakefile

Steps to reproduce:

1. Open a project
2. Open a file, possibly AppController.m/h
3. Copy a line vie the main menu
4. Paste it via the main menu
5. in the main menu, click Undo.

Result: Application may freeze
Expected: Changes should be undone

Comments: Not sure what is happening here, but I suspect the array or list of events for undo have a cycle of some sort.

• Split out Rennaisance project type
• Add new project types for other supported targets