Marc

Member

Last active [hidden]

  1. 2 days ago
    Mon Jul 15 18:22:23 2019

    For those interested I have attached my first own theme. I won't say it's pretty, but I personally like soft colours. Feel free to adjust it.

  2. 5 days ago
    Fri Jul 12 18:35:04 2019

    @marco @Marc please let me know if you build some cool theme to share with other users!

    It won't certainly be cool ;), but I'm working on it now.

    I already have a new feature request :). A refresh button that reloads the theme in the preferences. Now I have to reopen it every time I changed something in the external editor ....

  3. last week
    Wed Jul 10 06:31:28 2019

    @marco Hi @Marc, we added themes customization in the latest Creo version: https://docs.creolabs.com/technotes/themes.html

    I (of course ...) already have seen that :)

  4. 2 weeks ago
    Tue Jul 2 18:32:18 2019
    Marc started the conversation iOS Background Fetch support.

    iOS has Background Fetch that allows you to run code when the app is in the background. This allows you to for example refresh data and/or send local notifications.

    This is not the same as the Timer control, as with Background Fetch the interval is determined by iOS (based on app usage by user).

  5. 3 weeks ago
    Sat Jun 22 10:24:54 2019
    Marc started the conversation Suggestion UI change split panels.

    I now have 2 panels: CODE and DESIGN. If I want to change that I have to first set one to LIVE before I can choose an other option. This is a bit cumbersome from a user perspective.

    What I'm suggesting is:

    • Always enable all panel options.
    • If I choose an option in panel 1 that is also selected in panel 2 (which shouldn't be possible), then change panel 2 to an other option. You could choose the most obvious one in that case. Eg. choose DESIGN in panel 2 if panel 1 is set to CODE. If that's not what the use wants, they can change that.
    • Add an extra button to just switch panels, if that's what the user is intended to do.
  6. Fri Jun 21 15:59:31 2019
    Marc started the conversation Case insensitive string operations.

    For functions that need to compare/find a string, I would like to have the option to have it work case insensitive.

    This now doesn't work:

    "abc".replace("A", "X")
    // doesn't replace "a" with "X"; expected result: Xbc
    
    var list = ["a", "b"]
    var result = list.contains["A"]
    // result is false; expected result: true

    In other languages, like .NET, you can pass an extra StringComparison enum parameter, with an argument like "InvariantCultureIgnoreCase".

    In my experience most string operations need to be handled case *in*sensitive.

  7. Fri Jun 21 15:38:55 2019
    Marc started the conversation Smaller zoom steps.

    The zoom steps (Cmd +/-) are +/- 100%, which is a bit high for me. Maybe +/- 25% would be better.

  8. Thu Jun 20 21:32:39 2019
    Marc started the conversation Short circuiting logical operations.

    Example:

    var x = 1
    var y = 0
    
    if (y == 0 or x / y == 1) {
    }

    In this example we have 2 expressions in the if-condition using "or" as the logical operator. If the first expression is true, then the second one doesn't have to be evaluated. In this case it *is* evaluated, resulting in a "Division by 0 error".

    The only work-around is using 2 nested if statements.

    NB: In this example I'm using a division expression, but it's also suitable for many other expressions.

  9. Thu Jun 20 17:49:26 2019
    Marc posted in PickerView.

    I'm afraid this would be impossible for them to implement as the standard native PickerView control of iOS doesn't support that. Only a list of textual items (not multiple columns). Just like a ComboBox in Windows.

  10. Thu Jun 20 17:42:15 2019
    Marc started the conversation Named arguments.

    When you have a method with optional parameters:

    func Test(a = 1, b = 2) {} 

    and you only want to provide argument "b", then you have to do this:

    Test( , "value for b")

    This looks a bit messy imho.

    In other languages I've always used named arguments, when available there, like this:

    Test(b: "only value b")

    Or:

    Test(b: "value b", a: "value a")

    NB: With named arguments, sequence doesn't matter.

    I personally find using named arguments, albeit more verbose (for some ...), gives better code readability and, as a bonus, is less prone to errors (if you f.e. use the wrong sequence).

View more