well... 4D's 64 bit readiness report said they wanted 7 days. I think it took < 1 to resolve all of them.
> I don’t know how critical those anomalies are. Some are cosmetic, > but others, like the scrollable area compatibility mode, might impact > functionality. We have over 3,000 to change, so it's going to take a > while. > > Tom > >> On Sep 19, 2019, at 15:59, Chip Scheide <[email protected]> wrote: >> >> Thanks for the list >> >>> On a related note, there are other ‘anomalies’ which MSC doesn’t >>> necessarily flag, but which are reported in the log generated by the >>> Export structure file command in v17R3. Here are the warnings or >>> errors it reported for our structure: >>> >>> 'Scrollable area compatibility mode' not supported. >>> Highlight buttons are unsupported. Please convert them to 3D buttons. >>> Picture Radio buttons are unsupported. Please convert them to 3D buttons. >>> Matrix objects are unsupported. Please convert them to shapes. >>> 3D button style is not supported. >>> >>> There are likely more, but that’s all it flagged in our structure. >>> >>> More work for me... >>> >>> Tom Benedict >>> >>>> On Sep 19, 2019, at 14:34, Tom Benedict via 4D_Tech >>>> <[email protected]> wrote: >>>> >>>> I use NotePad++ which will generate a list of all the hits which is >>>> what Miyako’s parsing script does. Miyako’s script is much easier. >>>> >>>> Tom >>>> >>>>> On Sep 19, 2019, at 14:03, Chip Scheide >>>>> <[email protected]> wrote: >>>>> >>>>> it is not that I can not search - it is that I did not know what to >>>>> search for :) >>>>> >>>>> BTW - >>>>> in most browsers Command/Control + F will open a search entry area >>>>> which will allow you to search the contents of the current web page (or >>>>> in this case log file). >>>>> >>>>> Chip >>>>> >>>>> On Thu, 19 Sep 2019 13:49:30 -0700, Tom Benedict wrote: >>>>>> Browsing the log file manually is tedious, so I use a text editor to >>>>>> look for “warning” or “error”. That’s always been enough for me >>>>>> to find any outstanding “Anomalies”. If you’ve already done that >>>>>> there must be something else which is considered an anomaly. >>>>>> >>>>>> Sorry this isn’t very useful. >>>>>> >>>>>> Tom Benedict >>>>>> >>>>>>> On Sep 19, 2019, at 13:42, Chip Scheide via 4D_Tech >>>>>>> <[email protected]> wrote: >>>>>>> >>>>>>> I moved a large system to v16, ran MSC. >>>>>>> Verify - anomalies found - 2 PICTs --removed >>>>>>> Repair - anomalies found - orphaned method --removed >>>>>>> Verify - anomalies found - I can not find it >>>>>>> >>>>>>> there is no 'warning' in the log file. >>>>>>> what should I be looking for? >>>>>>> is there a parser available? >>>>>>> >>>>>>> note: why doesn't the log file total lines of code? >>>> >>> >> ------------ >> Hell is other people >> Jean-Paul Sartre > > ------------ Hell is other people Jean-Paul Sartre ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
