DesignSpark PCB: fonts?
提出问题
与社区会员和专家互动来寻找解决办法及答案.
搜索问题及答案
按主题查看问题
按关键字查看问题
- ETHERNET
- Embedded
- Platform
- power
- PoE
- Cisco
- 802.3af
- designspark
- systems
- design
- blog
- user
- profile
- photo
- events
- trade shows
- meet up
- bank holiday
- weekend
- marching
- band
- rain
- competition
- 3D
- Intel
- processor
- I5
- I7
- photography
- football
- world cup
- europe
- pcb
- schematic
- DesignSpark PCB
- Operating System
- OS
- Windows
- Linux
- libraries
- mounting holes
- pads
- components
- DesignSpark PCB. pcb
- pcb layout
- pcb.pcb layout
- autorouter
- Protel99
- 随机存取
- Random Access
- 隨机儲存
- IEEE 1588
- fiber channel
- 光纖通道
- 光纤通道
- Infiniband
- Profinet
- Profibus
- Library
- 激活
- 组件
- Win2000
- Win2K
- 博客
- 合作伙伴
- 注册
- 分享
- 窍门
- 全局,修改,参数
- DXF
- 创客空间
- 批量操作
Bright spark
相关问题
2012 5月 22
2012 4月 18
2012 4月 13
2012 4月 13
2012 4月 7
订阅问题及答案
接收来自地区活动,内容.分类和联繫人活动的通知.

daveegg
Go Shift T, on the Design Technology dialogue select Text Styles; for Symbol Names, Pin Numbers, etc. You can then select any Windows fonts you have installed. If these fonts are going to be your standard then go File / Save Technology and then when you start a new design you have all your fonts plus anything else you have set all ready to use.
nigelmercier
Trying again ...
I thought I had done that. Is it possible that the two components use different DT files? If so, how do I change them?
Futher to this, I've found that I keep getting new styles, such as Normal_1 and they are "in use" so I can't get rid of them.
nigelmercier
Any thoughts on this anyone?
nigelmercier
Hello? Anyone there?
I've since been playing, and I've discovered a possible bug. Despite changing the Text Style in the component to the correct style, when I view the schematic and change the bogus styles to a large font, it seems the component is still using the bogus style.
I've tried all combinations of deleting the styles from the component, and saving the Technology file.
I'm tearing my hair out here, please can someone from the DesignSpart Team look into this for me?
nigelmercier
The only way I have found to fix this is to delete the component then insert it again. Looks like a bug in the Update Components section to me ...