dim f as folderitem
//check for nil etc.
Now, how to deal with f.launch (for all platforms) when using Xojo.IO.Folderitem?
Does it mean that we have to keep the classic and the new folderitems existing side by side?
I hope I’m missing something.
The Launch method seems to be missing.
Xojo.IOS.FolderItem was originally created for iOS, where it is simply impossible to launch any process (no Shell either there). So it was missing for a reason.
Now, looks like a feature request is in order for the other platforms that support it.
I guess I am stupid but xojo.io.folderitem is not able to stay alive very long. In contrary to the classic framework folderitem the new io.folderitem goes out of scope, even you keep a reference.
I don’t get that. Can someone prove ?
enclosed sample project demonstrates the issue. I have no clue what I am doing wrong. If the coding is
wrong please correct me.
Weeeelllll now that’s interesting. If I try to view the celltag in the IDE the debug app will crash.
It might have to do with how you’re mixing the frameworks, trying to store a Xojo.IO.FolderItem as a variant.
For now, a decent workaround is to store the path as the celltag and create the folderitem when you need it.
Yes, it will crash in IDE.
In my current app I do this workaround already with the path as Text. That’s the only way.
I haven’t figured out yet how to store a reference of a xojo.io.folderitem. Weakref won’t work too. Using a variant doesn’t work either.
Once reading out the value it goes out of scope (=nil).
Definitely file a Feedback report on this.
Yep, I’ll do. Feedback was broken too for a few hours.
#edit: feedback submitted.