Re: Gorm can edit which types of files ?
Gorm should be able to edit gorm files. It can read nib files and edit them but I would recommend saving them as gorm files as the nib export has never been perfect. I’m not sure why you wouldn’t be able to edit them. There are some older nib files with which Gorm may have some issues. Whether it’s worthwhile fixing these issues is a matter of debate since the older nib format is no longer in use. GC On Mon, Dec 25, 2017 at 18:25 Daniel Santoswrote: > Could you reply again ? Your first reply didn’t have any text > > Thanks > > > > On 25 Dec 2017, at 22:54, Riccardo Mottola > wrote: > > > > > > > ___ > Discuss-gnustep mailing list > Discuss-gnustep@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnustep > -- Gregory Casamento GNUstep Lead Developer / OLC, Principal Consultant http://www.gnustep.org - http://heronsperch.blogspot.com http://ind.ie/phoenix/ ___ Discuss-gnustep mailing list Discuss-gnustep@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnustep
Re: Gorm can edit which types of files ?
Could you reply again ? Your first reply didn’t have any text Thanks > On 25 Dec 2017, at 22:54, Riccardo Mottolawrote: > > ___ Discuss-gnustep mailing list Discuss-gnustep@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnustep
Re: Gorm can edit which types of files ?
___ Discuss-gnustep mailing list Discuss-gnustep@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnustep
Gorm can edit which types of files ?
Hi and Merry Christmas, I was trying to select elements on one of the NIB files in the GNUMail project, a noticed that I can’t seem to do that on NIB files, only on Gorm files. Is it really lijke that ? Or am I missing something ? Cheers ___ Discuss-gnustep mailing list Discuss-gnustep@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnustep
Re: Mysterious crash in NSRunLoop, using libobjc2 on Linux
On 21 Dec 2017, at 07:11, David Chisnallwrote: > > On 20 Dec 2017, at 21:08, Lobron, David wrote: >> >> The [NSException raise] method just calls "@throw self" when >> _NATIVE_OBJC_EXCEPTIONS is defined > > It does, but [NSException raise] is another function (well, method, but after > the call to objc_msgSend it’s a function). The exception is thrown from > there, not from the stack frame containing the @catch block. It turns out that this is the crucial bit: throwing an Objective-C exception through a C++ catch (or ObjC++ @catch) block was broken. This is pretty uncommon, but we now have a test for it and it appears to be passing. I’ve also tweaked the build system so that we now don’t build a separate libobjcxx, which should give a more consistent interface. David ___ Discuss-gnustep mailing list Discuss-gnustep@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnustep