New file upload types supported: .qsch & .qsym

I am pleased to announce that the forum now supports uploads of .qsch and .qsym files.

6 Likes

Excellent! Thanks, Jeff.

–robert

1 Like

Jeff,

Thank you.

I realize that you’re probably hesitant to add “.zip” files to the list of allowed uploads.

The advantage is that the archive format would allow multiple filetypes to be combined. I’ve uploaded a couple of .zip archives ( with the file extension .txt) to this forum to allow for a C-block file structure to be keep intact. These include the .cpp, .dll, .qsym (a symbol maintaining the hierarchical information) and a .qsch (to use as a demo/test example).

You’ve written earlier about possible support for a download area of user IP. Maybe this would be a reasonable alternative.

Len

Great, thanks! But now I’m somewhat conflicted. :smirk:

On one hand, attached *.qsch and *.qsym can be downloaded conveniently but not be dragged or pasted into QSPICE directly (and there is no preview of the content in the forum, like for images, or SVG, if configured). US Windows 95 encoding.

On the other hand, post content marked as code (image) can be copied (image on top right) and pasted directly into QSPICE (but in the forum the code is missing correct highlighting). UTF-8 encoding.


qspice-icon.qsym (1.0 KB)

«symbol qspice-icon
  «line (48,-20) (48,17) +30 0 0x0 -1 -1»
  «line (-58,17) (-58,7) +30 0 0x0 -1 -1»
  «line (-5,-46) (2,-46) +30 0 0x0 -1 -1»
  «rect (-130,130) (130,-130) 0 +01 0 0xffffff 0xffffff -1 0 -1»
  «ellipse (-160,160) (160,-160) 0 +80 0 0xe0a000 0x1000000 -1 -1»
  «arc3p (120,0) (-200,0) (-40,0) +01 0 0x0 -1 -1»
  «arc3p (-120,0) (200,0) (40,0) +01 0 0x0 -1 -1»
  «arc3p (60,-104) (-100,173) (-20,35) +01 1 0x0 -1 -1»
  «arc3p (-60,104) (100,-173) (20,-35) +01 1 0x0 -1 -1»
  «arc3p (-60,-104) (100,173) (20,35) +01 2 0x0 -1 -1»
  «arc3p (60,104) (-100,-173) (-20,-35) +01 2 0x0 -1 -1»
  «arc3p (120,0) (-120,0) (0,0) +01 0 0xe0a000 -1 -1»
  «arc3p (-120,0) (120,0) (0,0) +01 0 0xe0a000 -1 -1»
  «arc3p (200,0) (-200,0) (0,0) +01 0 0xe0a000 -1 -1»
  «arc3p (-200,0) (200,0) (0,0) +01 0 0xe0a000 -1 -1»
  «arc3p (48,-21) (48,-20) (-5,-20) +30 0 0x0 -1 -1»
  «arc3p (48,17) (-58,17) (-5,17) +30 0 0x0 -1 -1»
  «arc3p (-58,7) (-5,-46) (-5,7) +30 0 0x0 -1 -1»
  «arc3p (48,-73) (2,-46) (2,-99) +30 0 0x0 -1 -1»
»

We’re moving in the right direction here. You do have to download the file before you can drag-and-drop it into QSPICE, but that’s easy enough from the Downloads folder. Still, reducing that friction would be nice, so I’ll keep that on our list.

Regarding your comment about formatted in-line code, do you mean that QSPICE code doesn’t get proper formatting the way C++ does?

Hi Len,

I like the idea. I suspect our IT security folks, who are justifiably paranoid, probably won’t like it as much.

Hosting .dll files directly seems rife with security concerns, too, but since it’s quick to compile. cpp directly in QSPICE, this may not be too big of an issue.

I think I’ve seen Github mentioned as a possible third-party solution. Does anyone else have a suggestion?

Since «symbol above isn’t configured to be recognized as a “magic number”, it would just select one of the other configured programming languages (maybe Python, JavaScript, C, etc.) and highlight not all the correct parts (unless it’s turned off explicitly using ```qsym [because it’s not configured], ```txt or ```text).

I didn’t like Microsoft’s 2FA enforcement on GitHub. I’m using GitLab for repositories but not sure if that’s the right thing here. Obviously, groups.io/g/qspice could help to avoid some IT folks issues (and is pretty responsive).