Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Archiving files #33

Open
reesericci opened this issue Sep 27, 2021 · 5 comments
Open

Archiving files #33

reesericci opened this issue Sep 27, 2021 · 5 comments

Comments

@reesericci
Copy link

On ticalc.link, there is currently no way to archive files when transferring like in TI-Connect. Is there any way to add this?

--reese

@Timendus
Copy link
Owner

Do you mean that when transferring the file ends up on the calculator, already archived? I guess that would be a matter of setting the right property, but I'd have to figure that out and build it into ticalc-usb. And seeing that you can achieve the same result by archiving the file on the device after the transfer, it's not really a priority at the moment.

(I wrote ticalc.link and ticalc-usb because I didn't find any linking software that "just worked" and that I liked for MacOS, after about a decade of not touching TI calculators. So ironically enough, I'm really not familiar with the features of other software 🙈 Please let me know if you meant something completely different!)

@reesericci
Copy link
Author

reesericci commented Sep 30, 2021

Do you mean that when transferring the file ends up on the calculator, already archived?

yes! TI-Connect can do this, and it would be helpful to have in ticalc.link

@Timendus
Copy link
Owner

Alright, I'm sure someone reading this will be able to confirm if I'm correct in thinking that this would be a matter of setting DUSB_AID_ARCHIVED to true instead of the value of the archived attribute of the file in these lines:

{
type: v.attributes.DUSB_AID_ARCHIVED,
size: 1,
value: entry.attributes && entry.attributes.archived ? 1 : 0
},

If that's the case, it wouldn't be much work, I guess.

@reesericci
Copy link
Author

@debrouxl ^ ?

@debrouxl
Copy link
Collaborator

Yup. Simply add a mode where you force entry.attributes.archived to true before passing said entry to the variable sending code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants