Bit Che > Bugs & Feature Requests

[Old] - Bit Che 2.0 Release Candidate 4 - Build 35

<< < (43/46) > >>

Bovski:
Make them both Portable(portable=1) and put them somewhere with write access.

They don't play nice together(both running at the same time) but run fine individually.

chip!:

--- Quote from: CuF on November 10, 2012, 02:43:18 pm ---My first impression?  Inhospitable to Bit Che 1.0.

Since at the moment they use 2 different script sets, BC 2.0 shouldn't completely mess up any older installation.
I guess I assumed a non-install version meant it wouldn't drop files anywhere else.

I tried to run v1 and all my settings are gone, my passwords, my columns are a mess, etc.

It wouldn't be a bad idea to have BC2 install into a different directory and create a new settings.ini there just for itself.

Trying to get a grip on the new scripting language, but removing BC2 for now if keeping it means doing without BC1.  :-\

--- End quote ---

yes.. it is true there was no design goal to allow bc2 to run side-by-side with bc1 since that version is no longer being 'officially' supported. bc2 attempts to upgrade and use as many settings as possible to make the transition as smooth as possible.

if you prefer bc1, then you can:
 a) restore the backup of bc1 settings: 'settings.ini.bak' to continue using bc1 
 b) then run bc2 from its own directory by putting 'settings.ini' in the same dir as bit_che.exe (for bc2 you do not have to set a portable=1 flag like you do for bc1). 


bc2 adapts to your system.. you run it without install and it sets up its camp in its proper place (default).. if you include the 'settings.ini' with it, then it acts as portable. no fuss.. it just works.

design wise, i guess options would be to move from 'convivea\bit_che\'  to 'convivea\bit_che2\'  or move to 'settings2.ini' but i'm not sure that's smart.  we haven't had many people throughout the betas concerned about running them side-by-side. and going forward, we will have less and less people concerned once they have bc2 up and running.

for the new scripting language, its basically the same as before, except just the functions are now more user friendly (easier names), and variable handling is much more powerful. the goal was to be far easier to learn and less confusing than bc1..

AnthonyB:
Am using Build 27 and am often seeing in the torrent details window, in the name column "max-age=60, must-revalidateConnecti"
This seems to only be from IsoHunt.com

Bovski:

--- Quote from: AnthonyB on November 14, 2012, 09:25:08 pm ---Am using Build 27 and am often seeing in the torrent details window, in the name column "max-age=60, must-revalidateConnecti"
This seems to only be from IsoHunt.com

--- End quote ---

Have you tried the new beta ?

http://convivea.com/forums/index.php?topic=1893.msg19566#msg19566

CuF:
Thanks for the info.  Will try v2.0 again as soon as possible.

I do like the changes in the new version.  Being able to run 1.0 while transitioning scripts to 2.0 will make things easier.

Is there any sort of list of changes in the language yet?  I've noticed some short hand that confused me.  Mostly because BC2 seemed able to recognize what it was looking for without guidance from the script as long as it had the correct array.

Navigation

[0] Message Index

[#] Next page

[*] Previous page