Lone Wolf Development Forums  

Go Back   Lone Wolf Development Forums > Realm Works Forums > Realm Works Feature Requests

Notices

Reply
 
Thread Tools Display Modes
Farling
Senior Member
 
Join Date: Mar 2013
Location: Greater London, UK
Posts: 2,623

Old July 29th, 2019, 01:22 PM
Quote:
Originally Posted by kbs666 View Post
Create a topic, name it "Green," open Manage Names, set "Green" Case Matching to sensitive. Create another topic named _anything but Green_, use Green and green in snippets. Only "Green" will be found to be a valid name to link.

First image
Second image
The OP is wanting to set up alias names on the same topic with different capitalisation, not different topics.

Farling

Author of the Realm Works Import tool, Realm Works Output tool and Realm Works to Foundry module

Donations gratefully received via Patreon, Ko-Fi or Paypal
Farling is offline   #21 Reply With Quote
kbs666
Senior Member
 
Join Date: Oct 2014
Location: Chicago, IL
Posts: 1,690

Old July 29th, 2019, 02:56 PM
Quote:
Originally Posted by Farling View Post
The OP is wanting to set up alias names on the same topic with different capitalisation, not different topics.
Why? That makes no sense.

my Realm Works videos
https://www.youtube.com/channel/UCZU...4DwXXkvmBXQ9Yw
kbs666 is offline   #22 Reply With Quote
Farling
Senior Member
 
Join Date: Mar 2013
Location: Greater London, UK
Posts: 2,623

Old July 29th, 2019, 03:23 PM
Quote:
Originally Posted by kbs666 View Post
Why? That makes no sense.
He explained why wants to do it in the first post.

His explanation makes sense to me. He is avoiding having a topic called only "green" because it will cause too many links.

Farling

Author of the Realm Works Import tool, Realm Works Output tool and Realm Works to Foundry module

Donations gratefully received via Patreon, Ko-Fi or Paypal
Farling is offline   #23 Reply With Quote
Silveras
Senior Member
 
Join Date: Aug 2010
Posts: 1,528

Old July 29th, 2019, 04:59 PM
Yup.. in my case, it is not colors, but titles that can have different meanings in different organizations. Regardless, at least some of us have use for this.
Silveras is offline   #24 Reply With Quote
kbs666
Senior Member
 
Join Date: Oct 2014
Location: Chicago, IL
Posts: 1,690

Old July 29th, 2019, 05:11 PM
?
I use things with the same name all over the place. That isn't a problem. If he wants to use auto-accept based on capitalization I simply have to say that auto-accept is almost always a bad idea.

What he wants breaks my realm and breaks how I do things. I still remain unalterably opposed to this.

my Realm Works videos
https://www.youtube.com/channel/UCZU...4DwXXkvmBXQ9Yw
kbs666 is offline   #25 Reply With Quote
Bidmaron
Senior Member
 
Join Date: Dec 2010
Posts: 468

Old July 29th, 2019, 07:53 PM
It could be a setting you have to enable globally so kbs would be ok. That makes everyone happy. I would like it too. PF2 capitalizes or italicizes rules elements to keep things like lock from linking all the time if we had this option plus an option to require a particular font element to be an auto key
Bidmaron is offline   #26 Reply With Quote
Greebo
Senior Member
 
Join Date: Aug 2013
Location: Germany
Posts: 282

Old July 30th, 2019, 02:39 AM
Quote:
Originally Posted by Bidmaron View Post
It could be a setting you have to enable globally so kbs would be ok. That makes everyone happy. I would like it too. PF2 capitalizes or italicizes rules elements to keep things like lock from linking all the time if we had this option plus an option to require a particular font element to be an auto key
+1

This approach would be very useful for me.


Supporting Calendar Campaigner

Tools: Realm Works, Campaign Cartographer 3+ and Add-ons, MapTools
Games: home brew world, Lord of the Rings (CODA), Shadowrun, Earthdawn
Greebo is offline   #27 Reply With Quote
Farling
Senior Member
 
Join Date: Mar 2013
Location: Greater London, UK
Posts: 2,623

Old July 30th, 2019, 05:26 AM
Quote:
Originally Posted by kbs666 View Post
What he wants breaks my realm and breaks how I do things. I still remain unalterably opposed to this.
Why does allowing multiple aliases just with different capitalisation break your realm?

Farling

Author of the Realm Works Import tool, Realm Works Output tool and Realm Works to Foundry module

Donations gratefully received via Patreon, Ko-Fi or Paypal
Farling is offline   #28 Reply With Quote
kbs666
Senior Member
 
Join Date: Oct 2014
Location: Chicago, IL
Posts: 1,690

Old July 30th, 2019, 07:36 AM
Quote:
Originally Posted by Farling View Post
Why does allowing multiple aliases just with different capitalisation break your realm?
Because an alias is a distinct name and making every different capitalization distinct breaks my realm, and likely lots of other peoples, just to let this one guy use auto-accept.

my Realm Works videos
https://www.youtube.com/channel/UCZU...4DwXXkvmBXQ9Yw
kbs666 is offline   #29 Reply With Quote
Randall Jhen
Junior Member
 
Join Date: Feb 2014
Location: Zeeland, Michigan
Posts: 23

Old July 30th, 2019, 08:49 AM
But... But it only comes into play when a person is using the Case Sensitive setting on an alias. Instead of *only* being allowed to detect *one* combination of case sensitivity, this feature would allow you to detect variations of capitalization.

I cannot fathom how this breaks anything.

Would you kindly walk me through a specific, exact situation where this change would negatively affect your realm? Not an "ab vs. Ab vs. AB" hypothetical. Something real. Because for the life of me, all I can figure is that you're violently opposed to something I'm not suggesting.

Last edited by Randall Jhen; July 30th, 2019 at 09:00 AM.
Randall Jhen is offline   #30 Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -8. The time now is 05:33 AM.


Powered by vBulletin® - Copyright ©2000 - 2024, vBulletin Solutions, Inc.
wolflair.com copyright ©1998-2016 Lone Wolf Development, Inc. View our Privacy Policy here.