![]() Make internal interface similar to VCL and replace VCL with it in existing source codes (to avoid redesigning logic and breaking anything, some tweaks will be applied though). The way to go is redesigning application structure to be able easily change firemonkey UI units to VCL UI units, so it should be some kind of internal interface which connects program logic to the selected widgets and compile for both platforms with single logic sources, but different UI sources. Actually as far as I know for MacOS Delphi uses some kind of virtual machine to look like native. Reality is a bit different: Windows support is made with VCL and MacOS with Firemonkey, you can compile Firemonkey for Windows too, but that is not good way to go for Windows. Especially when you can do it with (comparatively) little effort. Combine that with the fact that Eagle has gone subscription based and you’d be stupid *not* to provide your EDA tool on those platforms. Based on the latest numbers I’ve seen, the Windows 10 adoption rate is pretty dismal while macOS and Linux are growing faster than ever. So I don’t see how it would make the Windows version of DipTrace “slower and more complex” as you seem to think. It can produce binaries (using native UI widgets) for Windows, macOS, iOS, Android, etc. That’s the beauty of the tool they’re using. ![]() Aside from a bit of simple code they’d need to add, there’s really nothing else they’d need to do. The UI and system libraries are already obfuscated behind higher level calls, so it’s not like they’d have to implement those things separately for each platform. (Assuming you don’t install a second graphics card and pass it through to the VM like you can with Virtual Box and some versions of VMWare this method also has certain issues and limitations.) At any rate, once they’ve “reorganized” their code, it’s a simple matter of telling the compiler to produce a native Mac binary. Since the guest OS doesn’t have direct access to the GPU, like it does with the CPU, 3D performance is significantly limited. That’s simply to boot into the guest OS! Then there’s the matter of 3D acceleration, which all modern EDA software requires, including DipTrace. Virtual Machines are also large and consume a ton of system resources. Also some smaller features like BOM in PCB Layout, tear-drops, etc. Overall improvements of routing usability and bus routing. You will not get power of PADs or other high-end EDAs in the first versions, but this is what we want to reach for this feature. Interactive push and shove router and trace editor. Additional fields in Pick and Place, tab divider in text files for BOM and Pick and Place. Rotate Group and Flip Group commands in Component and Pattern Editors. Always open/soldered option in custom mask/paste settings for pads and vias. Storing common solder mask swell and paste mask shrink with the project file. Polishing of length matching and meander features. Improved highlight and selection of objects in PCB Layout (traces and all other objects under footprints are highlighted and can be edited in default mode). ![]() DRC same net clearance check (Trace to Trace, SMD to Pad, SMD to Via, SMD to SMD). However some new tricks have been added too: 1. I'll keep you informed.Just posted on the forum from DT Team: We have published new version 3.2 today, the major thing we changed in it is polishing of existing features (added in 3.0 and 3.1). We will be happy to solve this, but don't know how at the moment.Īnyway we will keep current settings yet (I suppose allowing access to all PC users for just new DipTrace folders is not critical) and our programmers together with sys admin now trying different configurations - probably we will find why it doesn't work on some 圆4 systems and make something intermediate, then publish update after DesignCon. Now it only creates new DipTrace folders with "all allowed" security settings. Enabled incorrectly and it changed security for "My Documents" folder. Same results both times.Īctually that was the reason why we enabled that option in the past. Tried installing from the administrator login and also from the standard user login, entering the administrator password to allow the installation. You may not have appropriate permissions to access the item." and then terminates. "Windows cannot access the specified device, path, or file. Standard user, attempting to start the launcher or any other Diptrace program throws an error: ![]() The users write though:Ĭlean install of Diptrace 2.3.0.2 (64bit). On our PCs all versions work ok with any security settings under any account. The problem is not actually software, but something in Windows 64-bit security settings, installer and specific computer settings.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |