AlanQuatermain/AQGridView 2406
A grid view for iPhone/iPad, designed to look similar to NSCollectionView.
evadne/DayFlow 231
iOS Date Picker + Infinite Scrolling
evadne/angular-chosen-playground 4
Chosen + AngularJS + Typeahead + Auto-Suggestion with good search performance on 10,000 items
Core Data Persistence with AFNetworking, Done Right
DAKeyboardControl allows you to easily add keyboard awareness and scrolling dismissal (a receding keyboard ala iMessages app) to any UIView, UIScrollView or UITableView with only 1 line of code. DAKeyboardControl automatically extends UIView and provides a block callback with the keyboard's current origin.
Browse the web from the comfort of your UINavigationController.
Crypto Support for Cappuccino
evadne/CPTableview-customDataView-selectionTest 2
CPTableview custom data view -setSelected:animated: experiment
7 Languages in 7 Weeks…
A library of easing functions for C, C++ and Objective-C
issue openedmozilla/pdf.js
`TypeError: can't access property Symbol(), match is null` error when loading XFA PDF
Attach (recommended) or Link to PDF file here: PDF from #4106, https://mail.gnome.org/archives/evince-list/2013-November/pdfNC0hkVW67a.pdf.
Steps to reproduce the problem:
- Open the PDF
What is the expected behavior?
What went wrong?
The PDF doesn't load, TypeError: can't access property Symbol(), match is null error is logged in the console.
created time in a few seconds
pull request commentmozilla/pdf.js
XFA - Value in field can be html
OK, when you do, please make a link with this PR.
comment created time in 10 minutes
issue commentcyring/CoreFreq
Terminal transparency in corefreq-cli
Thanks to your tips, I'm adding the new branch develop-ui-transparency in which you can push your PR.
Like you, using urxvt -tr with Awesome DE, UI menus are fully blank except the dimmed braces
These are among of the impacts I hope we will solve with just some color choices.
It's clear now that it's more appropriate to provide a second resources theme dedicated to transparency. I'm preparing this for next commit.
comment created time in 16 minutes
pull request commentmozilla/pdf.js
XFA - Value in field can be html
In a separate one.
comment created time in 20 minutes
push eventmixxxdj/mixxx
commit sha 876db3ef1dd86c64794f7b57c6a5cec64533c494
Skins, waveforms: remove I-beam from in/outro marker to equalize marker size
commit sha 977eca1d04cbe15c7d6e9ce7716b3052c44736a7
Skins, waveforms: position in/outro markers inside the range
commit sha 8e6b3a80d683d8b29bbfe9fc23709d1f74ee7cd2
Merge pull request #3989 from ronso0/waveform-introoutro-markers Skins, waveforms: remove I-beam from in/outro markers to equalize marker size
commit sha 7c7d406c6c0e27e72b382f6420d6ef9f231ae9cf
Merge branch '2.3' of [email protected]:mixxxdj/mixxx.git
push time in 25 minutes
Pull request review commentmixxxdj/mixxx
Add support for editing ReplayGain values.
mixxx::ReplayGain Track::getReplayGain() const { return m_record.getMetadata().getTrackInfo().getReplayGain(); } +bool Track::setReplayGainDb(double ratio) {+ QMutexLocker lock(&m_qMutex);+ mixxx::ReplayGain replayGain = *m_record.refMetadata().refTrackInfo().ptrReplayGain();
mixxx::ReplayGain replayGain = m_record.getMetadata().getTrackInfo().getReplayGain();
comment created time in 26 minutes
issue commentValveSoftware/Proton
[Whitelist] Deus Ex: Game of the Year edition. (6910)
I tried the original Deus Ex GotY Edition via Proton in May 2020, but since the brightness function did not work it was too dark to be playable and I resorted to using my old Windows 7 machine to play.
Returning to Deus Ex via Revision in June 2021, I noticed the brightness function does work with Proton 6.3 as per aeikum's remark, however that version of Proton also introduces an extreme colour banding regression, unfortunately. Thus I'm resorting to playing via Windows 7 again since playing under Proton would force me to choose between colour banding (Proton 6.3) vs too dark to play reasonably (Proton 5.13). I confirm this is an issue for both GotY and Revision versions, both under D3D rendered, with Radeon GPU and open-source drivers (Mesa 20.2.6, I believe).
comment created time in 27 minutes
pull request commentmixxxdj/mixxx
DB v37: Synchronize file modified time with track source on metadata import/export
Unrelated
While testing this branch, I notice that the key value in the track property dialog changes from Traditionl to OpenKey notation after reload metadata from file. Is this related to this branch? Probably not.
Also not a regression from this branch, but it prevents testing it:
If I click "reload metadata from file" and leave the dialog with OK I got this:
critical [Main] DEBUG ASSERT: "m_recentTrackId == pTrack->getId()" in function void BaseTrackCache::replaceRecentTrack(TrackId, TrackPointer) const at /home/daniel/workspace/qt5mixxx/src/library/basetrackcache.cpp:165 critical [Main] DEBUG ASSERT: "!pTrack" in function void BaseTrackCache::replaceRecentTrack(TrackId, TrackPointer) const at /home/daniel/workspace/qt5mixxx/src/library/basetrackcache.cpp:198
Probably caused by #3906. I'll take care of that.
comment created time in 29 minutes
issue commentValveSoftware/Proton
[Whitelist] Deus Ex Human Revolution Directors Cut (238010)
I played Human Revolution Director's Cut via Proton back in June-July 2020. I noticed I could get around the 'missing textures' issue by toggling between full-screen and windowed modes. Usually I would do this at the main menu and then loading a game would allow me to play in full-screen (or whatever it was that has no window decorations, not sure if there's explicitly a borderless window mode). I also observed the hang-on-exit behaviour but I recall sometimes if I had the patience to leave it long enough it would close successfully. Not sure if time is a factor, though.
I plan on replaying again within the next few months, but not sure if I will have the same good experience with Proton 6.3, given some differences I'm noticing with the original Deus Ex (via Revision).
comment created time in 39 minutes
push eventmixxxdj/mixxx
commit sha a91affac2590bfc9f8d3345b8186c2897739021d
CI: Remove references to ubuntu-18.04 from build
commit sha 0d4f6fdc0ec44c4f264c20d4e1a87d80e0812243
CI: Upgrade jwlawson/actions-setup-cmake from v1.4 to v1.9
commit sha b5616dd76fe2f56c9de43afd9aaf3522007d6cfc
Enable StatementMacros in .clang-format
commit sha 7bfc8ac3d657a3556bdb562e80f9242af010fa2e
Delete obsolete comments referencing Ubuntu Bionic 18.04
commit sha 97218633ef4497bcea62dfd9b1b6cd0895c58d93
Delete obsolete workaround when casting a double into an enum
commit sha 3ddbbae90492fe8b7889d07a4c0fa0986b9d690d
Merge pull request #3985 from uklotzde/obsolete-ubuntu-bionic-18.04 Obsolete Ubuntu Bionic 18.04
push time in 40 minutes
PR merged mixxxdj/mixxx
- Update comments
- Update clang format settings
- Remove obsolete workaround
- Remove obsolete references in CI build
- Upgrade actions-setup-cmake in CI build
TODO:
- Update PPA build
pr closed time in 40 minutes
pull request commentmixxxdj/mixxx
Thank you for taking care.
comment created time in 40 minutes
pull request commentmixxxdj/mixxx
Done, see: https://launchpad.net/~mixxx/+archive/ubuntu/nightlies
comment created time in 41 minutes
pull request commentmixxxdj/mixxx
@daschuer Regarding the PPA: I was unsure if you want to delete all the conditionals that was required for supporting different releases with differing dependencies.
Do we distribute main builds through the PPA?? Then we definitely need to delete those 18.04 packages.
comment created time in 43 minutes
pull request commentmixxxdj/mixxx
DB v37: Synchronize file modified time with track source on metadata import/export
While testing this branch, I notice that the key value in the track property dialog changes from Traditionl to OpenKey notation after reload metadata from file. Is this related to this branch? Probably not.
Also not a regression from this branch, but it prevents testing it:
If I click "reload metadata from file" and leave the dialog with OK I got this:
critical [Main] DEBUG ASSERT: "m_recentTrackId == pTrack->getId()" in function void BaseTrackCache::replaceRecentTrack(TrackId, TrackPointer) const at /home/daniel/workspace/qt5mixxx/src/library/basetrackcache.cpp:165
critical [Main] DEBUG ASSERT: "!pTrack" in function void BaseTrackCache::replaceRecentTrack(TrackId, TrackPointer) const at /home/daniel/workspace/qt5mixxx/src/library/basetrackcache.cpp:198
comment created time in an hour
issue commentValveSoftware/Proton
I returned to Alien Swarm a few weeks ago, 10-17 May 2021 according to my logs. I noticed that there are GUI freezing issues with Proton 6.3 but Proton 5.13 seems okay. I haven't noticed any difference between Alien Swarm and Alien Swarm: Reactive Drop to date, in terms of Proton behaviour. For both Alien Swarm and Reactive Drop I need to set PROTON_USE_WINED3D=1.
comment created time in an hour
startedmljs/random-forest
started time in an hour
push eventmixxxdj/mixxx
commit sha 876db3ef1dd86c64794f7b57c6a5cec64533c494
Skins, waveforms: remove I-beam from in/outro marker to equalize marker size
commit sha 977eca1d04cbe15c7d6e9ce7716b3052c44736a7
Skins, waveforms: position in/outro markers inside the range
commit sha 8e6b3a80d683d8b29bbfe9fc23709d1f74ee7cd2
Merge pull request #3989 from ronso0/waveform-introoutro-markers Skins, waveforms: remove I-beam from in/outro markers to equalize marker size
push time in an hour
pull request commentmixxxdj/mixxx
Skins, waveforms: remove I-beam from in/outro markers to equalize marker size
Looks nice now. The windows build error is related. Thank you.
comment created time in an hour
startedphuctm97/ntast
started time in an hour
pull request commentmixxxdj/mixxx
cmake default_option() parentheses
But the actual notation should be UNIX;NOT APPLE;MP4_FOUND OR MP4v2_FOUND IIRC.
That is part of the first commit.
comment created time in an hour
pull request commentmixxxdj/mixxx
cmake default_option() parentheses
But the actual notation should be UNIX;NOT APPLE;MP4_FOUND OR MP4v2_FOUND IIRC. Because the semicolon is like an AND.
Check the example at: https://cmake.org/cmake/help/latest/module/CMakeDependentOption.html
So the bug was us using braces, which were redundant anyway.
comment created time in an hour
push eventcyring/CoreFreq
commit sha 8ecb9ccfa96406af19b671aca6d809a1d2b6d46d
Add links for AUR packages
commit sha 61cabad55486b4b54c19080f76ed3e234df71afc
Merge pull request #230 from inglor/fix-archlinux-packages Add links for AUR packages
commit sha 717e444e89caa0c74038f9c0d09ae68b725007cd
Kernel 5.12: Conditionally build w/o `MODULE_SUPPORTED_DEVICE`
commit sha 1d4f6b0053d38eccfe365ee6d85fe2bbaf539283
Version 1.85
commit sha 72bc79033c7846fac4b613ad9f7a56de94d386fc
Version 1.85 hotfix
commit sha ad622ca5e4cdb8a503da31a1049df609cd0545be
CoreFreq version 1.86
commit sha 99cfa916163a67b30cc209edce0ea3154be890f6
Version 1.86.3
push time in 2 hours
created tagcyring/CoreFreq
CoreFreq is a CPU monitoring software designed for the 64-bits Processors.
created time in 2 hours
push eventcyring/CoreFreq
commit sha a0e305fd58fc0484793b39dc3419e33727f388bc
Misc UI latency optimizations.
commit sha 0787a7b1d4aebd41b5dd68ef18610a2aa5f767a1
[Driver] New 'CPU_Count' argument to choose among: the kernel counting or hardware probing or any User value [Cli] Added the shortcut [G] to toggle the SysGate [UI] Moved some strings to the resources table; misc windows improved. [Kernel] Driver is operationnal with latest mainstream build 5.12.10
commit sha 0de2648c040e020c55596817afc07dadec6c64b9
CPU_Count argument is limited to CORE_COUNT and NR_CPUS
commit sha 250d75691358a23a098b62c08f9befdb6264ab39
Shared memory API footprint hardening. Stop compiling on first error. [AMD/Zen] P-State DID divisor computation fix.
commit sha aab94a9f0cbed0f2af4160e41e18719db3ae5ef9
[UI] Stream buffer memory overlap fix.
commit sha 99cfa916163a67b30cc209edce0ea3154be890f6
Version 1.86.3
push time in 2 hours
pull request commentmixxxdj/mixxx
Maybe delete the Ubuntu 18.04 package, so that users get a warning that the package is not updated any longer.
comment created time in 2 hours
pull request commentmixxxdj/mixxx
Add support for editing ReplayGain values.
I really wouldn't want this to be a default behavior for a few reasons.
I agree, and I wasn't suggesting that. But IMHO it's not really useful to edit the RG value by hand via the table. Instead, my suggestion would be to add a track menu entry "Update ReplayGain value from gain knob" for a currently loaded track.
That prevents situations where you blow out your speakers because you mistyped a value.
comment created time in 2 hours