How to indent a new list item.
Hi!
So I am new to the composer, but not computers and what I call adaptive editors. I am having problems with the list editing feature. Specifically, how do I indent-in from a current indentation level? I can indent-out by hitting return, but I can no find the trick to indent-in.
Evernote for example just lets you tab and the indentation moves right, and hitting return/enter does in the way mmd Comp does.
Otherwise, having a great time using the tool.
J
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Fletcher on 02 Jul, 2013 12:11 PM
You can use the Shift Left/Right/Up/Down to do all of this.
FTP
2 Posted by Jeff Pfaffmann on 03 Jul, 2013 05:36 PM
That is not working for me. Shift left/right/etc only serves to highlight
text. I tried just now in 2.3.5 from the app store. Do I need to turn
something on?
Also, I would be nice if there were a cheat sheet for the different key
commands, separate from the MMD cheat sheet.
Support Staff 3 Posted by Fletcher on 03 Jul, 2013 07:42 PM
Shift Left/Shift Right/Shift Up/Shift Down are menu commands that move text as described. They don't highlight text.
It's probably worth a few minutes of your time to explore the available menu bar options in Composer. It can do a lot.
Fletcher closed this discussion on 03 Jul, 2013 07:42 PM.
Jeff Pfaffmann re-opened this discussion on 04 Jul, 2013 01:36 AM
4 Posted by Jeff Pfaffmann on 04 Jul, 2013 01:36 AM
So first, I was describing the behavior I am seeing.
Second, your menus could have better naming or you might be more obvious in
you documentation. Under the edit menu you have "move", move what? Well
now I know. But it could still use some explanation in the documentation,
as it implies a higher meta move function I did not pick up on.
Third, based on your menu, it is not shift left/etc, it is
shift-cmd-left/etc.
Fourth, when I use the key command as listed in the menu, the behavior is
still to highlight text either by word (left/right) or line (up/down).
I assume there is some thing conflicting with the mmdC key combinations,
but I am not sure what that is.
Thanks,
Jeff.
5 Posted by Jeff Pfaffmann on 04 Jul, 2013 01:42 AM
Ok, I see. After some playing around, I see that the cntl-cmd give me the
move behavior.
On Wed, Jul 3, 2013 at 9:36 PM, Jeff Pfaffmann <[email blocked]> wrote:
> So first, I was describing the behavior I am seeing.
>
> Second, your menus could have better naming or you might be more obvious
> in you documentation. Under the edit menu you have "move", move what?
> Well now I know. But it could still use some explanation in the
> documentation, as it implies a higher meta move function I did not pick up
> on.
>
> Third, based on your menu, it is not shift left/etc, it is
> shift-cmd-left/etc.
>
> Fourth, when I use the key command as listed in the menu, the behavior is
> still to highlight text either by word (left/right) or line (up/down).
>
> I assume there is some thing conflicting with the mmdC key combinations,
> but I am not sure what that is.
>
> Thanks,
> Jeff.
>
>
> On Wed, Jul 3, 2013 at 3:42 PM, Fletcher <
> [email blocked]> wrote:
>
>> **
>>
Support Staff 6 Posted by Fletcher on 04 Jul, 2013 01:46 AM
Correct - which is shown by the keyboard shortcut shown in the menu items. The shortcuts described in Composer are the same as described in all Mac OS X applications. If you're not familiar with the notation used, it's worth reading up about Mac OS X. It will save you a lot of time in the future.
Glad you've got things working!
Fletcher
7 Posted by Jeff Pfaffmann on 04 Jul, 2013 05:09 AM
I'm fine with reading menus, that but your treating your users poorly here
and cutting corners on explanations. If you tell people shift and it is
not shift, then something is off. If you want them to understand what it
means to move something, then you need to explain what you mean by move.
Plus, you hide it with all the pasting stuff and other items that have
nothing to do with movement and pasting.
You need to crawl into the user's head and not assume that they should
crawl into yours. I have been using computers since the early 1980s and
when I use menu systems of editors (for example Textmate, Emacs, and Vim) I
always knew what was meant, so don't try to school me on reading a set of
menus. Particularly when you do not seem to know that the real key
combination of some functionality you are touting is cntl-cmd instead of
shift.
But generally, your menus are muddled. You have editing items mixed with
formatting items and vice-versa. Then there is the versioning stuff that
is complex enough it should really be its own thing, particularly as users
sort-out the best way to use it.
Finally, there is this issue of forcing the user to search through a bunch
of menus when they forget the key combination. Why wouldn't you create the
cheat sheet and use it as an info source. I thought the point was to keep
the hands on the keyboard. You have these nifty see through windows, those
as a cheat sheet would be awesome.
I apologize for being critical and I believe your app has a lot of
potential, but the interface really needs to be a just a little slicker,
and just a bit more intuitive.
Best Regards.
Support Staff 8 Posted by Fletcher on 04 Jul, 2013 10:47 AM
Thank you for your feedback!
Fletcher