New: HomeBank (Sep 03, 2023), Platform 26.2.1 (Sep 17, 2023)
450+ real apps (49GB), 1.1 billion downloads, Please donate.
Jack Haller, Advisor and Father of Our Founder, Has Passed Away
So at the moment I am hard at work on 2.0 (as well as getting 1.2 out of the door) and I was wondering, does anyone actually use portable variables? If so how would you like them to change, either in implementation or how the user interface is designed?
Steve
I think portable variables have unreplecable function when synchronizing between computers which have user data located in different paths, e.g. on different drives (C: on one, D: on second).
Also, I don't work with directories of 'C:\Documet and settings\\...blabla...\My Documents\' type, but purely in ':\LuP\'; I use a named portable variable which points to ':\LuP\' when synchronizing.
I only use it for paths on 1 computer. Maybe remove the ability to add new ones within the interface, but still leave the backend code so we can manually add it to the INI.
----
Ryan McCue.
Blog.
So all that Airbus-delay trouble over here in Europe is because of YOU!
Simeon.
I would like to be able to use them, but they aren't all that reliable. The backslash doubling is a problem, but also often just a drive letter doesn't seem to want to work right. (Making P: as a variable and then doing @ExampleDrive@\PortableApps or whatever doesn't work, however entering P:\PortableApps works fine.)
@drive@?
----
Ryan McCue.
Blog.
So all that Airbus-delay trouble over here in Europe is because of YOU!
Simeon.
I have a local encrypted drive that I synchronize my USB drive to. The drive letter isn't necessarily the same on each computer. Of course I use @drive@ to reference the USB stick.
Visit the Community page
Join our forums
Follow us on BlueSky