Re: V17 MSC Reports Orphaned Methods...
Hi Tim, I’ve only noticed this behavior on this particular structure. I’ve accepted it somewhat after I realized that most of the recent anomalies go away after restarting 4D. Thanks, Robert Sent from my iPhone > On Nov 17, 2018, at 7:11 PM, Tim Nevels via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > It’s just a 4D bug in how it handles deleting methods connected to objects. > It does a less than perfect job of handling this. Sometimes it does it right, > sometimes it screws up. Been this way for years in untold number of 4D > versions. ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
Re: V17 MSC Reports Orphaned Methods...
Hi Robert, You worry too much. Orphaned methods are nothing to lose sleep over. It’s just a 4D bug in how it handles deleting methods connected to objects. It does a less than perfect job of handling this. Sometimes it does it right, sometimes it screws up. Been this way for years in untold number of 4D versions. My philosophy is that when I see references to orphaned methods I simply delete them and move on. I don’t even give it a second thought. There is a line from an old Chicago song “you learn to live with it... but I don’t want to” that really sums it up for me. :) Tim Sent from my iPad On Nov 17, 2018, at 2:00 PM, Robert wrote: > Actually I was using build 229490 but now I’m using the most recent (229707) > with the same behavior as previously reported. ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
Re: V17 MSC Reports Orphaned Methods...
> So, any thoughts on how to get a clean bill of health from MSC…? I’ve deleted > all orphaned methods, repaired & compacted the structure. I’m running out of > things to try. Try deleting the 4D.indy then do a repair. I had a similar problem and this seemed to work for me. Neil -- Neil Dennis 4D Developer since 1990 GreaText - Designing Software for the Way You Work 716 East 1850 N North Ogden, UT 84414 mailto:npden...@greatext.com http://www.greatext.com/ ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
Re: V17 MSC Reports Orphaned Methods...
Actually I was using build 229490 but now I’m using the most recent (229707) with the same behavior as previously reported. Thanks, Robert > On Nov 17, 2018, at 1:10 AM, Robert ListMail via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > While using v17R3 (Build 17.228509) ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
Re: V17 MSC Reports Orphaned Methods...
Okay, after a lot of testing…. I noticed that after deleting a form object and seeing MSC report the warning, on a couple of occasions the “anomaly” was cleared solely by re-launching 4D. I still would like to ensure that I have a clean, corruption-free structure and for MSC to report a clean bill of health. So, if you have any ideas on what to check, I’m all ears. BTW: I could see that the 4D Forum shows that this was an issue with an old V13 beta but was quickly fixed after being reported by Tony R. Robert > On Nov 17, 2018, at 1:10 AM, Robert ListMail via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > MSC shows that there is an anomaly...The problem is that this issue continues > after the structure repair. ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
V17 MSC Reports Orphaned Methods...
While using v17R3 (Build 17.228509) and v17.0 HF3, I noticed that my converted structure (coming from v11) that I’ve been regularly modifying during this v17 upgrade started to report anomalies via MSC Verify. To reproduce a problem I just delete a from object that was recently duplicated, just for testing and then MSC shows that there is an anomaly. On several occasions, orphaned methods (sometimes up to 93 orphaned methods) were viewable via Explorer and were deleted (and the Trash emptied) and sometimes MSC just completed the repair (seemingly without issue). However, deleting a single object (testing with two different forms) will trigger the warning: "The method resource CC4D of id 17 is not used anywhere”. The problem is that this issue continues after the structure repair. So, any thoughts on how to get a clean bill of health from MSC…? I’ve deleted all orphaned methods, repaired & compacted the structure. I’m running out of things to try. BTW: a few days ago, I noticed that I could not select buttons on a form I was working with and I could not duplicate that form either. I rebuilt that form copying some of the objects and all seemed well. MSC did not report any issues at the time. Here is one screenshot of the larger warning list…. https://www.dropbox.com/s/6wmk6nqb3qp7o8c/Screenshot%202018-11-16%2019.44.33.png?dl=0 Thanks, Robert ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
