viper3400 / domanager Goto Github PK

Else the will be a firebird.log in application dir which reads:
Tue Apr 18 19:32:27 2016 ib_util init failed, UDFs can't be used - looks like firebird misconfigured C:\DoManager_3.0.1.1_master\bin/ib_util.dll library has not been found C:\DoManager_3.0.1.1_master\ib_util.dll library has not been found ib_util.dll library has not been found

There is no scrollbar defined explicitly. What happens if the number of tasklist entries in exceeds the current UI height?

When a task is blocked he won't become NEXT task.
A task could be blocked and unblocked in UI.
An item to block can be:

• ACTIVE
• NEXT
• stateless

If the active task is blocked, the current task phase is stopped.
If the next task is blocked, a new next task has to be evaluated.

In any case the task list will need a refresh.

Hi @viper3400 I've been on the lookout for a decent active c# (To)Do Manager type application for a while.
I had a search on github a little while a go but came up short.

I then had a look at your projects after you submitted the PR to ClipBoard and saw you are actively running one of these!
Perhaps I did not find this repo as most of my searches contained words like "ToDo" or "TaskList"

Anyhow I need an app that will popup alerts when certain tasks we due.
I wasnt sure that this app would do this from the readme but thought I'd give it a run and see if there might be scope for suggesting a feature like this if it doesn't offer this currently.

Anyhow when I run it I get the below issues:

1. Cannot create task
2. Crash on exit
   See these documented in gif below.

Perhaps I'm doing something wrong?
Running Win10
Let me know if there is anything else I can do to help ID this issue.

• On the way to integrate todo.txt into DoManager there should be a fast & dirty way to load task which are due or overdue from a todo.txt.
• Todo.txt need to be placed in "C:\Users[USER]\Documents\DoManager\TodoTxt\todo.txt"
• Todo.txt need to respect spec from https://github.com/ginatrapani/todo.txt-cli/wiki/The-Todo.txt-Format
• If this file exists the new button in tasklist view "Load Todo.txt" will be enabled
• Tasks, which a due or overdue will be inserted into DoManagers Next-Queue and will be marked as completed in the todo.txt

(Way to #19)

The right click on the status badges (NEXT, BLOCKED, ACTIVE, TODO) is just recognized when clicking directly on the text. Clicking on the border has no effect.

• DoManager should be able to interact with a todo.txt as specified at http://todotxt.com/.

• Therefore existing source code https://github.com/benrhughes/todotxt.net (under BSD licencse) may be partly used.

• #20 Simple proof of concept integration

• #21 Configurable path to todo.txt

• Useful integration of Todo.txt

V3.0.0.1
Reproducible when right click into grid header instead of a task entry

Anwendung: DoManager.exe Frameworkversion: v4.0.30319 Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet. Ausnahmeinformationen: System.Reflection.TargetInvocationException Stapel: bei System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean) bei System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[]) bei System.Reflection.RuntimeMethodInfo.Invoke(System.Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo) bei GalaSoft.MvvmLight.Helpers.WeakAction1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Execute(System.__Canon) bei GalaSoft.MvvmLight.CommandWpf.RelayCommand1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Execute(System.Object) bei GalaSoft.MvvmLight.Command.EventToCommand.Invoke(System.Object) bei System.Windows.Interactivity.TriggerBase.InvokeActions(System.Object) bei System.Windows.Interactivity.EventTriggerBase.OnEvent(System.EventArgs) bei System.Windows.Interactivity.EventTriggerBase.OnEventImpl(System.Object, System.EventArgs) bei System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(System.Delegate, System.Object) bei System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object) bei System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs) bei System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean) bei System.Windows.UIElement.ReRaiseEventAs(System.Windows.DependencyObject, System.Windows.RoutedEventArgs, System.Windows.RoutedEvent) bei System.Windows.UIElement.OnMouseDownThunk(System.Object, System.Windows.Input.MouseButtonEventArgs) bei System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(System.Delegate, System.Object) bei System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object) bei System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs) bei System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean) bei System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs) bei System.Windows.UIElement.RaiseTrustedEvent(System.Windows.RoutedEventArgs) bei System.Windows.UIElement.RaiseEvent(System.Windows.RoutedEventArgs, Boolean) bei System.Windows.Input.InputManager.ProcessStagingArea() bei System.Windows.Input.InputManager.ProcessInput(System.Windows.Input.InputEventArgs) bei System.Windows.Input.InputProviderSite.ReportInput(System.Windows.Input.InputReport) bei System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawMouseActions, Int32, Int32, Int32) bei System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef) bei System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) bei MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) bei MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) bei MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) bei System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) bei MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) bei MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) bei System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) bei System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame) bei System.Windows.Threading.Dispatcher.Run() bei System.Windows.Application.RunDispatcher(System.Object) bei System.Windows.Application.RunInternal(System.Windows.Window) bei System.Windows.Application.Run(System.Windows.Window) bei System.Windows.Application.Run() bei DoManagerMui.App.Main()

There should be a function which allows the user to open the exported time log right after export or open the whole export file folder.

• Given, that a task is in state "ACTIVE" and
• given, that another task is in state "NEXT" and
• given, that the button "START NEXT TASK" is hit
• than, the NEXT task should be ACTIVE and the until than active taks should become NEXT.

While working on another project I found the state column of DoManager UI need some fancy coloured state labels instead the boring text. Eventually the colouring made it much more easier to identify the active task at the first glance.

If defined export folders doesn't exist, an uncaught exception is raised. There should be an CanExecuteOpenExport Folder in TimeLogViewModel.cs so that button is disabled, when export directory don't exist.

OnOpenExportFolder = new RelayCommand(ExecuteOpenExportFolder);

On my Windows 8.1 machine the "Interrupt Active Task" label has grown to large when I capitalized the first letters. Buttons need to be larger or text need to fit into button size.

It's only possible to export the task log into a text file. It should be possible to view / copy it directly from UI.

After change the date in the time log datepicker (mouse click) the next click on the "Export time log" button won't fire the expected event.

The template database TEMPLATE.FDB mentioned in README.MD is not copied to output directory after build and therefore it's not part of the released ZIP package.

Path to ToDo,txt is hard coded to "C:\Users[USERNAME]\Documents\DoManager\TodoTxt\todo.txt". Instead a configurable setting should be considered.

(way to #19)

The time format should be HH:MM:SS, for example 01:32:50
Time report should show days only if the day part is greater than 0.

Explanation why it's possible to have task phases with such long duration:
TimeLog as available in UI today sums up all task phases of a task wich have a task phase end at the given date. A task phase that has been started three day ago and is ending today (and has never been stopped in between) will appear on todays task log with a duration 3 days ...

Export task log may freeze ui