Bit Che > Bit Che - Info & Updates

OLD: Bit Che 2.0 - Latest Version -- Build 60 (April 11, 2013)

<< < (7/29) > >>

chip!:

--- Quote from: depmodey on October 25, 2012, 12:18:35 am ---First of all, a big thanks for your GREAT work.

I wanted to inform you about two problems in the newer BitChe 2.0 Beta (maybe you already know):

1) A lot of times, activating a row of a searched torrent ("double click" or "right click + open torrent") causes BitChe to close to Desktop without any warning (tested on Win7 and Win8 [both with 64bit] on two different machines). Sometimes you need to start BitChe 3/4 times and try to open the desidered torrent before being able to add it to your torrent software (if can help, I'm using uTorrent 1.8.5, really old, but seems a lot faster than any version after 2.0). Since uTorrent isn't actived in any case, I don't think (but not sure) that the problem is connected with the torrent 'cacher' software. It never happens with previous version of BitChe (1.0)

2) Installing BitChe 1.0, after having installed BitChe 2.0, causes the tab columns to mess up (really small width): as you can view from the linked image (tested on WinXP, Win7 and Win8)


--- End quote ---

Thanks!

1.  I assume you are testing the latest 2.0 build 24?  I am curious if you tried any of the previous builds and if those builds had the same problem?  Lastly, have you made any modifications to Bit Che 2.0 or used a cracked version of 1.0?  And, while you're at it, maybe try turning off your anti-virus program (what is it?)?   I develop on Win7 64bit English and have not had those problems without it being related to modifications/cracks or anti-virus. But it could be something new. What language is your OS?

2. Sounds like a bug with 1.0 loading the 'settings.ini' which gets upgraded to 2.0 format when its ran. Unfortunately, 1.0 is no longer supported so I cant fix that "downgrade" issue with 1.0, but you can fix it by deleting 'settings.ini' and restarting Bit Che 1.0.  Otherwise, you can create another directory for 2.0 and copy 'settings.ini' to it, and run 2.0 and 1.0 sidebyside...  but keep in mind, there likely arent going to be 'official' script updates for 1.0 since my main efforts are getting 2.0 finalized and out the door :).

Bovski:

--- Quote from: chip! on October 24, 2012, 06:49:47 am ---
--- Quote from: Bovski on October 23, 2012, 06:08:34 pm ---So where do I put my scripts to stop it deleting them.
I have had to download my scripts from here a couple of times at present this is a big flaw.

--- End quote ---

well, concept is that the 'default' script pack is a protected and fully synced.  i think that is best for the majority of the users.  that way we are not combing 'default' script pack with other scripts and then having some out dated, old, not synced, deleted.. etc.

for developers, and for testing.. put any scripts in a new script pack/directory. 
a. create new directory in /scripts/<name> 
b. create a new 'bcs.<name>.ini' file

you can copy /scripts/default over to /scripts/<name> and edit or test those. they remain untouched when updating 'default' script pack

then, you can toggle which 'script pack' you are using ('default' or '<name>' in the Bit Che GUI using the menu or the button under the Script List.

idea is that if you have fixed script, then it should get sent to the GitHub so that the /script/default/ is auto updated on any user who has that option selected.  note, you can turn off 'auto update default script pack' in the Preferences.

also, relevant, lets say the user wants another script pack..  such as 'anime'.  anyone can create and maintain a 'anime' script pack and the pack can have its own update check and can keep that fully in synced too.

open to suggestions on this :)


--- End quote ---

This is just way to complicated why do I need to create a bcs.<name>.ini file cant Bitche tell there is a new folder present.

Why am I limited to selecting either the Default script pack or the new one why can't I select both.

If I select my new script pack and want to go back to the default pack I get an error Feature Disabled in Freeware Edition(though not if I register Bit Che) shouldn't this just lock onto the default pack?
It also took me to an error 404 page http://www.convivea.com/bc_plus.php

Perhaps scripts should have versions in them as some only work some versions of 2.0 beta.

depmodey:

--- Quote from: chip! on October 25, 2012, 05:38:57 am ---
--- Quote from: depmodey on October 25, 2012, 12:18:35 am ---First of all, a big thanks for your GREAT work.

I wanted to inform you about two problems in the newer BitChe 2.0 Beta (maybe you already know):

1) A lot of times, activating a row of a searched torrent ("double click" or "right click + open torrent") causes BitChe to close to Desktop without any warning (tested on Win7 and Win8 [both with 64bit] on two different machines). Sometimes you need to start BitChe 3/4 times and try to open the desidered torrent before being able to add it to your torrent software (if can help, I'm using uTorrent 1.8.5, really old, but seems a lot faster than any version after 2.0). Since uTorrent isn't actived in any case, I don't think (but not sure) that the problem is connected with the torrent 'cacher' software. It never happens with previous version of BitChe (1.0)

2) Installing BitChe 1.0, after having installed BitChe 2.0, causes the tab columns to mess up (really small width): as you can view from the linked image (tested on WinXP, Win7 and Win8)


--- End quote ---

Thanks!

1.  I assume you are testing the latest 2.0 build 24?  I am curious if you tried any of the previous builds and if those builds had the same problem?  Lastly, have you made any modifications to Bit Che 2.0 or used a cracked version of 1.0?  And, while you're at it, maybe try turning off your anti-virus program (what is it?)?   I develop on Win7 64bit English and have not had those problems without it being related to modifications/cracks or anti-virus. But it could be something new. What language is your OS?

2. Sounds like a bug with 1.0 loading the 'settings.ini' which gets upgraded to 2.0 format when its ran. Unfortunately, 1.0 is no longer supported so I cant fix that "downgrade" issue with 1.0, but you can fix it by deleting 'settings.ini' and restarting Bit Che 1.0.  Otherwise, you can create another directory for 2.0 and copy 'settings.ini' to it, and run 2.0 and 1.0 sidebyside...  but keep in mind, there likely arent going to be 'official' script updates for 1.0 since my main efforts are getting 2.0 finalized and out the door :).

--- End quote ---

1) I'm using the latest build (24), without any changes or cracks. My antivirus is actually Norton Antivirus 2013 (retail [not cracked] version), but I had the same problem with the 2012 retail version. I had the same problem even with previous builds of the new 2.0 BitChe. I'm using Italian O.S. I will experiment and let you know

2) It's not really a problem, since you could rearrange columns width: it is just a bit strange and weird

Thanks for the quick answer.

chip!:

--- Quote from: Bovski on October 25, 2012, 06:28:54 am ---This is just way to complicated why do I need to create a bcs.<name>.ini file cant Bitche tell there is a new folder present.

Why am I limited to selecting either the Default script pack or the new one why can't I select both.

If I select my new script pack and want to go back to the default pack I get an error Feature Disabled in Freeware Edition(though not if I register Bit Che) shouldn't this just lock onto the default pack?
It also took me to an error 404 page http://www.convivea.com/bc_plus.php

Perhaps scripts should have versions in them as some only work some versions of 2.0 beta.

--- End quote ---

a. bcs.name.ini file holds the Script Pack update URL and the CRC hash for the package, so each 'pack' can be synced. I can have Bit Che auto-create this file if a new /name containing scripts is detected, but point is, if someone wants to create their own 'script pack' and distribute a single .zip  then it would contain the bcs.name.ini and a /name folder  that holds the scripts. the single.zip file would be extracted to /script dir.

b. good idea to allow multiple packs to be selected. ill have to play with the design. i was trying to keep things simple with separate 'script packs'. but I can see that users might want only 1-2 additional scripts from another pack and also include them while searching with the 'default' pack.

c. i've decided to make 'script packs' standard feature so I will remove the plus/freeware check here.   and fix the 404 page.

d. there is currently a check and will ignore scripts that dont have 'version=2' in them.

thanks!

Bovski:

--- Quote from: chip! on October 25, 2012, 08:55:26 am ---d. there is currently a check and will ignore scripts that dont have 'version=2' in them.

--- End quote ---

Yes but there are different versions of 2 the tpb script I did will only work on 2.0 Beta 16 - 2.0 Beta 24 when 2.0B25 is released it will need updating.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version