pimhwang/qTox - qTox - git.quantfans.net

Commit Graph

Author	SHA1	Message	Date
Ansa89	046376bed6	Italian translation: update	10 years ago
tux3	66cb02d1c3	Fix qTox Android build	10 years ago
tux3	44c6b42c56	New OS X dock icon from #1541 Thanks to @pwnsdx	10 years ago
tux3	25329d3a57	Remove redundant QString ctor Thanks to @Papierkorb	10 years ago
tux3	92f14cc6eb	Create config directory on first run Fixes #1540	10 years ago
tux3	f0c01a4f64	Fix typo in error message Thanks to @Selena-Gomez for finding this.	10 years ago
tux3	2fed6724b2	Merge of the new API compatible qTox branch Merge branch 'back_in_the_game'	10 years ago
tux3	542cae85d3	Give appropriately scary name to dangerous function "isPathWritable" didn't convey really well the meaning of "let's try to open it, wipe everything the hell out, and see if it worked"	10 years ago
tux3	8786f9525e	Fix #1536 New friends must be added to the friend list before loading history, otherwise the history code won't find the friend in the friendlist, and the history will have blank names for the friend	10 years ago
tux3	936f055893	Merge branch 'pr1535' into back_in_the_game	10 years ago
agilob	a31b33106a	added missing lib for ubuntu	10 years ago
tux3	200af0fd49	Better error messages for friend requests	10 years ago
tux3	d962148dd0	Fix more save corruption bugs askProfiles is a really dangerous function. Awful things happen when the user closes that message box. We now prevent it from being closed in more places	10 years ago
tux3	7eb9370c0b	Disable the GUI until a profile is active There are small instants on startup and while profile switching during which no profile is loaded but the GUI could still receive events, e.g. between two modal windows. Disable the GUI to prevent that.	10 years ago
tux3	e682dada3b	Fix save corruption bug Don't just let the user close the profile select box and continue with an empty value. We would create a new profile and save it back on top of the previous encrypted profile	10 years ago
tux3	e74e29e4fb	Cleanly cancel broken file transfers	10 years ago
tux3	cdb2bad7c3	Signal broken file transfers	10 years ago
tux3	c6e60c4c77	Remove some CoreFile debug output	10 years ago
tux3	bd5eebbc2e	Cache avatar sending, fix image file preview - Add AvatarBroadcaster, in charge of making sure our friends have our avatar without spamming file transfers - Fix file sending code not closing the file after transfer, which prevented file previews, and make the QFile a shared_ptr to fix the obvious memory leak Some small additions to Core to support AvatarBroadcaster	10 years ago
tux3	9ece486e22	Prevent possible uninitialized read of status For unhandled values of Status, we want to return, not continue with an uninitialized value.	10 years ago
tux3	0e65d150e3	Don't show call buttons in text-only groupchats I'm not sure why there are text-only groupchats in the first place, but that's fixed.	10 years ago
tux3	9d3d17d05e	Avatar sending on top of file transfers	10 years ago
tux3	cdf3d9f553	Change some tabs to space for consistency	10 years ago
tux3	8b6ef7ab9d	Merge branch 'pr1524' into back_in_the_game Conflicts: src/widget/form/groupchatform.cpp	10 years ago
tux3	f76434f94f	Merge branch 'pr1522' into back_in_the_game	10 years ago
tux3	43279368f3	Cherry-pick `da084594d9` from #1523 Closes #1523	10 years ago
AxP	7b3baa8932	German translation updated.	10 years ago
tux3	c3c370d118	Cherry-pick `da084594d9` from #1523 Closes #1523	10 years ago
AxP	29ea557269	German translation updated.	10 years ago
kushagra	0a7c82c2cf	Right clicking anywhere wont unhighlight text, fixes #1517	10 years ago
tux3	1c51cd788b	Merge branch 'pr1509' into back_in_the_game	10 years ago
tux3	b70bc008a0	Merge branch 'pr1503' into back_in_the_game	10 years ago
tux3	f8eb90f74d	Merge branch 'pr1498' into back_in_the_game	10 years ago
tux3	2954ee3c95	Merge branch 'pr1496' into back_in_the_game	10 years ago
kushagra	b4f72b620d	fixes action bugs 1) action received gets modified on restart 2) sender's name is written twice if action is sent using offline messaging 3) /me is written when action is sent in groupchat having one peer 4) /me is not saved in last message variable in friendd chat	10 years ago
tux3	2d29c3d9f4	Merge branch 'pr1493' into back_in_the_game	10 years ago
Rohil Surana	a677e34ca4	Removed corner border in scroll area	10 years ago
tux3	262fc7059d	Merge branch 'pr1487' into back_in_the_game	10 years ago
tux3	110a6ca850	Fix typos in tooltips transmit -> tranfer	10 years ago
PKEv	137d1ae2d5	Add tooltip in filetransferwidget It is not clear what they are doing buttons	10 years ago
tux3	96e0f0d502	Merge branch 'pr1477' into back_in_the_game	10 years ago
Yuri	11883bab85	Added Ctrl+Q shortcut.	10 years ago
tux3	5662120c51	Show Tox ID instead of blank names	10 years ago
tux3	42d7a7bcef	Assert profile locks before writing This fixes the potential edge case where a frozen then unfrozen qTox instance could have its locks delete by a new qTox instance. We now check that we still own our locks, restoring them if we can, before saving	10 years ago
tux3	694933d24b	Correctly rename and lock imported profiles Imported profiles are legact 'data' and 'tox_save' files	10 years ago
tux3	dc5f812946	Merge branch 'bitg_multiple_instances' into back_in_the_game	10 years ago
tux3	05b6f1985d	Allow to start multiple instances with -p Starting a new instance with the -p option will force it to start a new instance with the given profile instead of bringing an eventual existing instance to the foreground Two instances can not run with the same profiles, the profile locking code will ensure that. A user who likes to live dangerously could manually delete the lock to force two instances on the same profile, but such an hypothetical user would be asking for it. If a qTox instance starts and becomes owner of the IPC shared memory on its first try, it considers itself the only running freshly-started instance, and deletes any possibly stale lock before starting up. This should be fine in the vast majority of cases, but if an existing qTox instance freezes for a long enough time to lose ownership of the IPC and a new instance is started without first killing the frozen one, the frozen instance's lock will be deleted as stale by the new one. If the frozen instance subsequentely unfreezes, it will be running on a profile for which it doesn't have a lock, which could cause trouble. This is an intentionaly allowed edge case, the alternative being a stale lock staying forever until removed manually. A potential solution not yet implemented would be to check that the lock is still actually present before attempting any write.	10 years ago
tux3	0baba7abe2	qtox.ini shouldn't overwrite our current profile If we're running on a given profile, reload the qtox.ini, and it has a diffeent value for the current profile, we don't overwrite our current value with whatever qtox.ini says anymore It would cause current profile confusions when multiple qTox instances where using different instances but sharing the qtox.ini	10 years ago
tux3	ea417d3688	Update lock when renaming profile	10 years ago
tux3	73bd5a656f	Fix possible profile corruption When loading an encrypted profile, not entering the password and switching directly to a plaintext profile could have overwritten the plaintext profile with the encrypted one	10 years ago

1 2 3 4 5 ...

2718 Commits (046376bed67b1bb5f9f50b945f3b9088551e1a89) All Branches Search

2718 Commits (046376bed67b1bb5f9f50b945f3b9088551e1a89)

All Branches