DesignCAD User Forum

General DesignCAD Topics => Looking For Help? => Topic started by: Latheman on June 18, 2017, 12:06:48 PM

Title: Oddity re Arial font.
Post by: Latheman on June 18, 2017, 12:06:48 PM
Hi folks,
I have two computers, Main & Backup. Both are as near identical as I can make them although as Main is a Celeron M CPU 520 @1.6GHz and Backup is a Pentium Dual T2380 @ 1.8Ghz they cannot be identical. Both have DC17.2 and DC2K on them. Both are running Linux Mint 18.1 so the Design Cad programs are running via Wine.

The problem:
DC17 on Main will not switch to Arial font. DC17 on Backup, and DC2K on both will switch and stay on Arial. DC17 on Main always drops back to Arial Black if Arial is selected.

In order to get a reasonable font on Main, I'm having to use one called Verdana which is probably a specific Linux font, but it's the nearest I've got to Arial, which I do quite like for my drawings.

I have reloaded all the associated Linux programs, and the Design Cad programs. I've even gone as far as copying the default workspace files etc from Backup to Main along with DC_Layer.ini and DC_FilePath.ini (which were different). All to no avail.

All in all it is either something in Linux Mint which only happens on Main computer, or it is something in DC17 that doesn't work properly either with Linux Mint or Main computer.

Anyone got any ideas before I risk the wrath of the Linux fanboys who take great exception to anyone sullying Linux with anything to do with Microsoft.



Title: Re: Oddity re Arial font.
Post by: Dr PR on June 18, 2017, 12:55:22 PM
Do you actually have the Arial font installed on your main machine? Can you use it with any other program running under Wine?

Title: Re: Oddity re Arial font.
Post by: Latheman on June 18, 2017, 01:04:24 PM
The only other program I use under Wine is DC2K, and Arial works with that. As far as I can tell. although a quick test just now did seem a bit odd. But it did retain Arial eventually.

Now there's a thing. I've deliberately created a small file in DC2K using Arial font. Saved it, reopened and it still says (Ctrl I) Arial. Close it, and reopen with DC17 & it says Arial Black. Further testing shows that DC17 has indeed changed it to Arial Black.


Title: SOLVED: Re: Oddity re Arial font.
Post by: Latheman on June 19, 2017, 04:40:37 AM
It looks like I have found the problem.

Originally on both machines I was using what is called the staging branch of Wine, v.2.4.0 which is, as I understand it, the latest *** version of Wine to be produced. Recently I updated the Main computer to staging branch v.2.10.0 whilst leaving Backup at 2.4.0. Reverting Main to the latest stable branch of Wine, v.2.0.1 and the problem has disappeared. This would suggest something wrong with staging branch 2.10.0.

I've looked at reporting it as a bug in Wine, but the procedure appears rather complex requiring explanations and downloads, I've decided not to bother. After all, the next version of Wine might correct it. In any case, since DC works reasonably well with Wine v.2.0.1, I'm happy for now.


*** That's not quite true, but near enough. The way Wine, and other Linux programs work is that they have so-called stable and unstable versions. The stable versions are, if you like, a reasonably secure system as far as it goes. This doesn't mean that it is perfect, just reasonable for a lot of users. The unstable versions are later versions which are still in development, and Wine actually appears to have even split that into staging and development. No, I don't know what it means.

For me, I've had various problems with using Design Cad under Linux and hence having to use Wine as an intermediatory program between DC and Linux. Starting with Wine v.1.4, DC was a no-no, v.1.6 allowed DC2K to work ok, but not so DC17. Later, I accidently loaded staging branch v.2.2 and found that DC17 was now working ok. At that time the stable version was 1.7 or 1.8 and I didn't feel inclined to revert to one of those. The staging branch was automatically upgraded to v 2.3 and then to 2.4 and DC still continued to work so I wasn't particularly bothered. However, the upgrade to v2.10 broke it as described above.