10020. A client reported getting a broken link message when going to Facebook from their website that we created, on a phone but not a laptop, even though their Facebook page did open, and wanted us to look into it. We downloaded and installed MyPhoneExplorer, a desktop application for managing stuff on Android phones using a computer.
10042. Our OpenOffice Writer was again redlining all words, as if its dictionary was empty. This has happened about two years before and was quickly sorted out, by replacing the C:Users<username>AppDataRoamingOpenOffice4user directory with the most recent backup, after renaming it. We investigated the broken link message reported for the Facebook button on a client’s website and found why it was happening, something to do with Facebook’s new page restriction policies, not a problem with the link itself. It may not come up if you were logged into Facebook already before clicking the button on a website, probably the reason the client didn’t experience it on their laptop. The message—The link you followed may be broken, or the page may have been removed—was shown by Facebook because there were restrictions on who could see the page (by country or age) and the visitor was not yet logged in for them to be validated, or logged in but didn’t qualify. We later explained the issue to the client and showed them how to edit their page restrictions so the message didn’t show.
10112. Visited a client for briefing on a new software project. Although the client felt the new system they were considering should be part of Labelwriter, from the discussion it sounded to us like it should be a totally separate program as the output wasn’t for exam bodies at all and needed to be more flexible, with features from graphics applications like page layout and content formatting and even barcoding of numbers, sort of like a customized mailmerge tool. In the next few days we researched the feasibility of the stated requirements and submitted a proposal for implementation.
10123. Began exploring MyPhoneExplorer which has different options for connecting to an Android phone. Cable connection required we make some debugging settings in the phone (which we were not yet ready to do), while Bluetooth required that a client version of the program be installed in the phone (which we would do later).
10134. Began researching barcoding using PowerBuilder, downloading and installing ConnectCode, testing out their Encoder application and seeing it generate a barcode, then successfully registering their COM library (requiring .NET 4.x) that could be used by PowerBuilder. We researched producing PDF directly from a PowerBuilder application, and from what we saw the best bet would be using the latest 2022 version that had the option of PDF for saving datawindows, the next being using a COM library and coding the PDF output manually in the existing version that we had.
10145. We implemented Printwiser 9.11 upgrade with a new quotation schedule report generation option in the Estimating module, Show only different paper when more than one section (eg text 1, text 2) to address an issue reported by a user. We later created and emailed the client the installers.
10156. Although the page on using the ConnectCode barcode library in PowerBuilder specified a minimum PowerBuilder 12, their tutorial code (with one little adjustment) worked fine with PowerBuilder 8 that also had the OLEObject data type, and we got the tutorial application displaying a barcode. Later we researched on the feasibility of coding color separation of output.
10182. Installed MyPhoneExplorer Client in an Android phone, but after granting it the required rights, the desktop version on attempting to connect via Bluetooth said it wasn’t in range. We tested the Voice Recorder app in the phone to see if it could continue recording in the background, and found it didn’t. The following day we downloaded and tested Voice Recorder Pro and it was better than the other one, with different output formats, a pause button, and background recording; it has a price that once paid stopped ads from showing.
10230. Got MyPhoneExplorer on the desktop connecting via Bluetooth to the client running in the Android phone, downloading and viewing contacts and messages and then pondering which of the various viewing modes (sent, inbox, conversations) and file formats (csv, vmsg, html, etc) to use for saving the messages.
10263. Reviewed the file formats for sms imported by MyPhoneExplorer from the phone and saved on the computer. We settled for the csv format to be implemented for importing in our MoneyBooks Data Manager, then began the revision process for MBDM.
10296. We did the first executable build of MoneyBooks Data Manager for 2022, featuring the MyPhoneExplorer CSV option for importing SMS records. We also implemented ignoring (any accidental) show-detail commands during querying, on most frequently used list windows, like was done for MBGL in September.