Bit Che > Bit Che - Info & Updates

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

<< < (6/29) > >>

Bovski:
Feature request the ability to drag attached ini files from the board onto Bit Che to add the script.

people still don't get folders and the like see http://convivea.com/forums/index.php?topic=1800.msg19200#msg19200

Sort of like this
http://www.youtube.com/watch?v=emNogwGMJJM

Eat your heart out George Lucas not even he could do a video that would allow V1.6 script to be dropped into V2.0 Beta but you get the Idea. Some validation would be needed.

P.S.
OLE doesn't work in the IDE on Windows 7

chip!:

--- Quote from: Bovski on October 19, 2012, 03:26:24 am ---Feature request the ability to drag attached ini files from the board onto Bit Che to add the script.
P.S.
OLE doesn't work in the IDE on Windows 7

--- End quote ---

dang, that will make it tough(er) for me to test, but I can load it up in a WinXP VM.

but, IMO, I think its better we focus on the GitHub scripts so that the community can push changes and the default pack will be synchronized automatically.

Right now, Bit Che 2.0 will delete scripts that are not in the 'default pack' when you 'update', so if users drag and drop new scripts, then the 'default pack' is updated, they will lose any changes.  Reason is, 99.9% of the people dont want to mess with the scripts, so I've made extra effort to keep things 'synced' for 2.0.  And then, developers can create a 2nd 'Developer' script pack where those scripts are kept in a tidy 2nd folder.

Bovski:
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.

chip!:

--- 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 :)

depmodey:
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)

Navigation

[0] Message Index

[#] Next page

[*] Previous page