Now that Sierra has been released, we can talk about the issues with FW.
The problems I have had previously, and continue with the release build are:
the file>open dialogue box just doesn’t work properly. Requires double instead of single taps on trackpad to get into folders, and when there, it is impossible to open a FW file. Has to be done from Finder.
the worst issue is that the file>import graphic dialogue box just doesn’t work at all, just corrupted text at the bottom of the box, and impossible to import anything.
I have not been able to find a workaround for 2).
I hope that a minor patch will be done by the guys to fix these issues, otherwise, I will have to continue to use FW in a El Capitan VM.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
The decline of Freeway is devastating … just one OS release after the latest FW7 release and the house of cards collapses. It clearly shows how fragile the app really is.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Guys, after experimenting for a while longer, the problem doesn’t seem to insurmountable, at least for me!
Dragging and dropping images into boxes works ok, but, the import dialogue box can also work if all sorts of additional taps/clicks are done on file names, options (e.g. Pass-through).
I have to do a combination of double clicks/taps and triple click/taps to get this working ok.
Still, there is some hope!
freewaytalk mailing list
email@hidden
Update your subscriptions at:
On 20 Sep 2016, at 23:46, Richard van Heukelum email@hidden wrote:
The decline of Freeway is devastating … just one OS release after the latest FW7 release and the house of cards collapses. It clearly shows how fragile the app really is.
I doubt that Freeway is the only application that has problems with Sierra. File dialogs are part of the system (we didn’t roll our own) and there have been problems in previous betas where file dialogs were badly implemented and caused problems for Carbon applications.
I don’t currently have Sierra on my home machine, and I’m not planning to be an early adopter - but if you do have problems I think the best thing you can do is to log bugs with Apple and post a copy of the bug report on this thread.
Freeway is in limbo until the liquidation process is completed, but I am personally hopeful that compatibility issues will be fixed, either by Apple or in a future Freeway update.
I doubt that Freeway is the only application that has problems with Sierra. File dialogs are part of the system (we didn’t roll our own) and there have been problems in previous betas where file dialogs were badly implemented and caused problems for Carbon applications.
Jeremy Hughes
Jeremy, I’m sure there may be others, but throughout the last few months, I have not encountered any similar issues with any other apps I use.
These issues have been there since day 1 of the beta phase, and I would have expected a fix to have been made by Apple by now if there were a whole load of apps with similar problems.
On 21 Sep 2016, at 13:13, Iain Mackenzie email@hidden wrote:
Jeremy, I’m sure there may be others, but throughout the last few months, I have not encountered any similar issues with any other apps I use.
These issues have been there since day 1 of the beta phase, and I would have expected a fix to have been made by Apple by now if there were a whole load of apps with similar problems.
The problems I encountered with previous betas affected Carbon apps - such as Freeway, TextWrangler, BBEdit, and PowerMail. Apple replaced the original Carbon file dialogs with Cocoa file dialogs for Carbon applications a few years ago, without apparently doing much in-house testing. Every beta throws up new problems. Unless users report these problems, Apple is unlikely to fix them.
The Graphic Import dialog had problems in El Capitan betas. It contains custom controls, which are added to the dialog using Apple APIs. Carbon applications that don’t use the same custom controls might not have the same problems. I reported these issues during the El Capitan beta phase, and they were fixed in the release version - but I haven’t been using Sierra betas, apart from some early testing shortly before Softpress folded.
If Apple doesn’t fix these problems, it is possible that we can work around them in a Freeway update. Either way, your best bet is to send bug reports to Apple and copy them here.
Jeremy, thanks for that. I didn’t have any issues with the dialogue boxes in the El Capitan beta phase at all, nor previous versions of OS X betas. I am a very early adopter in all betas, and go ‘all in’ almost immediately.
Pretty sure I filed a BR on this months ago, but I’ll check and put in another if necessary.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
But I wouldn’t bet on there being a Freeway update…
Trev
If Apple doesn’t fix these problems, it is possible that we can work around them in a Freeway update. Either way, your best bet is to send bug reports to Apple and copy them here.
On 21 Sep 2016, at 14:17, Iain Mackenzie email@hidden wrote:
How do I do that? Are BRs not confidential? Not sure.
Anyone who reports bugs to Apple’s bug system (radar) is able to view the reports that they have submitted and is also free to share them with others.
There is a web site called openradar where bug reports to Apple’s private system can be openly shared by bug reporters. Many developers use it to repost bug reports so that other developers can view them.
Apple has stated in the past that the reason its bug system is private is to protect confidential information that a developer might have shared. Anything that does not contain confidential information can be shared freely - Apple does not have copyright on bug reports that are submitted to it!
Jeremy, also, have you (or someone else Softpress related) not filed a report on this? Any new reports will just be rejected as duplicates.
Softpress folded shortly after the first Sierra betas came out - so in contrast to previous betas, we haven’t been filing bug reports.
But it doesn’t matter if a report is marked as a duplicate - Apple tracks how many duplicates there are and prioritises bugs that have lots of duplicates.
The more reports there are, the more likely it is that a bug will be fixed!
I updated to Sierra on my home Mac mainly to see what would happen to Freeway, seeing I only use Freeway on my work Mac. Freeway Pro 7.1 was the first app I tried after updating to Sierra, and when I tried launching it, I got the Internal Error shown in the following screenshot:
I clicked the Continue button and it tried to launch Freeway but the app crashed. I then took a deep breath and tried launching the app again. This time it launched with no error.
I created a new HTML 4 Transitional document, sketched an HTML box, then pressed CMD-E. I was able to see my documents and choose a JPG file just fine. It imported the pic like normal, and I was able to tick the High-resolution checkbox in the Inspector like normal.
I then tried File > Open. I could get into folders normally with double-clicks or shoot straight into folders using a single click on a desktop folder via Default Folder X.
I don’t have my big Freeway docs here at home, but I will transfer those and try to open them and see if there is any trouble. So with the except of that scary Internal Error dialog I got the first time I opened Freeway, I’ve not seen anything major under Sierra yet.
–James Wages
freewaytalk mailing list
email@hidden
Update your subscriptions at: