User Portlet
| Discussions |
|---|
| Hi David, I often use this exact same approach. But it's a bit of a pain having to include the cell in pretty much each and every NB. So this discussion got me thinking about whether there's a more convenient solution. What I've come up with is... |
| Hi Connor, Thanks for highlighting these additional resources - very helpful. Would there be any chance of a Daily Study Group series to cover the various aspects of Paclet development and distribution? All the best, Ian |
| Hi David, Thanks for your comments. As mentioned previously, I’m pretty sure the issue I’m seeing is a bug introduced in V13. All the best, Ian |
| My experience is that Mathematica's DXF import and export functionality is very limited. It doesn't appear to be anywhere near comprehensive and doesn't seem to work for many CAD objects/entities. Unless you're working with quite basic primitives... |
| Thanks Jason, The PacletDirectoryLoad function look to do exactly what I want. I hadn't noticed it in the documentation. I'll give it a try tomorrow. Very much appreciated, Ian |
| Hi Lissa, Thanks for the suggestion. Much appreciated. All the best, Ian |
| I'm running into a problem trying to use the SetOptions function to customise the default values of optional arguments for several built-in functions. The problem I'm experiencing is that overriding the default values of some optional arguments for... |
| Reducing $HistoryLength may help. Especially for large notebooks implementing memory hungry computations. I think that by default its value is infinity and all input and output is stored in memory. |
| This might be veering off the main subject, but referring back to David Park’s suggestion that units could be introduced at the end of an evaluation sequence, I think this has some merit. I’ve found that using units can slow down evaluation speeds... |
| Try... AirTemperatureData["LESA", {DateObject[{2020, 1, 1}], DateObject[{2020, 2, 1}]}, Mean] |