DonationCoder.com Software > fSekrit

Beta: fSekrit 1.3 beta thread

(1/5) > >>

f0dder:
Believe it or not, I'm still working on fSekrit :)

I've set the release schedule for v1.3 at my birthday, October 15th. But I already have a beta version ready, for those that are interested (I suspect AbteriX will be, since I've added read-only notes support :)).

So far:
BETA1:

* added:  read-only notes, finally :)
* bugfix: changing key on unsaved document would crash
* bugfix: saving an empty document would crash

Eóin:
Small suggestion: How about adding a right click context menu for copy, cut and paste functions. Sometimes they're more useful than the keyboard shortcuts.

AbteriX:
Thank you f0dder!  :)

Brainstorming:

If i use "Make read only"
there is most of the file menu greyed out,, but the NEW button is still active.
So i can make a new EXE, which is still an r/o one and have the same PW as the original.

So i have this question:
why is the NEW button active for r/o fSekrit.exe's ?
Have anyone a need for this?

With this 1.3 beta1 i can use the NEW button
to reimport the text from a temp text file
and save it as new fSekrit.exe.
I would prefer to use the orignal exe to make new fSekrit files,
.. other people should use there own copy. ;)
So i think i have no need for this NEW button.  :-\

.

AbteriX:
If i use "Make read only"
this entry is not greyed out ... still clickable.. but of course without function.

Question:
should'nt this entry be greyed out too, if it once was clicked?

AbteriX:
If i use "Make read only"
the  "save" and "save as" is greyed out.

I can only save it if i close with the [X] button.

I suggest instead of  the "Make read only" entry
an "Save as read only.." entry
and disable the entry in the new created r/o exe only.

Navigation

[0] Message Index

[#] Next page